Multimedia processing graphs
Find a file
Wim Taymans 0af87d2685 client-node: keep port buffers in special location
Keep the output port buffers in a special mix info. They should
stay there even when the mix is removed and should only be cleared
explicitly with a NULL Format or 0 use_buffers.
2019-08-15 11:49:32 +02:00
doc
man Relicense as MIT/X11 2018-11-05 17:48:52 +01:00
pipewire-alsa@dddaaf4db4 channelmix: implement per channel volume 2019-08-12 15:14:39 +02:00
pipewire-jack@2d6f9950a5 channelmix: implement per channel volume 2019-08-12 15:14:39 +02:00
pipewire-pulseaudio@e4a6782c48 pulse: update module 2019-08-13 18:48:05 +02:00
po
spa client-node: keep port buffers in special location 2019-08-15 11:49:32 +02:00
src client-node: keep port buffers in special location 2019-08-15 11:49:32 +02:00
.editorconfig add .editorconfig files 2019-02-13 11:19:21 +01:00
.gitignore
.gitmodules
.travis.yml travis: fix the build script 2019-08-01 15:18:38 +02:00
_config.yml
autogen.sh autogen.sh: Immediately fail on command errors 2019-05-23 10:15:14 +02:00
check_missing_headers.sh travis: run make install and check for headers that have not been installed 2019-05-31 09:51:30 +02:00
config.h.meson
COPYING Relicense as MIT/X11 2018-11-05 17:48:52 +01:00
LICENSE Relicense as MIT/X11 2018-11-05 17:48:52 +01:00
Makefile.in Add PortConfig parameter 2019-08-06 12:45:20 +02:00
meson.build meson.build: fix meson version warning 2019-08-09 23:20:55 +02:00
meson_options.txt videoconvert: beginnings of video converter 2019-07-25 12:19:41 +02:00
NEWS
PROTOCOL
pw-uninstalled.sh
README Relicense as MIT/X11 2018-11-05 17:48:52 +01:00

PipeWire
--------

PipeWire is a server and user space API to deal with multimedia
pipelines. This includes:

  - Making available sources of video (such as from a capture devices or
       application provided streams) and multiplexing this with
       clients.
  - Accessing sources of video for consumption.
  - Generating graphs for audio and video processing.

Nodes in the graph can be implemented as separate processes,
communicating with sockets and exchanging multimedia content using fd
passing.

Building
--------

Pipewire uses the Meson and Ninja build system to compile. If you're not
familiar with these tools, the included "autogen.sh" script will
automatically run the correct meson/ninja commands, and output a Makefile.
It follows that there are two methods to build Pipewire, however both rely
on Meson and Ninja to actually perform the compilation:

$ ./autogen.sh
$ make

or the Meson/Ninja native method:

$ meson build
$ cd build
$ ninja

You can see the available meson options in meson_options.txt file.