Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for multiple devices in an airplayv2 road audio playing session #2591

Open
JensTimmerman opened this issue Dec 19, 2024 · 4 comments
Labels

Comments

@JensTimmerman
Copy link

What feature would you like?

I would like to be able to do multiroom audio.

The use case is where someone has multiple airplayv2 capable devices in their network, being able to stream to multiple at the same time, as one would do on e.g. an iPhone, selecting 2 speakers in the airplay menu.

Describe the solution you'd like

implement a method to have an airplayv2 capable device that's not playing anything join another airplayv2 capable device and play the same audio, in sync.

Any other information to share?

This issue is created to follow up the information I got in #1059

also, when trying to read the faq that's linked in the CONTRIBTING.MD I got a 404 page: https://pyatv.readthedocs.io/en/master/faq.html

@JensTimmerman
Copy link
Author

according to https://github.com/philippe44/libraop

It's possible to send synchronous audio to multiple players by using the NTP options (optionally combined with the wait option). Either get the NTP of the master machine from any application and then fork multiple instances of raop_play with that NTP and the same audio file, or use the -ntp option to get NTP to be written to a file and re-use that file when calling the instances of raop_play

@JensTimmerman
Copy link
Author

according to mikebrady/shairport-sync#1407 ptp is preferred

@JensTimmerman
Copy link
Author

https://github.com/hfujita/pulseaudio-raop2 is an implementation of this feature for PulseAudio

@JensTimmerman
Copy link
Author

I'm interested in giving this a go, it seems like most timing and rtsp support is already in place, I noticed a lack of setpeers command, but that might even be optional? https://emanuelecozzi.net/docs/airplay2/rtsp/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant