'Twas brillig, and Amar Akshat at 25/06/12 05:27 did gyre and gimble: > Now when I play a music on my on-board sound device (HDA Intel), and execute > > *arecord -Dpulse_monitor -c2 -fS32_LE /dev/null -vvv* > > I am able to monitor. > > However, when I monitor and do the following, > *arecord -Dpulse_monitor1 -c2 -fS32_LE /dev/null -vvv* > * > * > *&* > * > * > *aplay -Dhw:1 -c1 -fS16_LE song.wav, * > > the o/p is > > *aplay: main:660: audio open error: Device or resource busy. * This is expected as the pulse_monitor device will require the device to be opened by PulseAudio, but the aplay command is also trying to open the same device which results in this problem as the device can only be opened once in a typical setup (it requires h/w mixing to work otherwise). You really need to play the song.wav via PulseAudio and not via the hw directly to get the results you need. Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited http://www.tribalogic.net/ Open Source: Mageia Contributor http://www.mageia.org/ PulseAudio Hacker http://www.pulseaudio.org/ Trac Hacker http://trac.edgewall.org/
