Request addition to pipewire config - auto switch

[CharlesV]

The following method turns on auto switch for newly connected bluetooth devices under XFCE. I have been using this in several MX23 xfce machines, just worked with a gent to fix his too and he recommended we add it.

It is so useful, I have had it working since MX23 ( different fix for MX21 ) and would like to request it to be added to the pipewire config. If for some reason we cannot, then possibly added to MX Tweak.

-- To get auto switch working on bluetooth in XFCE with pipewire,
Modify:

Code: Select all

/usr/share/pipewire/pipewire-pulse.conf

And under the group of:

Code: Select all

  content.exec:

Add this line:

Code: Select all

    { path = "pactl" args = "load-module module-switch-on-connect" }

Restart the computer and bluetooth devices should now automatically switch to a bluetooth device when connected.

[dolphin_oracle]

The following method turns on auto switch for newly connected bluetooth devices under XFCE. I have been using this in several MX23 xfce machines, just worked with a gent to fix his too and he recommended we add it.

It is so useful, I have had it working since MX23 ( different fix for MX21 ) and would like to request it to be added to the pipewire config. If for some reason we cannot, then possibly added to MX Tweak.

-- To get auto switch working on bluetooth in XFCE with pipewire,
Modify:

Code: Select all

/usr/share/pipewire/pipewire-pulse.conf

And under the group of:

Code: Select all

  content.exec:

Add this line:

Code: Select all

    { path = "pactl" args = "load-module module-switch-on-connect" }

Restart the computer and bluetooth devices should now automatically switch to a bluetooth device when connected.

to survive updates, probably put a copy of that .conf file under /etc/pipewire or ~/.config/pipewire.

[CharlesV]

Good call.. and thank you !

[dolphin_oracle]

will make the change tonight on my machine and see how it behaves.

does this only work for bluetooth, or also for other connections? thinking mostly about hdmi connections, but also usb headsets and such.

[CharlesV]

will make the change tonight on my machine and see how it behaves.

does this only work for bluetooth, or also for other connections? thinking mostly about hdmi connections, but also usb headsets and such.

I have only used it on bluetooth, and dont have any monitors with with speakers to try it on. I found this and the same fix for pulse audio that I used in MX 21 here:

MX 23 - Pipewire
https://alexandra-zaharia.github.io/pos ... -in-linux/
( scroll down a bit )

and
MX 21 - Pulseaudio
https://alexandra-zaharia.github.io/pos ... lly-linux/

Been so long since I did them I totally forgot until the latest post I worked on.

[m_pav]

Not that it makes any difference in function, but shouldn't the line to add into pipewire.conf follow the conventions already used?

{ path = "/usr/bin/pactl" args = "load-module module-switch-on-connect" }
instead of
{ path = "pactl" args = "load-module module-switch-on-connect" }

and I agree with DO

to survive updates, probably put a copy of that .conf file under /etc/pipewire or ~/.config/pipewire.

[Stevo]

None of the commented-out examples already in the file use the full /usr/bin path, though.

[AVLinux]

@dolphin_oracle

Would it be better as an auxiliary package instead of part of pipewire-setup-mx? Supposing it was a separate package called something like 'pipewire-bluetooth-mx' and instead of placing the conf files in /usr/share/pipewire where they could get overwritten it could place the modified conf file directly into /etc/pipewire where it would be safe.. People with bluetooth devices could install it and people without could just have the stock PipeWire setup in case the auto switch does unwanted things with normal Audio devices..?

[Stevo]

@dolphin_oracle

Would it be better as an auxiliary package instead of part of pipewire-setup-mx? Supposing it was a separate package called something like 'pipewire-bluetooth-mx' and instead of placing the conf files in /usr/share/pipewire where they could get overwritten it could place the modified conf file directly into /etc/pipewire where it would be safe.. People with bluetooth devices could install it and people without could just have the stock PipeWire setup in case the auto switch does unwanted things with normal Audio devices..?

If we wanted to make it opt-in, or default with an opt-out, I'd vote for having the setting in MX Tweak.

[dolphin_oracle]

I need to think about it. I'm inclined to make a switch for it.

FWIW, this affects all connected audio devices, not just bluetooth ones. its quit irritating when pluggin in a microphone to have all your audio switch to the mic, even the output. I'm going to guess that it might be similar for other types of connections, maybe even HDMI audio, although I haven't tested that.

does work though.