gnome-shell-volume-mixer

gnome-shell-volume-mixer copied to clipboard

Hi, My PA session is as a frontend to a JACK backend, and so cardinfo.py returns {} and the extension attempts to automatically disable itself.

Can I ask why cards were chosen as the target rather than Sinks? Another bug seems to cause the extension to not actually disable itself, and it otherwise works great using the description of each configured sink correctly.

I'd be happy to try and fix the script so it represents my use case better, but I don't quite understand why it's currently set up this way.

Cheers!

The PA cards are an actual requirement for switching profiles, made necessary by the lack of marshalled GJS objects for GVS mixer / card profiles and a very hard crash caused by accessing them.

Your setup seems "special" to me as in "no GNOME distribution comes with that setup by default". If you come up with a solution that doesn't break a default PA setup and works with JACK I'll be glad to merge your pull requests!

seems to cause the extension to not actually disable itself

As far as I know an extension cannot completely disable itself. I can only disable the functionality (via the same calls that GNOME Shell would execute) but the extension would still seem to be enabled.

Oh, and I'd very much appreciate if you could provide a setup instruction I can reproduce in a VM to test JACK/PA/volume-mixer integration (or even provide a preconfigured VM image for qemu/KVM).

There are so many ways to configure sound and mixing in Linux, I doubt I'd get it right. ;)

Oh it's definitely special. I think if I was to write this myself i'd make it two layered, iterate Sinks then iterate their Device attributes.

I can't expect you to do it for me but I am also jobseeking so I shall give it a go, but slowly :)

Take your time and don't hesitate to shoot questions at me! (We can also take this on Matrix, @aleho:matrix.hofpower.net)

i have a sort of similar issue and get an error saying: "Querying PulseAudio cards failed, disabling extension". The problem came up after i updated to gnome version 41.1 on manjaro. I don't think i have a special setup really i did once mess around with some sound settings but all i did was change my default profile to a2dp sink on some bluetooth headphones so i'm not sure what's causing the issue here sadly.