Well, I meant, keep PulseAudio running, but still use ALSA without using the PulseAudio server device, which other applications may want to use. -- Paul On Mon, Sep 8, 2014 at 4:11 PM, Sergei Steshenko <steshenko_sergei@xxxxxxx> wrote: > > > > Fri, 5 Sep 2014 09:38:54 -0700 от "Paul A. Steckler" <steck@xxxxxxxxxxxxx>: > > I have an app that uses the ALSA library on Linux. > > The app calls snd_pcm_open() to open the capture device. Currently, > I use "default" as the name of the device. According to "arecord -L", the > default device is the PulseAudio server. > > Is there a way to bypass PulseAudio, and communicate with the > hardware directly? > > I've tried using "sysdefault" and "hw:0,0" as the name of the device, > and in both cases, I get an error that the device is busy. Is that because > PulseAudio has monopolized the device? > > -- Paul > > > "Is there a way to bypass PulseAudio" - one can (simply) stop PulseAudio > server, e.g.: http://jan.newmarch.name/LinuxSound/Sampled/PulseAudio/ -> > http://www.linuxplanet.com/linuxplanet/tutorials/7130/2 . > > Regards, > Sergei. ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ Alsa-user mailing list Alsa-user@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-user
