mirror of
https://gitlab.freedesktop.org/pipewire/pipewire.git
synced 2025-10-29 05:40:27 -04:00
reintroduce channels
Bring back the channel object. Making a node and port on the client side was rather awkward because of the async nature of many methods. It feels better to have a specific communication channel object to interface with a server side port. Use port activate/deactivate to start/stop streams Remove links from the ports. We let other objects install a callback on the port to receive and route buffers.
This commit is contained in:
parent
eefe6aacb9
commit
e167d30296
26 changed files with 2840 additions and 675 deletions
|
|
@ -35,6 +35,8 @@ Node1: a processing node, this can be a source, sink or transform
|
|||
/org/pinos/node*
|
||||
Port1: a port on a Node1, ports can be input or output ports
|
||||
/org/pinos/node*/port*
|
||||
Channel1: a communication channel between a client and port
|
||||
/org/pinos/client/channel*
|
||||
Link1: a link between 2 ports
|
||||
/org/pinos/link*
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue