$thing today”, when $thing was something incredibly stupid and/or painful. 🥴
$thing today”, when $thing was something incredibly stupid and/or painful. 🥴
$thing today”, when $thing was something incredibly stupid and/or painful. 🥴
btw, there are two main reasons why I’m doing this:
1. I’m using LADSPA filter chains on a regular basis. I almost always run an EQ and for movies I put a compressor on top of it. Problem is, this introduces a lot of “pauses” in PulseAudio: When I hit “play”, it takes several seconds until the audio finally starts to play. You can get used to it, but it’s annoying.
2. I have multiple audio interfaces and one of them is currently dedicated to JACK. JACK and PulseAudio are two different worlds (both run on top of ALSA). Some clients support JACK, others don’t, and it’s all really messy. PipeWire claims to be compatible with plain ALSA, PulseAudio, and JACK, so I hope I can finally “unify” all this and just have *one* audio system.
So far, it’s looking pretty promising. 🤔
btw, there are two main reasons why I’m doing this:
1. I’m using LADSPA filter chains on a regular basis. I almost always run an EQ and for movies I put a compressor on top of it. Problem is, this introduces a lot of “pauses” in PulseAudio: When I hit “play”, it takes several seconds until the audio finally starts to play. You can get used to it, but it’s annoying.
2. I have multiple audio interfaces and one of them is currently dedicated to JACK. JACK and PulseAudio are two different worlds (both run on top of ALSA). Some clients support JACK, others don’t, and it’s all really messy. PipeWire claims to be compatible with plain ALSA, PulseAudio, and JACK, so I hope I can finally “unify” all this and just have *one* audio system.
So far, it’s looking pretty promising. 🤔
btw, there are two main reasons why I’m doing this:
1. I’m using LADSPA filter chains on a regular basis. I almost always run an EQ and for movies I put a compressor on top of it. Problem is, this introduces a lot of “pauses” in PulseAudio: When I hit “play”, it takes several seconds until the audio finally starts to play. You can get used to it, but it’s annoying.
2. I have multiple audio interfaces and one of them is currently dedicated to JACK. JACK and PulseAudio are two different worlds (both run on top of ALSA). Some clients support JACK, others don’t, and it’s all really messy. PipeWire claims to be compatible with plain ALSA, PulseAudio, and JACK, so I hope I can finally “unify” all this and just have *one* audio system.
So far, it’s looking pretty promising. 🤔
So far, it has been a surprisingly good experience. PipeWire appears to “just work”.
It’s really great to have just one sound server for everything. This was really messy before … Crazy that I had put up with that. 😅
So far, it has been a surprisingly good experience. PipeWire appears to “just work”.
It’s really great to have just one sound server for everything. This was really messy before … Crazy that I had put up with that. 😅
So far, it has been a surprisingly good experience. PipeWire appears to “just work”.
It’s really great to have just one sound server for everything. This was really messy before … Crazy that I had put up with that. 😅
i recently rebuilt and included pipewire. my hesitation was that implementation a while back when they tried to layer pipewire on top of pulseaudio in one of the arch variants. multiple times a day i had to disconnect my speakers and reconnect. miserable existence.