PipeWire integration discussion?

[AVLinux]

@dolphin_oracle

I found a typo in the pipewire setup Control file and another pulseaudio module conflict that needs to be added. In the existing Control file 'pulseaudio-modules-bluetooth' is a typo, the package is actually 'pulseaudio-module-bluetooth'...

Secondly if the User has 'pulseaudio-module-jack' installed it will not work with PipeWire so it should also be listed as a Conflict...*Note this won't have any negative effect on MX Users because it is not installed in MX by default but it is in AV Linux..

Suggested changes:

Code: Select all

Package: pipewire-setup-mx
Version: 22.10.22
Architecture: all
Maintainer: Dolphin Oracle <dolphinoracle@gmail.com>
Installed-Size: 96
Depends: pipewire (>= 0.3.58), pipewire-alsa, pipewire-pulse, pipewire-jack, gstreamer1.0-pipewire, wireplumber, libspa-0.2-bluetooth, libspa-0.2-jack
Conflicts: pulseaudio-module-bluetooth, pulseaudio-module-jack
Provides: pulseaudio
Section: system
Priority: optional
Description: pipewire setup for sysVinit and/or systemd

[dolphin_oracle]

Ok thanks.


The autostart entry doesn’t seem to work on kde. Got to figure that out

[AVLinux]

Ok thanks.


The autostart entry doesn’t seem to work on kde. Got to figure that out

Actually, I've been having some issues getting sysvinit working as well, I haven't troubled you about it yet because I haven't tested it on a pure MX install yet and so far testing has been in an Enlightenment VM. What's interesting is that PipeWire systemd is working perfectly there so perhaps the sysvinit issue is not D.E. related, just mentioning it now since the other post has come to light. Maybe what you come up with will work on all D.E's. Happy to test! What is @anticapitalista doing on the antiX side with PipeWire without systemd?

[dolphin_oracle]

Ok thanks.


The autostart entry doesn’t seem to work on kde. Got to figure that out

Actually, I've been having some issues getting sysvinit working as well, I haven't troubled you about it yet because I haven't tested it on a pure MX install yet and so far testing has been in an Enlightenment VM. What's interesting is that PipeWire systemd is working perfectly there so perhaps the sysvinit issue is not D.E. related, just mentioning it now since the other post has come to light. Maybe what you come up with will work on all D.E's. Happy to test! What is @anticapitalista doing on the antiX side with PipeWire without systemd?

unless Enlightenment processes autostart entries in /etc/xdg/autostart, you would need to add a autostart entry in whatever way enlighttenment has. for isntance fluxbox would be in ~/.fluxbox/startup.

[AVLinux]

Ok thanks.


The autostart entry doesn’t seem to work on kde. Got to figure that out

Actually, I've been having some issues getting sysvinit working as well, I haven't troubled you about it yet because I haven't tested it on a pure MX install yet and so far testing has been in an Enlightenment VM. What's interesting is that PipeWire systemd is working perfectly there so perhaps the sysvinit issue is not D.E. related, just mentioning it now since the other post has come to light. Maybe what you come up with will work on all D.E's. Happy to test! What is @anticapitalista doing on the antiX side with PipeWire without systemd?

unless Enlightenment processes autostart entries in /etc/xdg/autostart, you would need to add a autostart entry in whatever way enlighttenment has. for isntance fluxbox would be in ~/.fluxbox/startup.

Yes it has it's own method of autostart and I had tried that, also running pipewire-start manually, it doesn't seem to work either, the script runs but pactl info still shows pulseaudio alone as the Audio server...? Any this is all off spec. Perhaps what you find in MX KDE will be applicable here too. I don't expect you to fix my Enlightenment issue unless the fix for KDE fixes both..

[dolphin_oracle]

On kde, wireplumber is not startuping up, even under systemd. maybe I missed a step somewhere.

[AVLinux]

On kde, wireplumber is not startuping up, even under systemd. maybe I missed a step somewhere.

What are the errors? I believe 'wpctl status' should show you the running clients etc.. I will be out until this evening unfortunately, will check back asap

[dolphin_oracle]

no errors, it wasn't running at all. looks like I might need to enable the systemd service for wireplumber.

I feel that's going to be a moving target over time.

on the KDE autostart entry, changing the desktop file to launch the pipewire-start script with

Code: Select all

bash -c "pipewire-start" cleared that up.  will update the autostart desktop entry.

[alextone]

Woohoo, EFL volume control works. Now i can adjust volume from the keyboard.

Onwards and upward.

(systemd)

[dolphin_oracle]

so the systemd --user service for wireplumber was enabled, it was just failing to launch, complaining of missing DISPLAY variable. I made a special autostart entry for KDE for wireplumber that launches wireplumber on systemd.

Now, it could be my test system hosed, but its a pretty fresh install so I don't think so. and the issue will likely be fixed in future KDE for debian 12, so its something to keep an eye on. On Xfce systemd there was no issue at all.

so new package now, with the autostart entries working for me at least in both KDE and Xfce. (attached).

sending it to tim for the test repo.