why is that it does not seem to be possible to run two csound processes
writing to the jack server? The second always fails with the message

"cannot read response from jack server"
"**rtjack: could not connect to JACK server"

Victor

At 14:48 11/04/2006, you wrote:
>On Tue Apr 11, 2006 2:18 pm, Victor Lazzarini wrote:
>
> > I could not find the command-line option that allows
> > for csound to automatically connect to a Jack port,
> > as soon  as it is started (for instance to alsa in/out).
> > How do we do it?
>
>By using the full port name - not including any channel number
>suffix - as the device name for -i adc or -o dac. For example,
>a stereo orchestra would connect to alsa_pcm:playback_1 (left)
>and alsa_pcm:playback_2 (right) if -o dac:alsa_pcm:playback_ is
>used.
>See also this page for more information on using the JACK plugin:
>   http://csounds.com/manual/html/using.html#csound5jack
>--
>Send bugs reports to this list.
>To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk

Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth 

I've had this problem before; the default name for both processes is 
the same, "csound5".

try using the -+jack_client="name" with a unique handle as "name" for 
each instance.


-David

On Apr 11, 2006, at 11:17 AM, Victor Lazzarini wrote:

> why is that it does not seem to be possible to run two csound processes
> writing to the jack server? The second always fails with the message
>
> "cannot read response from jack server"
> "**rtjack: could not connect to JACK server"
>
> Victor
>
> At 14:48 11/04/2006, you wrote:
>> On Tue Apr 11, 2006 2:18 pm, Victor Lazzarini wrote:
>>
>> > I could not find the command-line option that allows
>> > for csound to automatically connect to a Jack port,
>> > as soon  as it is started (for instance to alsa in/out).
>> > How do we do it?
>>
>> By using the full port name - not including any channel number
>> suffix - as the device name for -i adc or -o dac. For example,
>> a stereo orchestra would connect to alsa_pcm:playback_1 (left)
>> and alsa_pcm:playback_2 (right) if -o dac:alsa_pcm:playback_ is
>> used.
>> See also this page for more information on using the JACK plugin:
>>   http://csounds.com/manual/html/using.html#csound5jack
>

That's done it, thanks!

At 16:27 11/04/2006, you wrote:
>I've had this problem before; the default name for both processes is the 
>same, "csound5".
>
>try using the -+jack_client="name" with a unique handle as "name" for each 
>instance.
>
>
>-David
>
>On Apr 11, 2006, at 11:17 AM, Victor Lazzarini wrote:
>
>>why is that it does not seem to be possible to run two csound processes
>>writing to the jack server? The second always fails with the message
>>
>>"cannot read response from jack server"
>>"**rtjack: could not connect to JACK server"
>>
>>Victor
>>
>>At 14:48 11/04/2006, you wrote:
>>>On Tue Apr 11, 2006 2:18 pm, Victor Lazzarini wrote:
>>>
>>> > I could not find the command-line option that allows
>>> > for csound to automatically connect to a Jack port,
>>> > as soon  as it is started (for instance to alsa in/out).
>>> > How do we do it?
>>>
>>>By using the full port name - not including any channel number
>>>suffix - as the device name for -i adc or -o dac. For example,
>>>a stereo orchestra would connect to alsa_pcm:playback_1 (left)
>>>and alsa_pcm:playback_2 (right) if -o dac:alsa_pcm:playback_ is
>>>used.
>>>See also this page for more information on using the JACK plugin:
>>>   http://csounds.com/manual/html/using.html#csound5jack
>
>--
>Send bugs reports to this list.
>To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk

Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth