Waester

Can confirm this happens in RPi3 as well, observing the top command I can see that it is python3.5 that draws most CPU resources (50%+) while the transcoding by ffmpeg...

Any chance the throttler fix make it to the 10.8.x branch?

@pallas I can confirm that by changing these lines to static ports works. https://github.com/FD-/RPiPlay/blob/e485668f752cedf9d1304ca08d5b2f2d03b67063/rpiplay.cpp#L384 **port** = 7000 ([source](https://openairplay.github.io/airplay-spec/service_discovery.html)) https://github.com/FD-/RPiPlay/blob/e485668f752cedf9d1304ca08d5b2f2d03b67063/lib/raop_ntp.c#L192 **tport** = 7011 ([source](https://openairplay.github.io/airplay-spec/screen_mirroring/time_synchronization.html)) https://github.com/FD-/RPiPlay/blob/e485668f752cedf9d1304ca08d5b2f2d03b67063/lib/raop_rtp.c#L231 **cport** = 6001 ([source](https://openairplay.github.io/airplay-spec/audio/rtsp_requests/setup.html) & [source](https://git.zx2c4.com/Airtunes2/about/#preferred-tcp-udp-ports))...

~~I can try changing it to 7100, but it might conflict with the HTTP port. It depends if rpiplay support multiplexing ports. If it works I will post a PR,...

@pallas ~~OK I verified that RPiPlay does not support port multiplexing, so using 7100 both as the HTTP port and mirror port did not work.~~ ~~We might have to pick...

Nevermind, my static HTTP port selection was wrong from the beginning, HTTP service should have been in port 7000 ([source](https://openairplay.github.io/airplay-spec/service_discovery.html)) and the HTTP **request** for mirroring happens in port 7100...

@SanderBorgmans @CO2020 I am no expert on the rpiplay application, but I know that when the initial connection is established and when the mirroring is shown on the laptop there...

Network wise it seems to be fine for both of you. Can you verify that all the dependacies is installed? If anything is missing you should install it and try...