[L2Ork-dev] Flatpak build - audio backend testing

Sam Thursfield ssssam at gmail.com
Mon Jul 20 15:46:22 EDT 2020

Hi :)

On Mon, Jul 20, 2020 at 8:26 PM Jonathan Wilkes <jon.w.wilkes at gmail.com> wrote:
> 1. I haven't read the ALSA Adventure Dungeon Map in a while. Is
> "pulse" really a valid ALSA device,
> or are you reusing the "-alsaadd" interface for the purpose of
> re-routing to pulse?

It's an ALSA device implemented by a plugin, the plugin itself being
installed by PulseAudio. I haven't checked, but I guess it exists on
most/all Linuxes that ship PulseAudio.

> 2. Are you suggesting to have Purr Data on Linux default to "-alsaadd
> pulse" and to have that device
> selected by default? I think that's a good idea as newcomers will be
> able to run youtube tutorials at the
> same time as Purr Data.

Ideally, yes :)

> 3. If #2 above is the case, does anything in the Audio preferences tab
> need to change? In other words,
> are "sample rate", "block size", and "delay" still operational while
> using the pulse device?

That's a good question and I haven't yet figured out the answer. In
testing I saw some 'audio dropout' type errors which suggest things
aren't working as they should. I also got different results depending
on the blocksize. It needs more testing, and ideally input from
someone who knows more about ALSA and Pulseaudio than I do :)

> 4. With the pulse device selected and a youtube video paused, what
> happens if the user chooses a
> direct-audio-hardware-access device in the audio list and clicks "Ok?"

Probably something like this:

    snd_pcm_open (input): Device or resource busy
    snd_pcm_open (output): Device or resource busy

Followed by a lack of sound :)

More information about the L2Ork-dev mailing list