5 commits

Author	SHA1	Message	Date
Wim Taymans	d89df144f0	jack-tunnel: run graph from JACK thread ... Stop our own data-loop and enter/iterate/leave it from the jack thread. This runs all our nodes in the JACK thread and removes 2 context switches (jack to and from pw thread). We can possibly do this nicer by only pushing our own streams onto a new custom data-loop but that's for later.	2023-04-28 17:06:29 +02:00
Wim Taymans	9e7921b37d	module-jack: improve xrun reporting	2023-04-27 18:10:41 +02:00
Wim Taymans	381aa90b54	module-jack-tunnel: improve some docs	2023-04-27 17:22:05 +02:00
Wim Taymans	ab0cee29dd	doc: add jack-tunnel to docs	2023-04-27 17:03:10 +02:00
Wim Taymans	73f5f7ae65	jack-tunnel: add a new 0-latency JACK sink/source module ... Add a new JACK sink/source pair that translates to a single JACK client. The JACK playback port appears as PipeWire source and is processed directly, synchronously, through the complete pipewire graph into the PipeWire sink that is then made available on the JACK capture ports. Because all this happens in the same JACK cycle with no delay, the latency is 0. A jack_iodelay on the JACK server has exactly the same latency as the jack_iodelay on the PipeWire side. The PipeWire sink and source are forced into the same rate and buffer_size as the JACK server and can't dynamically change. This only supports Audio for now.	2023-04-27 16:27:54 +02:00