Comments by "Lawrence D’Oliveiro" (@lawrencedoliveiro9104) on "Let's Shell Script Together: Case statements, audio control and more" video.

  1. 1:11 It’s actually unnecessary to use the PulseAudio-specific commands, if you want a script that works both ways. The Alsa amixer command still works under PulseAudio.
    3
  2. 14:33 The trouble with that technique is that it returns true even if the pulseaudio server is running for a different user.
    3
  3. 6:35 You realize that continual polling of the volume setting is quite unnecessary? For example, on KDE, I get D-Bus signals broadcast to all listeners on the per-user session bus to notify them of useful things like volume changes. So interested processes can simply listen for the relevant signals.
    1
  4. 1:00 PulseAudio bloat?!? But, but it’s in Slackware now!
    1
  5. 14:01 Don’t do it that way. The more reliable way would be to use a client tool like pactl, ignore the output, and see if it succeeds (PulseAudio is running) or not, e.g. pactl info &>/dev/null && echo yes || echo no outputs “yes” if PulseAudio is running, “no” if not.
    1