Are you using adjust-refresh and whitelisted modes to play media at native resolution/refresh or forcing everything to 60Hz? I'm not seeing any issues from a current TVH setup and my server is 6,000Km away down a WireGuard tunnel (this generally encourages any latent issues to show up).
wolfgang61 You have to compare debug logs to answer this. Logs name internal codecs.
Pi 5 goes to Yamaha RX-V685 goes to a 4K TV.
Replacing the cable from Pi 5 to the Yamaha fixed the problem. I have no idea if this cable is 2.0 or whatever, but it looks more expensive.
Could it be that the Pi 5 produces a higher HDMI data rate than the Pi 4? Why is that so with the same video material? DVB-S2, HD. If so, that might be worth mentioning in future upgrade instructions. Or reduce the HDMI data rate to what is really needed for the actual video.
Different HDMI output resolutions, frame rates and bit depths require different bandwidth HDMI cables. I think both the Pi 4B and Pi 5 can output the higher bandwidth 18Gbs modes in 2160p60 4:2:2 12-bit (there isn't a 4:2:2 10-bit option in HDMI 2.0). Someone please correct me if I'm wrong.
However it could be that your previous set-up with a Pi 4B didn't try to use 18Gbs modes and your Pi 5 set-up is?
