PipeWire: Difference between revisions

Yajo (talk | contribs)
Lua is no longer used.
Frontear (talk | contribs)
m some small changes to formatting and grammar
Line 4: Line 4:
The daemon based on the framework can be configured to be both an audio server (with PulseAudio and JACK features) and a video capture server.
The daemon based on the framework can be configured to be both an audio server (with PulseAudio and JACK features) and a video capture server.


PipeWire also supports containers like Flatpak and does not rely on audio and video user groups but rather it uses a Polkit-like security model asking Flatpak or Wayland for permission to record screen or audio.  
PipeWire also supports containers like Flatpak and does not rely on <code>audio</code> and <code>video</code> user groups, but rather it uses a Polkit-like security model, asking Flatpak or Wayland for permission to record screen or audio.  


==Enabling PipeWire==
==Enabling PipeWire==
PipeWire can be enabled with the following configuration:
PipeWire can be enabled with the following configuration:


<syntaxHighlight lang=nix>
<syntaxhighlight lang="nix">
# Remove sound.enable or set it to false if you had it set previously, as sound.enable is only meant for ALSA-based configurations
# On NixOS 24.05 or older, this option must be set:
#sound.enable = false;


# rtkit is optional but recommended
# rtkit is optional but recommended
Line 22: Line 23:
   #jack.enable = true;
   #jack.enable = true;
};
};
</syntaxHighlight>
</syntaxhighlight>


It is possible to use the <code>services.pipewire.extraConfig</code> option hierarchy in NixOS (available from 24.05 onwards) to create drop-in configuration files, if needed.
It is possible to use the <code>services.pipewire.extraConfig</code> option hierarchy in NixOS (available from 24.05 onwards) to create drop-in configuration files, if needed.