Closed cnkoder closed 2 years ago
Dsnoop works well when the slave.pcm is a hardware device but as soon as I point to something else it fails. Is there a workaround or any other solution to tackle this problem?
dsnoop
, dshare
, dmix
plugins works only with hw:
plugins (direct ALSA devices). Why you cannot use the eco
pcm device two times directly ?
Replying to myself - pipe right...
Pehaps, the used software may write output to two pipes, if possible. Or you may use the ALSA loopback soundcard (snd-aloop
kernel module) and dsnoop
on top of it.
Pehaps, the used software may write output to two pipes, if possible. Or you may use the ALSA loopback soundcard (
snd-aloop
kernel module) anddsnoop
on top of it.
Thank you, will search on the compatibility of dsnoop with snd-aloop and try this out first and then maybe move the first option. Will update as soon as I get some results
Replying to inform on what was done. Searched on snd-aloop but I could not achieve what was required, therefore edited the software to write data to two pipes and managed to solve the problem. Thanks again
Problem
I am facing problems in using "dsnoop" to share/divide the audio stream into two. When dsnoop plugins' slave is set to be a FIFO it throws an error.
executed:
error:
This is the current asound.conf settings
asound.conf
Note: eco is used to read the FIFO file which contains the echo canceled audio coming in from cancellation software. This software's input is hw:0 and records audio directly from the microphone, and then processes and passes this over to ec.output
Dsnoop works well when the slave.pcm is a hardware device but as soon as I point to something else it fails. Is there a workaround or any other solution to tackle this problem?