PipeWire 1.0.0 for MX-23 main?

[siamhie]

I just sent a revised pipewire-setup-mx package up to the test repo (should show up soonish).

it requires pipewire >= 1.0. I also recommend updated wireplumber, which might actually be where the volume fix under systemd resides.

I wasn't sure which package to upgrade so I upgraded all of them. I'll keep an eye out for the setup package.

pipewire.png

[AVLinux]

Actually in some further testing today I can reproduce 'the 40% issue' @siamhie brought up even with PW 1.0.0 and Wireplumber 4.16... It doesn't happen on reboot but it does on Logout (like siamhie said) when using systemd. I'm using lightDM with Enlightenment but I don't think the D.E. or login manager is relevant with this issue anyway. I wouldn't even call it a bug really just a minor annoyance but it would appear it is still in PW 1.0.0..

Here's my Audio info:

Code: Select all

DevVM@AVL-MXE-VM:~
$ pactl info
Server String: /run/user/1000/pulse/native
Library Protocol Version: 35
Server Protocol Version: 35
Is Local: yes
Client Index: 217
Tile Size: 65472
User Name: DevVM
Host Name: AVL-MXE-VM
Server Name: PulseAudio (on PipeWire 1.0.0)
Server Version: 15.0.0
Default Sample Specification: float32le 2ch 48000Hz
Default Channel Map: front-left,front-right
Default Sink: alsa_output.pci-0000_00_05.0.analog-stereo
Default Source: alsa_input.pci-0000_00_05.0.analog-stereo
Cookie: cab0:ee0e

Further to that on another system I tried the updated 'pipewire-setup-mx' package that @dolphin_oracle made for MX-Test and on a system with the default Debian PipeWire 0.3.65 installing only the pipewire-setup-mx package successfully pulled in all the correct dependencies for PipeWire 1.0.0 and ugraded without a hitch so that is working well!

[siamhie]

Actually in some further testing today I can reproduce 'the 40% issue' @siamhie brought up even with PW 1.0.0 and Wireplumber 4.16... It doesn't happen on reboot but it does on Logout (like siamhie said) when using systemd. I'm using lightDM with Enlightenment but I don't think the D.E. or login manager is relevant with this issue anyway. I wouldn't even call it a bug really just a minor annoyance but it would appear it is still in PW 1.0.0..

It is just a nuance. If you happen to have two users share the computer and one logs out of the desktop so that the other logs in, you get the volume reset to 40% if you boot with systemd.
Same thing happens in KDE with SDDM, so it's definitely not a login manager issue either. I just wish I could find the config file that sets the volume to 40% initially so that I could maybe change
it to 70% for testing purposes.


One thing puzzles me. When I open alsamixer the default device is set to pipewire (as it seems)

pipewire.jpg

and not my onboard audio device (F6)

realtek.jpg

[dolphin_oracle]

Actually in some further testing today I can reproduce 'the 40% issue' @siamhie brought up even with PW 1.0.0 and Wireplumber 4.16... It doesn't happen on reboot but it does on Logout (like siamhie said) when using systemd. I'm using lightDM with Enlightenment but I don't think the D.E. or login manager is relevant with this issue anyway. I wouldn't even call it a bug really just a minor annoyance but it would appear it is still in PW 1.0.0..

It is just a nuance. If you happen to have two users share the computer and one logs out of the desktop so that the other logs in, you get the volume reset to 40% if you boot with systemd.
Same thing happens in KDE with SDDM, so it's definitely not a login manager issue either. I just wish I could find the config file that sets the volume to 40% initially so that I could maybe change
it to 70% for testing purposes.


One thing puzzles me. When I open alsamixer the default device is set to pipewire (as it seems)

pipewire.jpg


and not my onboard audio device (F6)

realtek.jpg

that is what alsamixer is supposed to look like.

[AVLinux]

[that is what alsamixer is supposed to look like.

@siamhie

It's actually by default telling you what has 'claimed' the hardware which should be whatever core Audio system you have running at boot.. F6 is showing you the supported Hardware Devices to select and then F3-F5 are showing you the available Hardware Controls on the devices, so each View in Alsamixer is a different aspect of the ALSA system..

[siamhie]

[that is what alsamixer is supposed to look like.

@siamhie

It's actually by default telling you what has 'claimed' the hardware which should be whatever core Audio system you have running at boot.. F6 is showing you the supported Hardware Devices to select and then F3-F5 are showing you the available Hardware Controls on the devices, so each View in Alsamixer is a different aspect of the ALSA system..

@AVLinux OK, that makes sense. I booted up a Debian 12 Gnome live ISO and got the same thing.

deb12.png

@dolphin_oracle I going to put to bed the audio drop when logging out of the desktop and then logging back in.
I booted up a Debian 12 Gnome live ISO and when I logged out of the desktop and then back in, the volume dropped back down to the default level.
They are using pipewire version 0.3.65 and systemd for the init.

I still find it strange the volume level drops back to default when booted up in systemd but not when booted to sys-v.

[AVLinux]

Just a (probably not so) gentle reminder..

Can any other Users comment on if PipeWire 1.0.0 installed from MX-Test or the updated 'pipewire-setup-mx' Package in MX-Test is working as expected? I have upgraded several test VM's and a few Live test boots with no issues but it would be great to hear if anyone else has seen any issues, thanks!

[alextone]

Just a (probably not so) gentle reminder..

Can any other Users comment on if PipeWire 1.0.0 installed from MX-Test or the updated 'pipewire-setup-mx' Package in MX-Test is working as expected? I have upgraded several test VM's and a few Live test boots with no issues but it would be great to hear if anyone else has seen any issues, thanks!

Even after refreshing, pipewire in test shows up as version 0.379. Pipewire-setup-mx shows up, but I don't know which version it will attempt to install.

[AVLinux]

Just a (probably not so) gentle reminder..

Can any other Users comment on if PipeWire 1.0.0 installed from MX-Test or the updated 'pipewire-setup-mx' Package in MX-Test is working as expected? I have upgraded several test VM's and a few Live test boots with no issues but it would be great to hear if anyone else has seen any issues, thanks!

Even after refreshing, pipewire in test shows up as version 0.379. Pipewire-setup-mx shows up, but I don't know which version it will attempt to install.

I would imagine your issue is that to my knowledge you are still using MXDE-EFL which is based on MX-21, PipeWire 1.0.0 in only in MX-23 Test, MX-21 Test has 0.3.79. Even I wasn't able to test PipeWire 1.0.0 until I had AVL-MXE 23 ISO's completed enough to boot..

[dolphin_oracle]

quick question>

when running the updated pipewire AND pipewire-setup-mx from the test repo, do you get a beep when you access the Xfce logout menu?