It'd be theoretically possible to make this a #pipewire filter I think but I have no idea how.
#PipeWire
So #sendspin seems to become support in #pipewire 😍
https://gitlab.freedesktop.org/wtaymans/pipewire/-/commits/sendspin
@jmorahan good idea putting meters on the monitor.
I just checked out Easy Effects and if it could do VST3s, that would be awesome. Seems the difference between Easy Effects and Carla, is that Easy Effects creates a dedicated sink, which keeps the connection to ex. the music app, even if a number is changed.
If I route from the music app to Carla (or Bitwig/Ardour), it loses the connection when a new track starts playing.
I have to look more into this. It's interesting.
So, when I play back a music in #Audacity via the #ALSA interface of #Pipewire, it is roughly 3dB* more quiet than when I play back the same piece from my #DAW / #Ardour via the #Jack interface. When I play back the file in good old Clementine player via Jack, it's also as it should be.
Things like this make me nervous. Okay I exported my music from Ardour or #Mixbus in the current case, just wanna check the file again, so Audacity… and then it all of sudden sounds differently.
*: I have a digital audio console with peak-hold meters at the other end, so it's not just by ear.
I have a #Pipewire question: I wanted to use a couple of meters through Carla, when listening to music on the Gnome Music app, and it seems, that everytime I change my tune, Pipewire drops the connection from Music to Carla, and resets to the speaker instead.
Would it be possible to lock the connection between Music and Carla when both apps are open?
The "Pro Audio" profile in #Pipewire has vanished for my #mAudio #airHub.
I have Pipewire 1.4.10 from a PPA. on #UbuntuStudio 24.04
I don't have time right now to look into this. But things like this make me nervous. What if this happens on my Laptop just the day I need to record a show from a digital console via USB?
"Pro Audio" also went away for my 100% professional and much needed Dante AVIO USB audio interface. WTF?
EDIT: So, I ran the UbuntuStudio audio config something and selected "switch configuration" and found out I was not using Pipewire at all! I was using only PulseAudio. Which has no Pro Audio of course. The really crazy thing about this however is: Something made the switch automatically, likely by (un)installing some packages. It's kind of a dark magic! This is Windows 11 behavior, not #Linux… argl!
FINALLY i made it work under #Rocky #Linux 9 ! Using #SWH's audio plugins ( #LV2 and/or #LADSPA ) under #PipeWire to "smooth out" audio loudness in a "set and forget" way. For #Rocky9 / #Rhel9 / #OL9 see my solution at https://awerner.myhome-server.de/doku.php?id=it-artikel:linux:how-to-enable-audio-normalization-a.k.a.-audio-compression-a.k.a.-audio-dynamic-range-compression-under-pipewire-using-ladspa-swh-plugins-rocky9 . For #Debian based Systems use https://awerner.myhome-server.de/doku.php?id=it-artikel:linux:how-to-enable-audio-normalization-a.k.a.-audio-compression-a.k.a.-audio-dynamic-range-compression-under-pipewire-using-lv2-swh-plugins-debian
Bit of a longshot today!
Anyone using #pipewire with #reaper and a Mackie #MCU?
It almost works but not quite, all the buttons and faders are responding, but the MCU display isn't showing anything (well it's stuck on the 'boot screen' - MACKIE CONTROL UNIVERSAL- etc).
@pipewire is otherwise excellent (easy to use, low latency etc etc), but this apparent snag with #MIDI handling is something of a fly in the ointment.
My audio output in my Fedora device is getting choppy when I use my browser. I guess it's time to contribute on #pipewire
It bothered me that #PipeWire didn't switch to my headset microphone when I plugged it in.
So last week, I figured out how to do that automatically! Here's how:
@vermaden @omar
I always use alsamixer -c0 up to cxx from the OSS ALSA period since it's ncurses based & faster than GUI programs.
Many things in Linux were changed for good reason, but some are questionable. I don't use systemD init is easier to maintain. It aint broke so KISS
Pipewire is fun to add FX in my signal chain to my DAW, but for serious work I have a physical FX rack.
I love pavucontrol
I understand why Wayland was made and only have it on my SBC Raspberry Pi5
#Ifconfig #ip #init #systemD #Xorg #Wayland #programming #pipewire #ALSA #OSS
So software vendors: Support Pipewire already. Support the transition of these functions in the development of Linux.
This seems like the Xorg / Wayland fight all over.
"We can't support it, it's not good enough yet"
- But then support it and make it good. You are missing out on competent people joining (y)our community because the price of joining is too high.
It becomes this negative circle, where vendors choose not to support Pipewire natively. But all the distros turn to Pipewire to make things easier. It just keeps getting more confusing.
And when the longtime software users don't need pipewire, because it doesn't support their specific needs, then they wont support suggestions from new users to get native pipewire - because you can do all that already, you just need to do write these terminal commands and gedit this file.
Then another might be trying out Reaper, using ALSA, and suddenly all other sound of the computer stops working, when Reaper is taking control of the audio interface.
We look into Jack, ALSA, Pipewire. Get confused. What's the driver we would normally get from the interface vendor. We don't know?
We find articles (or comments) of people still using Jack. It's the low latency standard. Or ALSA, so there is direct connection between software and interface.
In comes music producers new til Linux, install Bitwig (with native pipewire support), flip the "Pro audio" switch in the audio settings app and starts producing without any trouble. We open a browser in the background, listen to a little music, while still in Bitwig (because this is what we're used to on MacOS), and thinks pipewire is awesome. No specific needs, just a class compliant audio interface which is found and routed without much trouble.
Finally got sound working on #openSUSE on my new notebook. After spending a lot of time trying to figure out what is wrong (checking drivers, rights, #pipewire configuration, ...), the culprit was`wireplumber-video-only-profile` that was installed for some reason 🤦Uninstalled it and now everything works 🙄
Canonical Ubuntu 26.04 is likely shipping pipewire as a snap.
"We have a roadmap. One of the things we're looking at for 26.04 is shipping Pipewire as a Snap on the desktop. Now this is a bit of a risky move, because there is a crowd of people who love to say that the first thing they do on Ubuntu is remove snapd, and if they do that on this future release, they'll have no sound. Why start with Pipewire? Well, it interacts with things like cameras, so it would allow us to more easily backport support for newer cameras and speakers to Ubuntu."
Jon Seager, VP of Engineering, talks exclusively to The Reg
Source: https://www.theregister.com/2025/11/03/canonical_jon_seager_qa/
I made a call for help regarding Pipewire recently. And got some retoots. Thx for that.
Sadly i have to push that issue again.
I run Open Sound Meter which comes as an AppImage.
Issue:
Somehow OSM doesn't connect to Pipewire but to the audio interface directly. So it doesn't show up in the pw patchbay.
There was a suggestion to configure pipewire-alsa. I found zero helpful information on that matter. Just the general documentation that lists a lot but tutors not so much.
Any hint appreciated.
#Pipewire #wireplumber #AppImage #opensoundmeter #linux #linuxaudio #linuxaudioproduction
Client Info
Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst