Pipewire Input Latency / Updating Pipewire

Help
1

I have recently installed the latest version of NixOS, i now want to use Discord, but i experience ≈ 500ms delay on the input. Is would assume pipewire is responsible for this input lag. I found a thread claiming the issue where fixed in a patch > 1.3.27. I currently run:

$ pipewire --version
pipewire
Compiled with libpipewire 1.2.7
Linked with libpipewire 1.2.7

How would i update Pipewire in NixOS?

My config looks like this:

  # Enable sound with pipewire.
  hardware.pulseaudio.enable = false;
  security.rtkit.enable = true;
  services.pipewire = {
    enable = true;
    alsa.enable = true;
    alsa.support32Bit = true;
    pulse.enable = true;
    # If you want to use JACK applications, uncomment this
    jack.enable = true;

    # use the example session manager (no others are packaged yet so this is enabled by default,
    # no need to redefine it in your config for now)
    #media-session.enable = true;
    extraConfig.pipewire."92-low-latency" = {
	    "context.properties" = {
		    "default.clock.rate" = 48000;
		    "default.clock.quantum" = 32;
		    "default.clock.min-quantum" = 32;
		    "default.clock.max-quantum" = 32;
	    };
    };
  };

As you can see, i have tried both low-latency mode and i am unsure what Alsa and Jack are. The pulseaudio library is obsolete, no? Please give me some insights in how i could resolve my problem, or how i would update Pipewire to the latest 1.3.82 release.

1 Like
2

Is it possible that Discord is using pulse audio on the back end? Try adding the low-latency setup for that as well: PipeWire - NixOS Wiki

I’m running the same version of pipewire as you, and that pulse backend setup stuff helped with latency issues I was running into with the Carla VST Host using it to play music with a midi controller.

Also, I don’t know whether this is necessary, but I did a reboot after making my changes just to be safe. It’s worth a try. Good luck! These types of issues are really hard to debug.