I’ve been using “Linux audio”, namely jack, Ardour, freewheeling, hydrogen e.a. for more than a decade. But you can take your shiny pipewire and shove it where the sun doesn’t shine.
Pipewire is awesome, I can’t believe they did it, they implemented all the old APIs for the other system and brought it into great harmony. But hey I’m a wayland user too
A decade ago, all distributions switched to a new sound stack that is better by all metrics. He is saying he is old and knows the name of the old stuff, therefore new stuff bad
The pipewire switch happened far more recently than a decade ago, you may be thinking of pulseaudio, which had far more valid criticisms than pipewire does now.
You’re an idiot who doesn’t know what you’re talking about. Pipewire isn’t really up for production (and by far not a decade old) and whoever decided to activate it by default might have had easy desktop use and switching to BT or mobile audio trash in mind. If it comes to latency, low complexity or reliability, pipewire is terrible. It also doesn’t add anything useful that jack could not do, it only adds complexity where it’s not needed.
PW is nice, if you’re a newbie and want all your crappy BT shit to connect from the desktop so you can watch five tik-tok vids at the same time using you shiny “soundbar” (and have your voice comm blasting the neighbourhood), but it’s a mess if you want to use realtime audio with more than two ports, MIDI and a device chain for recording or playback.
Don’t matter replying, “Qwel”, I put you in my special place for trolling, abusive children who do not contibute to civilization - the killfile.
seems to me like you’re the troll. people who are advanced enough to want to use MIDI controllers and whatnot are advanced enough to just silently use the tools that work for them
Not strictly an issue in that sense, but I am a musician that heavily uses software monitoring for guitars and vocals, meaning I rely on the lowest latency possible to play back the input.
Pipewire just isn’t quite there on the performance level of jack, but I also use realtime kernels and CPU governors to further reduce latency issues, so this is an extreme use case.
While the guy you replied to seens a bit unhinged, I have to agree that pipewire isn’t the holy grail some people make it out to be, but I guess it’s a better solution than pulse audio for 99% of general users.
I don’t know much about “bluetooth instruments”, the question is what’s meant by that, exactly. There are wireless units for mics and guitars, but they are usually connected to an amp directly, so there is only one way transmission, which may be fine with a bit of latency.
When you use your computer as a digital amp/effects processor, you get a roundtip latency, e.g. from the input into a AD converter, to digital processing and back through a DA into the speakers.
That means you basically have doubled the internal latency and the more effects you use in parallel, the tighter the timings have to be.
With jack on an optimised system, I get anything between 4-8ms of total latency. Anything below 20ms is generally considered “fine”, but you can hear it, depending on your subjective brain and ears. I would say I notice anything above 10ms already, but I’ve played with 16+ when I started and it worked for pracitsing.
I’ve been using “Linux audio”, namely jack, Ardour, freewheeling, hydrogen e.a. for more than a decade. But you can take your shiny pipewire and shove it where the sun doesn’t shine.
Pipewire is awesome, I can’t believe they did it, they implemented all the old APIs for the other system and brought it into great harmony. But hey I’m a wayland user too
WAYYYYLANDDDDDD SHAKES FIST IN AUTOHOTKEY
I understand a couple of those words!
A decade ago, all distributions switched to a new sound stack that is better by all metrics. He is saying he is old and knows the name of the old stuff, therefore new stuff bad
The pipewire switch happened far more recently than a decade ago, you may be thinking of pulseaudio, which had far more valid criticisms than pipewire does now.
Oh. In my head both had happened in close succession
You’re an idiot who doesn’t know what you’re talking about. Pipewire isn’t really up for production (and by far not a decade old) and whoever decided to activate it by default might have had easy desktop use and switching to BT or mobile audio trash in mind. If it comes to latency, low complexity or reliability, pipewire is terrible. It also doesn’t add anything useful that jack could not do, it only adds complexity where it’s not needed.
PW is nice, if you’re a newbie and want all your crappy BT shit to connect from the desktop so you can watch five tik-tok vids at the same time using you shiny “soundbar” (and have your voice comm blasting the neighbourhood), but it’s a mess if you want to use realtime audio with more than two ports, MIDI and a device chain for recording or playback.
Don’t matter replying, “Qwel”, I put you in my special place for trolling, abusive children who do not contibute to civilization - the killfile.
Sir, this is a Wendy’s
seems to me like you’re the troll. people who are advanced enough to want to use MIDI controllers and whatnot are advanced enough to just silently use the tools that work for them
Say hello to Mr Killfile…
deleted by creator
I do, in fact, not know what I am talking about. Is there actually some sound engineers or musicians that are having real-life issues with it ?
Not strictly an issue in that sense, but I am a musician that heavily uses software monitoring for guitars and vocals, meaning I rely on the lowest latency possible to play back the input.
Pipewire just isn’t quite there on the performance level of jack, but I also use realtime kernels and CPU governors to further reduce latency issues, so this is an extreme use case.
While the guy you replied to seens a bit unhinged, I have to agree that pipewire isn’t the holy grail some people make it out to be, but I guess it’s a better solution than pulse audio for 99% of general users.
Oh wow. How much time does the whole input-processing-output takes? I would have thought it would be so fast that you couldn’t notice it
Some musicians assured me that using bluetooth instrument was fine in terms of delay, wouldn’t that absolutely blow up all the cool kernel tuning?
I don’t know much about “bluetooth instruments”, the question is what’s meant by that, exactly. There are wireless units for mics and guitars, but they are usually connected to an amp directly, so there is only one way transmission, which may be fine with a bit of latency.
When you use your computer as a digital amp/effects processor, you get a roundtip latency, e.g. from the input into a AD converter, to digital processing and back through a DA into the speakers.
That means you basically have doubled the internal latency and the more effects you use in parallel, the tighter the timings have to be.
With jack on an optimised system, I get anything between 4-8ms of total latency. Anything below 20ms is generally considered “fine”, but you can hear it, depending on your subjective brain and ears. I would say I notice anything above 10ms already, but I’ve played with 16+ when I started and it worked for pracitsing.
Here, you’re not you when you’re hungry