Re: [Jack-Devel] problems MIDI patchbay

I'm using LoopBe1, but I can't get my application (Musescore) to show up in the MIDI connections tab. I'm also using Windows 8.1. Any ideas?

Chad

On Feb 8, 2014, at 7:32 AM, David Santamauro <[hidden]> wrote:

> On 02/08/2014 05:54 AM, Nicola Di Vito wrote:
>> I am a beginner in this matter. I am using Jack audio connection kit on
>> Windows 8.1. While in audio patchbay everything go fine, in MIDI
>> patchbay doesn't appear no name of application-client when I add a new
>> plug-in, otherwise from audio patchbay (where appear the name of the
>> application)but only “System_midi”. I have added, following your
>> instructions, in Settings, in the field of server prefix the suffix: <-X
>> winmme>; the drivers I use is “portaudio”. So, if I try to connect for
>> instance the system_midi output with the system_midi intput, sending
>> Finale playng a MIDI stream to Pro Tools as recorder in a midi track,
>> nothing happen.What could I do?
>> Thanks niky
> 
> I can't comment on the patchbay naming, sorry. As for routing, it sounds like you are trying to route a hardware midi out to a hardware midi in. That won't work.
> 
> You need virtual midi interfaces/cables [1][2]. LoopBe has a free version (1 input/output) and there is a version allowing, I believe, 30 virtual cables.
> 
> I use LoopBe30, cost ~ 20 US $ / 17€ and works like a charm.
> 
> With all those unnamed cables, patches and routes, you will surely need a midi monitor of sorts [3]. This will help you diagnose missing connections, etc.
> 
> [1] http://www.nerds.de/en/loopbe1.html
> [2] http://www.tobias-erichsen.de/software/virtualmidi.html
> [3] http://www.midiox.com/
> 
> 
> 
> 
> Jack-Devel mailing list
> [hidden]
> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

1391920802.25777_0.ltw:2,a <4C3419FE-331C-426E-A7DC-4B1A0D09447A at gmail dot com>