mirror of
https://gitlab.freedesktop.org/pipewire/pipewire.git
synced 2025-12-15 08:56:38 -05:00
Multimedia processing graphs
We can't allocate the shared meta in shared mem because then clients can damage it for other clients. Place it instead right after the buffer metadata array. Filter out the shared metadata for a client, we send it as part of the client_buffer structure. Remove pointer metadata, it's not so useful. Document the layout of the allocated buffers and the shared memory. Work on metadata to define control parameters |
||
|---|---|---|
| doc | ||
| man | ||
| pkgconfig | ||
| po | ||
| spa | ||
| src | ||
| .gitignore | ||
| _config.yml | ||
| autogen.sh | ||
| config.h.meson | ||
| git-version-gen | ||
| GPL | ||
| LGPL | ||
| LICENSE | ||
| Makefile.in | ||
| meson.build | ||
| meson_options.txt | ||
| NEWS | ||
| PROTOCOL | ||
| README | ||
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