Re: [Jack-Devel] problems MIDI patchbay

Hi Chad,

I would suggest that you don't use JACK Midi at all as it will only be
available for client software that has native support for JACK Midi
(Musescore, GrandOrgue, LinuxSampler, etc. but not Finale, Pro Tools,
etc.). In my experience, Windows MIDI drivers lock the MIDI interfaces
to the application that is using them, so configuring JACK with -X
winmme typically locks LoopBe or LoopMIDI ports to JACK and other
software then cannot access them.

So use JACK for Windows for your Audio (using the ASIO JackRouter) and
then LoopMIDI or LoopBe as your virtual MIDI cables between Finale and
Pro Tools.

Kind regards,
GrahamG

On 2/9/14, Chad Hastings <[hidden]> wrote:
> 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 EURO 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
> 
> Jack-Devel mailing list
> [hidden]
> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
>

1391942066.7890_0.ltw:2,a <CALuNdZR4b3gxnBn-7xRh79=DrGKu_aA_S14Wa3Hj69F1UDxi1g at mail dot gmail dot com>