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.
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.