Recently, I had the opportunity to work with a customer that required customization of WirePlumber’s
configuration for use in their embedded Linux system. Oftentimes, people are confused about how to
customize WirePlumber for their use case. I thought I’d take this opportunity to discuss how it was
configured in this particular case and why.
PipeWire 1.4 is almost out of the door!
One of the highlights of the new release — which I personally worked on and presented also recently on my
FOSDEM talk —
is Bluetooth telephony support.
Last week I attended the
GStreamer spring hackfest
in Thessaloniki. It was very nice to meet all the usual people again, as it’s been
a while (I last attended a GStreamer event in 2022), and we had a great time!
I’ve been quiet about WirePlumber for a significant amount of time. It was back
in 2022 when after a series of issues were found in its design, I made the call
to rework some of its fundamentals in order to allow it to grow. I mentioned
this in the Collabora blog
at the time. And long story short, the year now is 2024 (time flies, who
knew?!).
A couple of weeks ago, back in October, the nice people of
Automotive Grade Linux asked me if it would
be possible to add some “bass” and “treble” controls on the audio output of the
AGL In-Vehicle Infotainment demo image, using PipeWire. I knew, of course, that
it’s perfectly doable using filters and I knew that PipeWire ships with the
filter-chain module, which can do wonders in that regard. But what I didn’t know
was how to configure it exactly for this particular job. To figure this out, I
embarked on my first ChatGPT coding adventure…
