3 ms·
Pipewire does not solve that unless your app uses their API. For 99% off apps (100% of VoIP?) you still get the same old latency until you go tuning configs. Pi
by NavinF 4y ago
Pipewire does not solve that unless your app uses their API. For 99% off apps (100% of VoIP?) you still get the same old latency until you go tuning configs. Pipewire is also not enabled on any LTS.
The rest of your replies reads as "La la la, I can't hear you!" which is pretty typical of the desktop Linux community. Deflect, deflect, and deflect :)
- xorcist 4y agoNot sure what "solving" means but it's not correct that Pipewire doesn't offer any benefits unless you use another API. Depending on what you compare it with, of course. If you use audio semi-professionally you might already use low latency software and not see better latency, but compared to Pulseaudio the difference should be noticeable. Of course, if the application is VoIP than Pulseaudio was already good enough, as network latency is an order of magnitude greater, but for realtime streaming applications the difference is there. Most end users won't care however. They switch when the distribution they use switches over.
- 29athrowaway 4y agoYou just listed a bunch of obscure issues that most people do not have and tried to portray that as being a blocker for a regular person adopting Linux.