PipeWire: Implementation API

PipeWire 0.3.67

Loading...
Searching...
No Matches
Modules | Files
Implementation API

PipeWire Object Implementation API. More...

## Modules
| Client Impl
| PipeWire client object class.
| Core Impl
| PipeWire core interface.
| Device Impl
| The device is an object that manages nodes.
| Factory Impl
| The factory is used to make objects on demand.
| Link Impl
| PipeWire link object.
| Metadata Impl
| The metadata is used to store key/type/value pairs per object id.
| Module Impl
| A dynamically loadable module.
| Node Impl
| The node object processes data.
| Port Impl
| A port can be used to link two nodes.
| Buffers
| Buffer handling.
| Control
| A control can be used to control a port property.
| Data Loop
| PipeWire rt-loop object.
| Global
| A global object visible to remote clients.
| Protocol
| Manages protocols and their implementation.
| Resource
| Client owned objects.
| Thread Loop
| The threaded loop object runs a Loop in a separate thread and ensures proper locking is done.
| Work Queue
| Queued processing of work items.

## Files
file | impl.h
| `pipewire/impl.h`

## Detailed Description

PipeWire Object Implementation API.

The implementation API provides the tools to build new objects and modules.

If you are familiar with Wayland implementation, the Implementation API is roughly equivalent to libwayland-server.

See: PipeWire API