I’ve done a few random tests of UHD movies on a Gen1 and Gen3 ATV4k here, and the most recent testflight crashes back to the home menu after a few minutes. Anyone else?
Ok, at present I can not reproduce this issue. Can you post your Logs immediately after the crash.
Have Verbose logging enabled, then after the crash enable Log Download. Then following these instructions.
https://support.plex.tv/articles/212639598-apple-tv-logs/
This crash was happening before the last update, what does seem to be consistent for my setup is a ATV power cycle. Meaning I have had electricity outages recently which would have cleared the ATV cache. So previous thought of a memory leak seems plausible. So anyone that would like to manually power cycle to see if this extends crash periods would be a way forward for now.
Yes few others and myself are experiencing the random crashes back to the Home Screen.
When we post logs, does anyone actually look at them?
Had to downgrade back to the TestFlight build without the experimental player. Subtitles aren’t showing up properly (shifted to one side, online outlined, no fill colour). Downgrading fixed it.
I hope we see Plex put more resources behind fixing these issues than just Craig. Users are getting frustrated and he’s left bearing the brunt of it because he’s seemingly all alone in here. Sorry for my frustration, Craig.
1 Like
Hello everyone, I’ve noticed over the past few days that Plex ATV abruptly crashes while watching a movie. I suspect that the Apple TV screensaver might be causing this. The app crashes, remains open in the background, and the screensaver starts immediately. Can anyone confirm this?
cheers Vati
Here’s my app and PMS logs from a crash playing a UHD movie for a minute or so. Hope this helps.
Plex Media Server Logs_2025-01-26_16-07-02.zip (3.9 MB)
logging.zip (501.4 KB)
-Alan
1 Like
Yes there is generally a negotiation and then a number of things can happen. Anything from the server setting up for transcoding, doing the actual transcoding, or the player taking time to decode the transcoded media which can take longer depending on how the stream is delivered.
Sometimes we can see from the logs if there is something that is consistently failing and retrying. If it is taking a very long time I would assume that multiple things are being tried on the server before it can actually produce a viable stream.
It uses the new experimental player and will continue to receive updates from the feedback in this thread. 
If you can send me logs with Verbose Logging on that would be helpful.
Also I’m going to push another build that disables the new audio engine and a few other fixes.
So if you can give it shot once that is pushed early this week.
I am working on the issue with HomePods, other AirPlay devices, and receivers.
The logs have helped so I appreciate it.
I can’t remember if you’re in the beta but yes the betas are still going out and don’t include the experimental player.
We did recently do the HEVC transcoding PMS update so that may be an issue? If you could provide some of the logs in a DM or in another thread we can get that to the right team.
Which subtitle types?
I’m fixing a similar issue where if some system settings for subtitles are set it will break some subtitle types so I want to confirm.
Yes it was reported but thank you for following up.
I do have a fix for this coming in the next build
1 Like
Here is a small update to start the week:
Sorry for the delay, we’ve had the new preview released, and I was also traveling.
I do have a new build that has various fixes and improvements.
It also includes a possible fix for the crashes that have been popping up.
I will still dig deeper into the crashes, though.
I am continuing to look at the larger audio sync issues, especially concerning external audio devices. (On top of the various smaller bugs)
Other than that, I’m refining my process for tracking bugs and making some bigger improvements to performance.
10 Likes
I must say that so far the video playback is excellent in the Preview. I tested this on an IPad Pro 2nd Gen and is on par with Infuse. Audio Playback is also on par so far … although I have only tested H.264 and H.265 files with AAC or EAC-3 sound tracks. Subtitles work with some minor glitches, like wrong font size etc.
1 Like
My problem with the “Plex Experience Preview” is that it’s a step backward on many basic items. While I understand this is a “preview” scrolling is very laggy even on a 16 Pro, there seems to be no sign of media info (is it 4k hdr, sd, ?), the player is only full screen (overlaying notch) with no option to toggle, etc. So I’m very cautiously optimistic at this point.
Thanks Craig! Much appreciated and keep up the great work.
1 Like
We’re constantly working on performance improvements for sure.
The media info is coming, some team members asked for the status on that just today.
We also talked about the full screen issue as well and have it down to be implemented
My next son shall be named Craig. 
I took a quick look here and it seems the bulk of what I’m curious about is a ~10 second period before transcoding starts where there are many entries for:
Codecs: hardware transcoding: testing API nvenc for device 'pci:0000:81:00.0' (NVIDIA TU104GL [Quadro RTX 5000])
Where it seems to be repeatedly testing the GPU for different capabilities(?) like (filtered log):
Jan 27, 2025 13:21:44.248 [139716088163128] Debug — [Req#6b5d0b/Transcode] Codecs: testing h264_nvenc (encoder)
Jan 27, 2025 13:21:44.765 [139716088163128] Debug — [Req#6b5d0b/Transcode] Codecs: testing hevc_nvenc (encoder)
Jan 27, 2025 13:21:45.217 [139716088163128] Debug — [Req#6b5d0b/Transcode] Codecs: testing hevc (decoder) with hwdevice nvdec
Jan 27, 2025 13:21:45.409 [139716088163128] Debug — [Req#6b5d0b/Transcode] Codecs: testing h264_nvenc (encoder)
Jan 27, 2025 13:21:45.864 [139716088163128] Debug — [Req#6b5d0b/Transcode] Codecs: testing hevc_nvenc (encoder)
Jan 27, 2025 13:21:46.313 [139716088163128] Debug — [Req#6b5d0b/Transcode] Codecs: testing hevc (decoder) with hwdevice nvdec
Jan 27, 2025 13:21:46.506 [139716088163128] Debug — [Req#6b5d0b/Transcode] Codecs: testing h264_nvenc (encoder)
Jan 27, 2025 13:21:46.983 [139716088163128] Debug — [Req#6b5d0b/Transcode] Codecs: testing hevc_nvenc (encoder)
Jan 27, 2025 13:21:47.453 [139716088163128] Debug — [Req#6b5d0b/Transcode] Codecs: testing hevc (decoder) with hwdevice nvdec
Jan 27, 2025 13:21:47.653 [139716088163128] Debug — [Req#6b5d0b/Transcode] Codecs: testing h264_nvenc (encoder)
Jan 27, 2025 13:21:48.105 [139716088163128] Debug — [Req#6b5d0b/Transcode] Codecs: testing hevc_nvenc (encoder)
Jan 27, 2025 13:21:48.571 [139716088163128] Debug — [Req#6b5d0b/Transcode] Codecs: testing hevc (decoder) with hwdevice nvdec
Jan 27, 2025 13:21:49.035 [139716092930872] Debug — [Req#6b5de4/Transcode] Codecs: testing h264_nvenc (encoder)
Jan 27, 2025 13:21:49.550 [139716092930872] Debug — [Req#6b5de4/Transcode] Codecs: testing hevc_nvenc (encoder)
Jan 27, 2025 13:21:50.027 [139716092930872] Debug — [Req#6b5de4/Transcode] Codecs: testing hevc (decoder) with hwdevice nvdec
Jan 27, 2025 13:21:50.217 [139716092930872] Debug — [Req#6b5de4/Transcode] Codecs: testing h264_nvenc (encoder)
Jan 27, 2025 13:21:50.669 [139716092930872] Debug — [Req#6b5de4/Transcode] Codecs: testing hevc_nvenc (encoder)
Jan 27, 2025 13:21:51.121 [139716092930872] Debug — [Req#6b5de4/Transcode] Codecs: testing hevc (decoder) with hwdevice nvdec
Jan 27, 2025 13:21:51.324 [139716092930872] Debug — [Req#6b5de4/Transcode] Codecs: testing h264_nvenc (encoder)
Jan 27, 2025 13:21:51.786 [139716092930872] Debug — [Req#6b5de4/Transcode] Codecs: testing hevc_nvenc (encoder)
Jan 27, 2025 13:21:52.245 [139716092930872] Debug — [Req#6b5de4/Transcode] Codecs: testing hevc (decoder) with hwdevice nvdec
Jan 27, 2025 13:21:52.436 [139716092930872] Debug — [Req#6b5de4/Transcode] Codecs: testing h264_nvenc (encoder)
Jan 27, 2025 13:21:52.884 [139716092930872] Debug — [Req#6b5de4/Transcode] Codecs: testing hevc_nvenc (encoder)
Jan 27, 2025 13:21:53.346 [139716092930872] Debug — [Req#6b5de4/Transcode] Codecs: testing hevc (decoder) with hwdevice nvdec
(full log here if you care 
) That feels like a lot of time/probes (especially without any UI progress indicator). So I’m curious. I assume those aren’t general capabilities being probed which could be cached for a given card – especially given they seem to repeat. But is this a sign of potential misconfiguration on my end or just “how it must be”.
Thanks again. After a long time with little movement player-wise, I’m really glad you’re on board.
1 Like
