Skip to contentSkip to conversation

newest versions of cs46xx driver => Terratec Xfire recording problem

DISCUSSION [email protected] 2 participants 2 messages Aug 4, 2002

lore
Share & tools
lore
#0 lore raw

Hi,

using the newer versions of the cs46xx driver with my Terratec DMX Xfire, I can use several playback subdevices at different sampling rates correctly. Many thanks, Benny!

But now I've got some trouble recording from the soundcard input:
Trying to record (or using a realtime audio application
input->process->output), I cannot select the input source any more. Alsamixer shows the capture flag at the correct position (e.g. CD or Mic), but hw:0,0 always records the output from PCM only.
I always record (or hear) silence until I produce some PCM output (e.g.
aplay or a BEEP in a shell). This PCM output gets looped back and I get a non-ending loud feedback noise (sounds just like acoustic feedback noise).

This input problem occurs with the following 2 driver versions:

1.
alsa-driver-0.9.0rc2-bs20020731.tar.gz +
alsa-driver-0.9.0rc2-bs20020731.diff +
additional patch in mail from 1.aug.2002

2.
cvs snapshot 2002-08-02
(I compiled the alsa-driver tree only using "cvscompile" and then "make install-modules")

The problem seems to be related to the pcm multi support as I can use the alsa-driver-0.9.0rc2-bs20020723.tar.gz driver version without this problem.

Any ideas what's the reason for this?
fritz_e

Signature · 9 lines
GMX - Die Kommunikationsplattform im Internet.
http://www.gmx.net



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
#1 lore raw
Quoted 11 lines

But now I've got some trouble recording from the soundcard input:
Trying to record (or using a realtime audio application
input->process->output), I cannot select the input source any more. Alsamixer shows the capture flag at the correct position (e.g. CD or Mic), but hw:0,0 always records the output from PCM only.
I always record (or hear) silence until I produce some PCM output (e.g.
aplay or a BEEP in a shell). This PCM output gets looped back and I get a non-ending loud feedback noise (sounds just like acoustic feedback noise).

In fact that I've not tested thoose part yet, so it's that they broken as consequence with all other changes done.

Quoted 8 lines

This input problem occurs with the following 2 driver versions:

1.
alsa-driver-0.9.0rc2-bs20020731.tar.gz +
alsa-driver-0.9.0rc2-bs20020731.diff +
additional patch in mail from 1.aug.2002

Quoted 8 lines

2.
cvs snapshot 2002-08-02 (I compiled the alsa-driver tree only using "cvscompile" and then "make install-modules")

The problem seems to be related to the pcm multi support as I can use the alsa-driver-0.9.0rc2-bs20020723.tar.gz driver version without this problem.

There where many hard && critical changes done between thoose two releases, it has probably become broken.

I will investigate the "recording" part, i believe the problem is (hopefully) easy fixed.

/Benny

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf