I’ll post updates to our mailing list and to my twitter. These features are not scheduled to a specific release yet. Longer-term plans (after 0.3) include service discovery, adaptive streaming, multi-room, a relay tool, and an Android app.

These features are planned for 0.3 release. These protocols will open a way towards adding more audio encodings, including non-stereo channel sets, non-44100 sample rates, and Opus support. Now we will focus on 0.2, which will add RTCP and RTSP support and the Control API. Thanks to everyone who have reported bugs and contributed patches! Special thanks to S-trace who has helped a lot with the porting to Android. They fix numerous build issues reported by users, fix OpenFEC crashes and bugs in networking code, and add initial Android support. Since the last publication, I and Dmitriy have prepared two minor bugfix releases: 0.1.1 and 0.1.2.

This tutorial describes how to use Roc to connect audio apps and devices running on Ubuntu or macOS desktop, Raspberry Pi board, or an Android phone. You can set up several devices and switch between them on the fly via standard PulseAudio GUI or CLI you can also route different apps to different devices Īll of these can work over Wi-Fi with acceptable service quality. You can set up some music server with remote control (like MPD) and then stream sound from it to other devices You can also stream sound to your Android phone You can connect speakers to a Raspberry Pi box and stream sound from your other devices to it What can you do with this? Some examples: My earlier article describes how does Roc achieve this and provides some comparison with other software including built-in PulseAudio transports. Roc transparently integrates into the PulseAudio workflow and can be controlled via the usual PulseAudio GUIs, just like the built-in PulseAudio transports, but provides a better service quality on Wi-Fi. Roc can interconnect audio apps and devices across different platforms and audio systems Roc has the following benefits in this case:Ĭompared to built-in PulseAudio transports and other software that uses TCP or bare RTP, Roc can provide quite low latency and good service quality over Wi-Fi at the same time Ĭompared to Opus-based transports, Roc can stream high-quality lossless audio and still provide loss recovery though, Opus support is also planned and is on the way You can learn about the project here: overview, features, usage.Īmong other things, Roc can be used as a network transport for PulseAudio, ALSA, or macOS CoreAudio, and connect audio applications and devices across the network. Roc is an open-source toolkit for real-time audio streaming over the network.

Pulseaudio raspberry pi