Re: [Jack-Devel] Windows application

I've been using the Connect window in qjackctl. To be honest, I never understood the difference between that and the patchbay. They seem to do the same thing.

Also - I'm running v1.9.8 from the download page. Is there some place I can get Windows binaries for a newer version? 
- Dave

Geoff Beasley <[hidden]> wrote:

On 05/20/2012 10:57 AM, Geoff Beasley wrote:
> On 05/20/2012 05:39 AM, Dave Horoschak wrote:
>> Since I'm on Windows I'm running Jack2. I start the master as normal 
>> (jackd -R -S -d portaudio -d "audio interface"), the slave starts 
>> with "jackd -R -S -d net", and the master then gets "jack_load 
>> netmanager". Again, everything seems to work - slave shows up in 
>> master's graph, it shows synching with latency 4, and I can 
>> cross-patch the ins on the slave to the outs on the master, and vice 
>> versa. I'm still not getting audio from either machines mic to the 
>> other's speakers, or by playing back files on either machine. 
>> Playback is still coming from the local machine's audio hardware and 
>> never from the remote machine. There must be a step I'm missing 
>> somewhere.
>>
> it's working by the sound of it. just try playing a wavefile on the 
> slave machine first to ensure your problem is not with muted mic 
> channels or whatnot. I'm on linux so cannot comment further about 
> specifics, however the principles are the same i believe.
>
>> One question I have... on the slave machine, how does jack know which 
>> audio hardware I'm using? I haven't defined it with a -d option like 
>> I did on the master.
>
> There is no local HW connection in jack on the slave machine - the 
> 'driver' is the Netjack2 driver -dnet ;)
>
> If you wanted to use your local HW with jack on the slave you would 
> need to stop Jack first then restart using -d (your HW driver here), 
> same as with your Master machine, but of course Netjack2 would not 
> operate. Jack cannot mount 2 '-d's' at the same time.
>

Just a thought Dave - are you using a patchbay for Jack? Jack doesn't 
connect clients automatically - you need a patchbay. Perhaps Qjackctl 
will work for you now - latest release a few days ago fixed a windows 
build problem i believe. Or you could try jack_connect from a command line.

g

1337476881.20114_0.ltw:2,a <9ee18db3-6405-4974-bb95-aa7b445d1705 at email dot android dot com>