Post

Since switching to Linux on my MacBook, I've been running Discord and some other apps as Chrome Web apps. It's nice that you can easily wrap any page into its own launcher icon. What's not so nice is that all apps' audio streams just end up as "Chromium" in the system.

This is especially annoying if you want Discord or Slack to always output on your headphones, and a music streaming page on a different output. The Linux audio system supports this, but since everything just ends up as "Chromium", all new audio is always routed to the last selection.

So now I have a local fork of ungoogled-chromium that actually sets the correct pulseaudio properties for each audio stream. It dynamically updates the stream label when the document title changes and it ensures that the correct app information for web apps is set.

There's actually an open Chromium issue about this: issues.chromium.org/issues/45041... issues.chromium.org/issues/41346... Which is where I started. It mentions updating the pulse stream information after creating the stream.

The issue with that is that if you want to have some rules applied like "always route Discord to my headphones", such rules only work when the stream is initially created. It took me quite some back and forth, recompiling Chromium, and testing to have something that reliably works.