Sergei, Paul, list...
On Sep 9, 2014 11:01 AM, "Sergei Steshenko"
wrote:
>
> What you want is impossible in principle, regardless of PulseAudio
specifically (i.e my statement applies to any kind of sound server with
similar functionality) and ALSA speicifically (i.e my statement applies to
any ki
What you want is impossible in principle, regardless of PulseAudio
specifically (i.e my statement applies to any kind of sound server with similar
functionality) and ALSA speicifically (i.e my statement applies to any kind of
direct HW access interface).
The point is that for an HW device to f
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
wrote:
>
>
>
> Fri, 5 Sep 2014 09:38:54 -0700 от "Paul A. Steckler" :
>
> I have an app that u
Fri, 5 Sep 2014 09:38:54 -0700 от "Paul A. Steckler" :
>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.
>
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
