68916e062b
When node.async is set, make the node async. Advertize SPA_IO_AsyncBuffers on mixer ports when supported. Set a new port flag when AsyncBuffer is supported on the port. When making a link and if one of the nodes is async and the linked ports support AsyncBuffer, make the link async and set this as a property on the link. For async nodes we will use SPA_IO_AsyncBuffers on the mixer ports. Nodes that are async will not increment the peer required counters. This ensures that the peer can start immediately before the async node is ready. On an async link, writers will write to the (cycle+1 & 1) async buffers entry and readers will read from (cycle & 1). This makes the readers read from the previously filled area. We need to have two very controlled areas with specific rules for who reads and who writes where because the two nodes will run concurrently and no special synchronization is possible otherwise. These async nodes can be paused and blocked without blocking or xrunning the rest of graph. If the node didn't produce anything when the next cycle starts, the graph will run with silence. See #3509 |
||
|---|---|---|
| .. | ||
| examples | ||
| jack | ||
| src | ||
| meson.build | ||