[Fluxus] connecting to Jack

[David Griffiths]

Hi Kassen,

Make it work for jackd2 I reckon... you can always pass the ports on
commandline if you want to still use jack1.

cheers,

dave

On 04/17/2012 03:31 PM, Kassen wrote:
> Dear list, 
> 
> I'm trying to fix Fluxa in that I want Fluxa to connect automatically
> to Jackd on a new-ish Ubuntu install like it does on my 10:10 install.
> For this I already updated the depreciated jack_client_new to
> jack_client_open but that didn't help.
> 
> Then I noticed that the actual error in connecting refered to a
> unknown port. I traced what I believe is the core of the matter to
> this part of the code in (fluxa's) main.cpp;
> 
> ----------------------8<-------------------
> #ifdef __APPLE__
>     string leftport("system:playback_1");
>     string rightport("system:playback_2");
> #else
>     string leftport("alsa_pcm:playback_1");
>     string rightport("alsa_pcm:playback_2");
> #endif
> 
> ----------------------8<-------------------
> 
> As I understand the info I was able to find online this isn't a
> difference between Apple and Linux as much as it is a difference
> between Jackd1 (using alsa_pcm) and Jackd2 (using system). Even that
> isn't entirely correct; on my own Linux computer (using jackd2) the
> alsa_pcm parameter is accepted (I get sound) even though jack_lsp
> lists the ports in question as being called "system....".
> 
> Clearly the above condition doesn't completely reflect reality and the
> check may need to be for the presence of Jackd1 or 2, unless jackd1 is
> also switching to calling it "system". I think it might, because jack
> can also connect to cards through means other than alsa, for example
> the firewire series of drivers.
> 
> Personally, BTW, I prefer jackd2 because unlike 1 jackd2 won't
> disconnect clients over a few missed deadlines. I think that makes it
> a more pleasant pick for experimental live performances where things
> can and will occasionally go wrong.
> 
> I think this will affect Fluxus too, not just Fluxa, so we should
> probably talk about what would be the best sollution here.
> Particularly I'm curious whether anything would go wrong if we'd
> simply just refer to "system".
> 
> Yours,
> Kas.
>