Forums
Linux NXT client and pipewire
Quick find code: 409-410-514-66216866
I've seen a single other bug report about it on Fedora 34 (Fwiw, one single bug report is concerning because the majority of people don't give feedback to begin with, so it doesn't take much to flag up patterns).
In theory, the AUR/deb version works best because it makes use of realtime audio threads. The Flatpak and Snap package can't do this. But the realtime threads were never the perfect fix from what I see anyway.
The other fix you'll see around is the PULSEAUDIO_LATENCY_MSEC variable, Pipewire/Pulse actually does still respect this variable, so it's unfortunate that it doesn't necessarily work in the same way. All the client packages set this value by default, but they all pick different values, and personally I don't see any trend that identifies what works best for who.
For curiosity sake, I'd personally appreciate if you could try out the Snap package, once it's installed, try running it with
Specifically, the old behaviour was that it'd usually fail to produce nice sound on the first boot, but EVERY (99.9%) boot afterwards on the same desktop session had perfect sound. I ended up having to revert it because of some complaints that might not exist now, so it'd be nice if you had any feedback on whether it helped for Arch/Pipe.
(And as a shortcut, you can mess with the Pulseaudio variable with
In theory, the AUR/deb version works best because it makes use of realtime audio threads. The Flatpak and Snap package can't do this. But the realtime threads were never the perfect fix from what I see anyway.
The other fix you'll see around is the PULSEAUDIO_LATENCY_MSEC variable, Pipewire/Pulse actually does still respect this variable, so it's unfortunate that it doesn't necessarily work in the same way. All the client packages set this value by default, but they all pick different values, and personally I don't see any trend that identifies what works best for who.
For curiosity sake, I'd personally appreciate if you could try out the Snap package, once it's installed, try running it with
runescape.rs3 -a
, which will make it use Pulse with the ALSA backend (and then pulse on your system would pass onto Pipewire). You'd think the indirection would be more problematic, but for Pulseaudio as the system server alone, this allegedly fixed a lot of the problems with audio for people. Maybe Pipewire has the same result.
Specifically, the old behaviour was that it'd usually fail to produce nice sound on the first boot, but EVERY (99.9%) boot afterwards on the same desktop session had perfect sound. I ended up having to revert it because of some complaints that might not exist now, so it'd be nice if you had any feedback on whether it helped for Arch/Pipe.
(And as a shortcut, you can mess with the Pulseaudio variable with
runescape.rs3 -p <int>
- just don't use -p and -a at the same time
26-May-2021 23:50:13 - Last edited on 27-May-2021 12:07:51 by Hmm
So I downloaded snap from the AUR and downloaded RS3 using the snap package.
So... apparently that works out of the box, didn't even need to do anything at all, just ran it and it works.
Of course I created a shortcut on my Desktop and ran it with gamemoderun
but looks like it fixed the sound problem and and also there is no other issue whatsoever. What is the difference between that and the flatpak? could it be that the latest development of the client was implemented in the snap and not in flatpak? (it would make sense).
Anyways I will update if there is anything else going on.
And one last thing, THANK YOU SUPER MUCH! Now I am able to use a workaround and stream desktop sound on Discord and other applications with pipewire and play RS3 without sound bugs, YAY!
So... apparently that works out of the box, didn't even need to do anything at all, just ran it and it works.
Of course I created a shortcut on my Desktop and ran it with gamemoderun
but looks like it fixed the sound problem and and also there is no other issue whatsoever. What is the difference between that and the flatpak? could it be that the latest development of the client was implemented in the snap and not in flatpak? (it would make sense).
Anyways I will update if there is anything else going on.
And one last thing, THANK YOU SUPER MUCH! Now I am able to use a workaround and stream desktop sound on Discord and other applications with pipewire and play RS3 without sound bugs, YAY!
27-May-2021 20:12:13
Quick find code: 409-410-514-66216866 Back to Top