Re: [ecasound] issues with ecasound CVS and jack

New Message Reply About this list Date view Thread view Subject view Author view Other groups

Subject: Re: [ecasound] issues with ecasound CVS and jack
From: Kai Vehmanen (k_AT_eca.cx)
Date: Tue Apr 23 2002 - 09:44:21 EEST

On Sun, 21 Apr 2002, Jeremy Hall wrote:

> I have noticed that with current CVS and current jack CVS, starting
> ecasound like this yields this error:

Btw; I have noted at least one similar error case, although it only
occurs if -z:db is enabled (you seem to have -z:db disabled). Anyway, this
is on my todo-next-list.

> Peace:/src/sound/ecasound/CVS/sound/ecasound_BUILD_ALSA # !mrec
> mrec 239.1.1.3/24119 2>/dev/null|ecasound -i stdin -o jack_alsa,out
> -z:nodb -ea:5 -r
[...]
> (eca-chainsetup) Audio object "stdin", mode "read".
> (audio-io) Format: s16_le, channels 2, srate 44100, interleaved.
> cannot read response from jack server (No such file or directory)
> (eca-chainsetup) Audio object "jack_alsa", mode "write".
> (audio-io) Format: f32_le, channels 2, srate 44100, noninterleaved.
> - [ Chainsetup connected ]

This is odd. We get a failure from jackd even before the chainsetup gets
connected (= ecasound activates the JACK ports).

> (audioio-jack-manager) Connection closed!

You'll get more verbose error messages with -d:255 (look for
"jack-manager" messages).

> but if I start ecasound interactively it works just fine. Is this error
> coming from jack or ecasound?

Hard to say without further investigations. 

-- 
 http://www.eca.cx
 Audio software for Linux!

--
To unsubscribe send message 'unsubscribe' in the body of the
message to <ecasound-list-request_AT_wakkanet.fi>.

New Message Reply About this list Date view Thread view Subject view Author view Other groups

This archive was generated by hypermail 2b28 : Tue Apr 23 2002 - 09:30:06 EEST