Re: [Jack-Devel] Windows application

PrevNext  Index
DateSat, 19 May 2012 15:39:59 -0400
From Dave Horoschak <[hidden] at horoschak dot net>
ToGeoff Beasley <[hidden] at laughingboyrecords dot com>
Cc"[hidden] at lists dot jackaudio dot org" <[hidden] at lists dot jackaudio dot org>
In-Reply-ToGeoff Beasley Re: [Jack-Devel] Windows application
Follow-UpGeoff Beasley Re: [Jack-Devel] Windows application
On 5/18/2012 6:58 PM, Geoff Beasley wrote:
>
> ok time to be clear on this confusing jack nomenclature.
>
> Jack1 and Jack2 and Netjack1 and Netjack2 have different commands for 
> equivalent actions.
>
> In Jack2 the -d net option calls up the Netjack2 driver.
>
> In Jack1 the -d net option calls up the Netjack1 driver. Netjack2 is 
> not available for Jack1
>
> The Netone driver is only available under Jack2 - it is  Netjack1 for 
> Jack2 - you simply call up -d netone.
>
> Now it gets silly...connecting audio I/O for Netjack1 is different to 
> connecting Netjack2
>
> for Netone/(and Netjack1?) =
>
>      -i, --audio-ins     Number of capture channels (defaults to 2) 
> (default: 2)
>     -o, --audio-outs     Number of playback channels (defaults to 2) 
> (default: 2)
>     -I, --midi-ins     Number of midi capture channels (defaults to 1) 
> (default: 1)
>     -O, --midi-outs     Number of midi playback channels (defaults to 1)
>
> for Netjack2
>
>     -C, --input-ports     Number of audio input ports. If -1, audio 
> physical input from the master (default: -1)
>     -P, --output-ports     Number of audio output ports. If -1, audio 
> physical output from the master (default: -1)
>     -i, --midi-in-ports     Number of midi input ports (default: 0)
>     -o, --midi-out-ports     Number of midi output ports (default: 0)
>
> So to sum up - if you're using Jack2, you can choose to use 
> Netjack2/jack_load netmanager or Netone/jack_netsource
>
> For Jack1 Netjack1(-d net)  is you're only option.
>
> My strong recommendation is to use Jack2 as it is more robust and 
> Netjack2 is far superior now to Netjack1 and Netone.
>

Thanks - this is extremely helpful and clarifies what I should be doing.

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.

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.

Other than for that, I'm at a loss for next steps.
  - Dave
PrevNext  Index

1337456440.25756_0.ltw:2,a <4FB7F70F.8010003 at horoschak dot net>