[Alsa-user] using copy plugin => "file descriptor in bad state" error
Brought to you by:
perex
From: <Fri...@gm...> - 2002-08-09 12:59:36
|
Hi, I tried to get the copy plugin running using the following lines in my .asoundrc: pcm.cp_test { type copy # Copy PCM slave cp_slave # Slave name } pcm.pb { # playback device for copy plugin test type hw card 0 } pcm_slave.cp_slave { pcm pb } I can use the "cp_test" device for playback with aplay, i.e. aplay -D cp_test some_wav_file.wav works. But using the "cp_test" device as output with BruteFIR(0.99), I get the following error: ALSA lib pcm_hw.c:384:(snd_pcm_hw_start) SNDRV_PCM_IOCTL_START failed: File descriptor in bad state Could not start audio: File descriptor in bad state. Failed to start I/O module, aborting. Using the "pb" device with BruteFIR *does* work (and of course with aplay, too). Is this an Alsa-, copyPlugin-, asoundrc- or BruteFIR-problem? Here's some data about the redhat linux box used: Advanced Linux Sound Architecture Driver Version 0.9.0rc1. Compiled on Jun 14 2002 for kernel 2.4.9-13smp (SMP) with versioned symbols. 0 [card0 ]: ES1371 - Ensoniq AudioPCI Ensoniq AudioPCI ES1371 at 0xc400, irq 5 1 [card1 ]: RME9652 - RME Digi9652 (Rev 1.5) RME Digi9652 (Rev 1.5) at 0xda000000, irq 11 Using card1 instead of card0, I get the same error. However, I still don't see how the copy plugin could help me transferring the data from an ALSA output to an ALSA input. Maybe the "cp_slave" gets the audio data, but can I use this slave pcm as an ALSA input device for another application? Any ideas? fritz_e -- GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net |