Re: [Jack-Devel] Mixed Windows / Linux system

Hi Jeroen,

In order to be able to map the Windows MIDI ports you will need to
start Jack with the 'winmme' option.

For example:
jackd.exe -v -R -S -X winmme -d portaudio -p 512 -d "ASIO::Saffire
1394 ASIO x64"

Then, in Hauptwerk you must use 'JackRouter' as the Audio device as is
this what sends the audio signal to the Jack Audio Connection Kit
server. You also need to use the loopMIDI port in Hauptwerk and then
map it using Jack Control MIDI panel.

JackRouter brings the Audio into the Jack Audio Server.... using the
-X winmme option captures the MIDI. The winmme option is only
available in the latest 1.9.8 testing versions...

Also see:
http://www.64studio.com/manual/audio/jack
http://www.rncbc.org/drupal/node/76

Hope that helps (and that I got it correct myself!)

GrahamG

On 6/27/11, Jeroen Van den Keybus <[hidden]> wrote:
>  Hello Graham,
>
>
>
>> Just to summarize - you'd like to use JackNet to pipe MIDI from your
>> Ubuntu netbook through to your Windows Vista Ultimate (64-bit) Jack
>> for Windows -> Hauptwerk (are you running HW in 32-bit or 64-bit??)
>> and then pipe the resulting Audio out from Hauptwerk -> NetJack to
>> your Ubunut netbook Jack system?
>
>
> Correct. I've installed 64-bit HW.
>
>
>> I'm asking this for clarity for other users as I have not used Netjack
>> so can't help with those specifics.
>>
> Well, my problem is that Netjack is apparently merged into Jack now.
>
>
>> 2) I have to start Jackd from the command prompt in Windows too, so
>> that is expected behavior until such time and Qjackctl catches up with
>> some of the windows development.
>>
>
> Aha. Good to hear that. Is it also acceptable to have three 'Not a
> driver' .dll error codes with return value 127 ?
>
>
>>
>> 3) If you are using Hauptwerk in 64-bit, then you will not be able to
>> connect the audio out from HW to Jack 1.9.7 and you will need 1.9.8
>
>
> In that case I will need to build Jack 1.9.8 from SVN and I still need some
> hints on how to do that: I can't seem to manage to produce a Makefile for
> the build.
>
>
>> 4) For Ubuntu I would suggest using Jack Control to automatically run
>> jackd and load a patchbay configured with the various connections
>> needed.
>>
>
> In fact, I have serious difficulty understanding the concepts behind the
> patchbay, connect and session windows. Anywhere I can find this explained ?
> The jackaudio.org documentation was no help to me.
>
> As far as I understand now, it would be sufficient to use the Connect box.
>
>
>> I suggest you take a look at loopMidi
>> (http://www.tobias-erichsen.de/loopMIDI.html) as it supports 64-bit
>> Windows.
>>
>
> Thanks a lot for this link.
>
>
>> Sorry I can't help more as I have not yet tried a setup like this...
>>
>
> I'm still a bit confused over the Windows PC configuration I have to make
> with HW.
>
> What input and output device do I have to use in HW ? What drivers
> (JackRouter, ASIO, loopMIDI) should I load ? Do I need WinMME ?
>
> The problem is: I have understood that, when using the 'net' backend, I
> cannot use local physical audio resources and I'm unclear if the JackRouter
> is one of them (or whether JackRouter is only available with the 'portaudio'
> backend).
>
>
> Jeroen.
>

1309181745.14948_0.ltw:2,a <BANLkTin=x0Yvv52fhM411QZt2yyH=QwPXg at mail dot gmail dot com>