roc-toolkit

* How does this compare to Roc, if you've looked at it? https://github.com/roc-streaming/roc-toolkit * Would it be possible to have pulse/pipewire sink/source examples to quickly get started on desktop?

Roc VAD[1] implements a virtual audio device for macOS that acts as network sender on receiver. It works on top of Roc Toolkit[2] and can be used with any compatible senders and receivers, including PipeWire and PulseAudio modules on Linux, Roc Droid app on Android, and CLI tools (which also support bare ALSA). Roc Toolkit itself is a library for (soft) realtime streaming with fixed latency and loss recovery (using FEC codes), designed to work well over unreliable networks like WiFi. Roc VAD also provides gRPC interface with full control of the driver, so that you can use it in your own projects. [1] https://github.com/roc-streaming/roc-vad [2] https://github.com/roc-streaming/roc-toolkit

I've used JamKazam (https://www.jamkazam.com) a few times recently to play folk music with some friends. The sort of music we play relies very heavily on listening to each other and improvising, and surprisingly it _just about_ works on JamKazam. It's certainly not perfect, but we're not going to be hanging out in pubs together any time soon. The important number is round-trip latency, and we found that around 25ms is good enough (we're all quite used to playing with people of varying time-keeping ability anyway). I think there's scope to improve on that using a library like Roc (https://github.com/roc-project/roc) where you can target a specific latency. I've been meaning to play around with it, but to be honest I'd rather be playing music :)

> 300ms is still noticably laggy when the audio is part of a video. Agree. > Some media players can delay their audio to account for playback delay in the audio device, if the audio stack supports that. Does Roc support that, or if not, is it on your roadmap? We have an open issue for implementing correct latency reports in PA modules. When we'll fix it, players that support that feature should automatically start taking the latency into account. Thanks for reminding me, I'll test this feature specifically. https://github.com/roc-project/roc/issues/171