Subject: Re: [ecasound] new ecasound jack plugin
From: Jeremy Hall (jhall_AT_uu.net)
Date: Tue Jan 29 2002 - 20:57:00 EET
I still get xruns and some assert related to buffer_size keeps
spontaneously being thrown every once in a while. I have less problems
with jack_alsa (since I changed jack_port_connect to jack_connect) but I'd
like to see:
By being able to use %me to represent my client name, you can reliably use
the correct ecasound client, but if you could define both src and
destination clients, you could force a sort of patch bay thing. AND, an
optimization might be:
ecasound -i:jack_generic:alsa_pcm:in_%i -o:jack_alsa,eca2
where %i is replaced with an integer. This would allow for clients that
don't use the _n concept but instead a different numbering scheme and you
don't have to type so much.
My former example might also be written:
that would tell ecasound to start counting from 3 and go for channels()
In the new year, Kai Vehmanen wrote:
> On Mon, 7 Jan 2002, S. Massy wrote:
> >> Now how come ecasound works fine here, absolutely no problems, both with
> >> ALSA 0.9.x and OSS? And if it really is soundcard specific, that makes
> > But the good news is that I just enjoyed two hours of non-garbled rt
> > processing with ecasound using the jack plugin... So I guess there's
> > hope... :)
> You really should try the latest ecasound CVS-tree and its native ALSA 0.9
> support. The ALSA-related bug fix I committed a few days might just fix
> the full-duplex problems you've been having.
> Audio software for Linux!
> To unsubscribe send message 'unsubscribe' in the body of the
> message to <ecasound-list-request_AT_wakkanet.fi>.
-- 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 29 2002 - 20:46:58 EET