We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello! Firstly, I really impressed your project and thank you :) So I want to use it for mirroring some device concurrently.
I tried as below for starting multiple airplay server. (I use kotlin)
AirplayServer("servername", 5003, 5004, MirrorDataConsummerImplement).start() AirplayServer("servername2", 5103, 5104, MirrorDataConsummerImplement).start() AirplayServer("servername3", 5203, 5204, MirrorDataConsummerImplement).start()
But I can see only one server among them on my iPhone or iPad.
Is it related with value of airPlayMDNSProps in AirPlayBonjour.java like deviceid, pk, pi? How can I start multiple airplay server?
The text was updated successfully, but these errors were encountered:
You need to change the mac address in the function airPlayMDNSProps() and airTunesServerName for each different AirplayServer.
Sorry, something went wrong.
@TrungTVT Thank you for your reply! I can see multiple airplay server now. Thank you again :)
No branches or pull requests
Hello!
Firstly, I really impressed your project and thank you :)
So I want to use it for mirroring some device concurrently.
I tried as below for starting multiple airplay server.
(I use kotlin)
AirplayServer("servername", 5003, 5004, MirrorDataConsummerImplement).start()
AirplayServer("servername2", 5103, 5104, MirrorDataConsummerImplement).start()
AirplayServer("servername3", 5203, 5204, MirrorDataConsummerImplement).start()
But I can see only one server among them on my iPhone or iPad.
Is it related with value of airPlayMDNSProps in AirPlayBonjour.java like deviceid, pk, pi?
How can I start multiple airplay server?
The text was updated successfully, but these errors were encountered: