|
PipeWire 0.3.38
|
| 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 |
| 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 |
| SPA JSON Parser | |
| SPA Key Names | |
| SPA Factory Names | |
| SPA Types | |
| Array Objects | An array object |
| PipeWire Client | |
| PipeWire Context | The PipeWire context object manages all locally available resources |
| 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 |
| PipeWire rt-loop object | This loop starts a new real-time thread that is designed to run the processing graph |
| PipeWire Filter | PipeWire filter object class |
| PipeWire Global Object | A global object visible to remote clients |
| Client Object | PipeWire client object class |
| PipeWire Core Interface | PipeWire core interface |
| PipeWire Device Interface | The device is an object that manages nodes |
| PipeWire Factory Interface | The factory is used to make objects on demand |
| Link Objects | PipeWire link object |
| 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 |
| Port Object | A port can be used to link two nodes |
| PipeWire Link | A link is the connection between 2 nodes (PipeWire Node) |
| Logging | Logging functions of PipeWire |
| PipeWire Loop | PipeWire loop object provides an implementation of the spa loop interfaces |
| PipeWire Main-Loop Interface | A main loop object |
| Map Objects | A map that holds objects indexed by id |
| Memory Blocks | |
| 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 | |
| PipeWire Port | |
| Key-Value pairs | Properties are used to pass around arbitrary key/value pairs |
| 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 |
| PipeWire Threaded Loop Object | The threaded loop object runs a PipeWire Loop in a separate thread and ensures proper locking is done |
| Thread related functions | Functions to manipulate threads |
| 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 |
| PipeWire Keys | A collection of keys that are used to add extra information on objects |