[Vm-dev] pulse audio default is not suitable for PI package

Tobias Pape Das.Linux at gmx.de
Thu Apr 23 08:49:25 UTC 2020

Hi  tim

> On 21.04.2020, at 23:02, tim Rowledge <tim at rowledge.org> wrote:
> The recent change to default pulseaudio for linux VM packages may not be a very good idea for the Raspbian Pi system. I know we've some ... issues... with ALSA that have made for very unhappy people at times but at least in the Pi world pusleaudio is not considered any improvement. So much so that it is not included in the distro.
> See https://www.raspberrypi.org/forums/viewtopic.php?t=256225#p1562939 for a more or less official comment.
> Given that, I'd urge not setting that default for the linuxARM packages.

Coming back to the original thing here, 
When the VM and the plugins are complied correctly, using default Raspbian should not be a problem.
Because when Pulseaudio is not installed, the VM will skip loading it...

Can someone please check that?

BTW: Pulseaudio is currently _not_ the "default" sound plugin. The list goes as follows:

  { &displayModule, "display", "Quartz" },	/* defaults... */
  { &soundModule,   "sound",   "OSS"    },
  { &soundModule,   "sound",   "MacOSX" },
  { &soundModule,   "sound",   "Sun"    },
  { &soundModule,   "sound",   "pulse"  },
  { &soundModule,   "sound",   "ALSA"   },
  { &soundModule,   "sound",   "null"   },

Ie, OSS -> MacOSX -> Sun -> pulseaudio -> Alsa -> no audio

Under the assumption that a plugin is skipped when its system is not available[1]
I would like to propose the following now:
	pulse -> alsa -> oss -> sndio -> macos -> sun -> no audio.

Best regards

[1]: I have a hunch that this is not completely the case. Rather 
     plugins are skipped when the sound system _libraries_ are not available.
     For example, if you do not have pulseaudio installed _but_ you have libpulse installed
     I think the vm will pick pulse regardless but will fail to play.
     Do I see this right?

More information about the Vm-dev mailing list