PipeWire
0.3.33
|
Array Objects | An array object |
PipeWire Core Interface | PipeWire core interface |
Client Object | PipeWire client object class |
PipeWire Client | |
PipeWire Context | The PipeWire context object manages all locally available resources. It is used by both clients and servers |
Control | A control can be used to control a port property |
The PipeWire Core Global Object | The core global object |
Registry | The registry object is a singleton object that keeps track of global objects on the PipeWire instance. See also PipeWire Global Object |
PipeWire Device Interface | The device is an object that manages nodes. It typically corresponds to a physical hardware device but it does not have to be |
PipeWire rt-loop object | This loop starts a new real-time thread that is designed to run the processing graph |
PipeWire Factory Interface | The factory is used to make objects on demand |
PipeWire Filter | PipeWire filter object class |
PipeWire Global Object | A global object visible to remote clients |
Link Objects | PipeWire link object |
PipeWire Link | A link is the connection between 2 nodes (PipeWire Node). Nodes are linked together on ports |
Logging | Logging functions of PipeWire |
PipeWire Loop | PipeWire loop object provides an implementation of the spa loop interfaces. It can be used to implement various event loops |
PipeWire Main-Loop Interface | A main loop object |
Map Objects | A map that holds objects indexed by id |
Memory Blocks | |
PipeWire Metadata Interface | The metadata is used to store key/type/value pairs per object id |
Dynamically loadable Module | A dynamically loadable module |
Node | The node object processes data. The node has a list of input and output ports (Port Object) on which it will receive and send out buffers respectively |
PipeWire Node | |
PipeWire Permission | Permissions are kept for a client and describe what the client is allowed to do with an object |
PipeWire initialization and infrastructure functions | |
Port Object | A port can be used to link two nodes |
PipeWire Port | |
Key-Value pairs | Properties are used to pass around arbitrary key/value pairs. Both keys and values are strings which keeps things simple. Encoding of arbitrary values should be done by using a string serialization such as base64 for binary blobs |
PipeWire Protocol | Manages protocols and their implementation |
Proxy Object | Represents an object on the client side |
PipeWire Resources | Client owned objects |
Stream Object | PipeWire stream objects |
Thread related functions | Functions to manipulate threads |
PipeWire Threaded Loop Object | The threaded loop object runs a PipeWire Loop in a separate thread and ensures proper locking is done |
PipeWire Types | |
PipeWire Utility Functions | Various utility functions |
PipeWire Work Queue Object | |
The pwtest PipeWire Test Suite | pwtest is a test runner framework for PipeWire |
SPA Buffers | Buffers describe the data and metadata that is exchanged between ports of a node |
SPA Controls | |
SPA Debug | |
SPA Graph | |
SPA Device | The device interface can be used to monitor all kinds of devices and create objects as a result. Objects a typically other Devices or Nodes |
SPA Nodes | A spa_node is a component that can consume and produce buffers |
SPA Parameters | |
SPA POD | |
SPA Support Features | |
SPA Logging | |
SPA Plugin Handles | |
SPA Utils | |
SPA Interfaces | Generic implementation of implementation-independent interfaces |
SPA Hooks | A SPA Hook is a data structure to keep track of callbacks. It is similar to the SPA Interfaces and typically used where an implementation allows for multiple external callback functions. For example, an implementation may use a hook list to implement signals with each caller using a hook to register callbacks to be invoked on those signals |
SPA JSON Parser | |
SPA Key Names | |
SPA Factory Names | |
SPA Types | |
PipeWire Keys | A collection of keys that are used to add extra information on objects |