Two feature requests of mine have been realised:
From Version 0.3.66 there is a filter that can phase invert, making it possible to run a virtual balanced setup on any multichannel sound card. Very nice for if you have a soundcard with extra stereo channels you're not using and an amp or speakers with balanced inputs.
If you add the filter to your config file/folder it will show up in qpwgraph. Then you wire it up like this:
That's all you need to do to convert a stereo unbalanced output to a virtual balanced one. Of course you should gain match the channels exactly for optimum effect. In the screenshot I didn't do that - I just wanted a quick demo.
Another feature request of mine, manual specifications of biquads in the filter chain has just been merged into the main branch. It will most probably be included in the next release. This will allow users to specify a set of biquads per samling rate, where pipewire will pick the one closest to the curent sampling rate.
I'm going to use this for RIAA deemphasis. But with biquads, anything (IIR) goes 😎
Once again I can only encourage use of the pipewire bug tracker. The developers are really friendly and open to suggestions. My obscure use cases seem to be interesting enough for the project lead to implement into the project. Thank you Wim!
From Version 0.3.66 there is a filter that can phase invert, making it possible to run a virtual balanced setup on any multichannel sound card. Very nice for if you have a soundcard with extra stereo channels you're not using and an amp or speakers with balanced inputs.
If you add the filter to your config file/folder it will show up in qpwgraph. Then you wire it up like this:
That's all you need to do to convert a stereo unbalanced output to a virtual balanced one. Of course you should gain match the channels exactly for optimum effect. In the screenshot I didn't do that - I just wanted a quick demo.
Another feature request of mine, manual specifications of biquads in the filter chain has just been merged into the main branch. It will most probably be included in the next release. This will allow users to specify a set of biquads per samling rate, where pipewire will pick the one closest to the curent sampling rate.
I'm going to use this for RIAA deemphasis. But with biquads, anything (IIR) goes 😎
Once again I can only encourage use of the pipewire bug tracker. The developers are really friendly and open to suggestions. My obscure use cases seem to be interesting enough for the project lead to implement into the project. Thank you Wim!
Last edited:
If anyone is interested, I figured out how to make pipewire default to 96kHz/32bit and upsample...
I built it on Manjaro, then refined it in Arch.
Warning - Pipewire output is borked on Manjaro Unstable right now... It feeds back on itself and sounds like crap. Stay with stable for now.
My first git repo 🙂
Check it out here --> https://github.com/k0d4/pipewire96.git
I built it on Manjaro, then refined it in Arch.
Warning - Pipewire output is borked on Manjaro Unstable right now... It feeds back on itself and sounds like crap. Stay with stable for now.
My first git repo 🙂
Check it out here --> https://github.com/k0d4/pipewire96.git
So this sets the default sampling rate to 96k in pipewire.conf and then bumps up the resampling quality to 15 on both alsa and pulseaudio clients? I'm probably missing something but it's hard to tell without making a diff between the original files and your changes. Anyway, good work and thank you for sharing 🙂