Subject: Re: [Jackit-devel] Re: [ecasound] new ecasound jack plugin
From: Kai Vehmanen (k_AT_eca.cx)
Date: Sat Dec 22 2001 - 00:18:49 EET
On Thu, 20 Dec 2001, S. Massy wrote:
> ecasound's native alsa plugin or ardour. I was most interested in the
> full duplex side of things as I can't currently get reliable full duplex
> processing from ecasound, it works fine but the sound grows garbled
> after about ten minutes. Unfortunately I experience the exact same
Same happens here, although I'm not sure whether it's a xrun (driver
unable to fully recover) or full-duplex (goes out-of-sync after X minutes)
problem.
> term.) Also, with a command such as:
> # ecasound -i:jack_alsa,in -o:jack_alsa,out -c
> As I said things work just find at start up, the connecting of the cs
> goes well and so does the starting of the engine. However whenever I try
> to stop the engine in any way causing, I assume, the jack manager to
> attempt disconnecting the client, ecasound hangs. Sending a sigint
I've fixed dozends of little bugs during the last few days. These hangs
are mostly gone, but there are still few left. Most visible ones are:
- ctrl-c'ing ecasound when jack plugin is active causes
a core dump; this is very difficult to trace and not
fully reproducible
- if the engine hangs, ecasound will hang too (libjack
uses blocking operating so this affects all client apps)
> BTW, I was wondering, when running both jackd and ecasound with raised
> priority, which should be set with the higher priority?
This is a good question. As they are supposed to run serialized, they
should never run at the same time. So based on this I'd say they should
run with the same priority (at least the same priority class; ie. normal
vs schedfifo).
-- 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>.
This archive was generated by hypermail 2b28 : Sat Dec 22 2001 - 00:11:49 EET