Subject: [ecasound] Ecasound and jack
From: S. Massy (theanaloguekid_AT_tak.net.dhis.org)
Date: Tue Jan 08 2002 - 23:16:47 EET
Hi,
As I reported yesterday the jack plugin for ecasound now has grown very
usable and reliable. So, encouraged by this, I've ventured a bit further
in its use and hit a knot.
Command lines:
# jackd -R -p 512 -d sbl &
# ecasound -b:512 -sr:48000 -f:16,2,48000 -a:1,2 -i:jack_alsa,in \
-a:1 -o:jack_alsa,out -ea:200 -erc:1,2 \
-a:2 -o:file.wav -erc:1,2
I start the processing, it works for about three to five seconds and
then everything freezes; I could reproduce it several times. (fsck is
fun)
Any idea what might be going on?
Another thing that seems to happen more randomly is that things aren't
dealt with properly upon stopping the processing... for example:
----------
# ecasound -b:512 -sr:48000 -f:16,2,48000 -i:jack_alsa,in -o:jack_alsa,out -c
****************************************************************************
* ecasound v2.1dev7 (C) 1997-2001 Kai Vehmanen
****************************************************************************
- [ Session created ] ------------------------------------------------------
(eca-session) Interactive mode enabled.
- [ Chainsetup created (cmdline) ] -----------------------------------------
alsa_pcm: xrun of 1288 frames, (26.833 msecs)
(eca-chainsetup-parser) Setting buffersize to (samples) 512.
(eca-chainsetup-parser) Setting internal sample rate to: 48000
ecasound ('h' for help)> start
- [ Connecting chainsetup ] ------------------------------------------------
(eca-chainsetup) 'rtlowlatency' buffering mode selected.
new client: ecasound, type 2 @ 0x402b1000
client ecasound is on event fd 15
(eca-chainsetup) Audio object "jack_alsa", mode "read".
(audio-io) Format: f32_le, channels 2, srate 48000, noninterleaved.
(eca-chainsetup) Audio object "jack_alsa", mode "write".
(audio-io) Format: f32_le, channels 2, srate 48000, noninterleaved.
- [ Chainsetup connected ] -------------------------------------------------
(eca-controller) Connected chainsetup: "command-line-setup".
- [ Controller/Processing started ] ----------------------------------------
alsa_pcm: xrun of 1080 frames, (22.500 msecs)
- [ Engine init - mixmode "simple" ] ---------------------------------------
(eca-control) ERROR: Warning! No chainsetup connected. Trying to connect currently selected chainsetup.
(eca-engine) Using realtime-scheduling (SCHED_FIFO).
trying to connect alsa_pcm:in_1 and ecasound:in_1
trying to connect alsa_pcm:in_2 and ecasound:in_2
trying to connect ecasound:out_1 and alsa_pcm:out_1
trying to connect ecasound:out_2 and alsa_pcm:out_2
ecasound ('h' for help)> stop
- [ Controller/Processing stopped ]----------------------------------------
disconnecting alsa_pcm:in_1 and ecasound:in_1
alsa_pcm:in_1 DIS-connecting and ecasound:in_1
ecasound:in_1 DIS-connecting and alsa_pcm:in_1
ecasound ('h' for help)> quit
(hung: CTRL-c)
Ecasound watchdog-thread received signal 2. Exiting..
Warning! Problems while shutting down the engine!
(hung: CTRL-c)
cannot read port registration result from server
(hung: CTRL-c)
cannot read port registration result from server
#
----------
Other times it'll work just fine but the messages upon stopping the
processing are:
----------
disconnecting alsa_pcm:in_1 and ecasound:in_1
alsa_pcm:in_1 DIS-connecting and ecasound:in_1
ecasound:in_1 DIS-connecting and alsa_pcm:in_1
disconnecting alsa_pcm:in_2 and ecasound:in_2
alsa_pcm:in_2 DIS-connecting and ecasound:in_2
ecasound:in_2 DIS-connecting and alsa_pcm:in_2
disconnecting ecasound:out_2 and alsa_pcm:out_2
ecasound:out_2 DIS-connecting and alsa_pcm:out_2
alsa_pcm:out_2 DIS-connecting and ecasound:out_2
disconnecting ecasound:out_1 and alsa_pcm:out_1
ecasound:out_1 DIS-connecting and alsa_pcm:out_1
alsa_pcm:out_1 DIS-connecting and ecasound:out_1
----------
Regards,
S. Massy
-- To unsubscribe send message 'unsubscribe' in the body of the message to <ecasound-list-request_AT_wakkanet.fi>.
This archive was generated by hypermail 2b28 : Tue Jan 08 2002 - 23:08:03 EET