Subject: Re: [ecasound] problem with ecasound 2.2.1
From: j.c.w. (jcwjcw_AT_qwest.net)
Date: Tue Mar 11 2003 - 02:31:56 EET
Kai,
thanks for the speedy reply!
your suggestions, sadly, did not produce results. it still hung in the same place and still needed to be killed. i will see if i can set up the cvs version later in the hopes that it will work. do you have other suggestions or things that you would like me to try? i'm more than willing to help run this down.
thanks for you time and effort!
take care,
j.c.w.
p.s. - i also appreciate the pronunciation clarification.
On Mon, 10 Mar 2003 15:28:15 +0200 (EET)
"Kai Vehmanen" <k_AT_eca.cx> wrote:
> On Sun, 9 Mar 2003, j.c.w. wrote:
>
> > ecasound -i:myfile.wav -o:alsa,dsp1
> [...]
> > i am running the debian unstable package with alsa rc7 drivers for my
> > hammerfall (rme9652) card. part of the reason that i am so curious is
> > that i don't have this issue at all with ecasound 2.0. in fact, when
>
> Hmm, this might be the same issue I've noticed a few times with my
> delta-44. Could you test the following:
>
> - try both with -z:nointbuf and -z:intbuf
> - try "-i:myfile.wav -f:32,10,44100,n -o alsahw,1" ... or with "alsahw,0"
> if rme is your first card; in effect we are bypassing the ALSA
> plugin layer
>
> ... if this is the same bug, it is fixed in ecasound CVS and in the next
> 2.2.2 release. The bug is triggered when you use ecasound to write a X
> channel file to a Y channel ALSA device through the ALSA PCM plugin
> layers. If Y>X, the bug occurs.
>
This archive was generated by hypermail 2b28 : Tue Mar 11 2003 - 02:19:02 EET