This determines the ordering of items in Doxygen sidebar. More...
Topics | |
| Initialization | |
| Initializing PipeWire and loading SPA modules. | |
| Main Loop | |
| A main loop object. | |
| Context | |
| The PipeWire context object manages all locally available resources. | |
| Client | |
| Client interface. | |
| Core | |
| The core global object. | |
| Device | |
| Device interface. | |
| Factory | |
| Factory interface. | |
| Link | |
| A link is the connection between 2 nodes (Node). | |
| Loop | |
| PipeWire loop object provides an implementation of the spa loop interfaces. | |
| Module | |
| Module interface. | |
| Node | |
| Node interface. | |
| Permission | |
| Permissions are kept for a client and describe what the client is allowed to do with an object. | |
| Port | |
| Port interface. | |
| Proxy | |
| Represents an object on the client side. | |
| Registry | |
| The registry object is a singleton object that keeps track of global objects on the PipeWire instance. | |
| Type info | |
| Type information. | |
| Key Names | |
This determines the ordering of items in Doxygen sidebar.
PipeWire Core API
The Core API to access a PipeWire instance. This API is used by all clients to communicate with the PipeWire Daemon.
If you are familiar with Wayland implementation, the Core API is roughly equivalent to libwayland-client.
See: PipeWire API