Packages / Debian 13 (Trixie) / libs / pipewire-system-services
Package: pipewire-system-services
Maintainers:
External Resources:
Homepage: [pipewire.org]
Similar packages:
- [gstreamer1.0-pipewire]
GStreamer 1.0 plugin for the PipeWire multimedia server
- [libpipewire-0.3-0t64]
libraries for the PipeWire multimedia server
- [libpipewire-0.3-common]
libraries for the PipeWire multimedia server - common files
- [libpipewire-0.3-dev]
libraries for the PipeWire multimedia server - development
- [libpipewire-0.3-modules]
libraries for the PipeWire multimedia server - modules
- [libpipewire-0.3-modules-x11]
libraries for the PipeWire multimedia server - X11 modules
- [libspa-0.2-bluetooth]
libraries for the PipeWire multimedia server - bluetooth plugins
- [libspa-0.2-dev]
libraries for the PipeWire multimedia server Simple Plugin API - development
- [libspa-0.2-jack]
libraries for the PipeWire multimedia server - JACK client
- [libspa-0.2-libcamera]
libraries for the PipeWire multimedia server - libcamera plugin
- [libspa-0.2-modules]
libraries for the PipeWire multimedia server Simple Plugin API - modules
- [pipewire-alsa]
PipeWire ALSA plugin, for ALSA applications to output via PipeWire
- [pipewire-audio]
recommended set of PipeWire packages for a standard audio desktop use
- [pipewire-audio-client-libraries]
transitional package for pipewire-alsa and pipewire-jack
- [pipewire-bin]
PipeWire multimedia server - programs
- [pipewire-doc]
libraries for the PipeWire multimedia server - documentation
- [pipewire-jack]
PipeWire JACK plugin, for JACK applications to output via PipeWire
- [pipewire-libcamera]
transitional package for libspa-0.2-libcamera
- [pipewire-pulse]
PipeWire PulseAudio daemon
- [pipewire-tests]
PipeWire multimedia server - tests and examples
- [pipewire-v4l2]
PipeWire V4L2 plugin
audio and video processing engine multimedia server (system services)
Жоден опублікований запис не відповідає цьому фільтру набору та архітектури.
Шляхи файлів пакета (0)
Paths come from the repository package-file index for the observed builds. They describe archive/package associations, not every file that will exist on a running system after maintainer scripts, alternatives, generated state, diversions, or installation choices.
No package-associated file paths were observed for the displayed build metadata.
