Ok, it was a bit odd. When previously mentioning Content Matching I indeed had it enabled, when i disabled CM the Screen saver would randomly activate which it never did prior that I recall. Then again I have a limited 4K Library with mkv container.
I have disabled screen saver now to NEVER, issue has disappeared obviously.
Do you mean the original stuttering issue, or the one reported in the recent beta build (that seems to be more related to frame rate matching than performance)?
The former seems to be mostly resolved in the beta builds, but we’re investigating the other issues that have been reported here. As such, we don’t have an ETA on when that work will go into the main builds.
Just filled out the form in hope that the beta will address the issues with Dolby TrueHD direct play on Apple TV 4K (3rd gen) : I just bought one and realized I can’t get a Dolby TrueHD track to play without getting transcoded to FLAC, introducing a high delay between audio and video in the process, making the Plex app unusable for me in most cases as I have a lot of this type of content in my library. Infuse works fine though but I’d prefer not having to pay this much money in addition to my Plex Pass, just to be able to stream my content.
Do you know how long it takes to get added to the program ?
This won’t be fixed (not really a bug) Apple TV does not support TrueHD, infuse pays for a Dolby License to decode TrueHD and send out LPCM… yes plex could do this but that’s not there thing… they support what the device supports. - also its not really the point of this beta… which is to fix the stuttering, anything else will come after that is sorted.
Plex covers many codecs, they have done DTS and as such, decodes DTSHDMA to LPCM for us. It is in their wheelhouse.
Whether the reason is cost or technical, Dolby is especially difficult, just look at the plethora of DV profiles. People will learn when they shun and avoid or convert off of the dolby bandwagon, their tech life gets a LOT easier.
Plex will direct play TrueHD in beta 8.38 (8676) with the new experimental player, but the Apple TV converts it to LPCM. Keep in mind this does mean that Atmos height elements are stripped away.
Thank you all for the explanations. I’m not sure I got it all though. In short, I think the main takeway is that the Apple TV is not (and probably never will be ?) a suitable contender for playing Dolby TrueHD, unlike the Nvidia Shield ? Basically, even using Infuse or Plex’s new experimental player, there will always be some scenario where something gets lost or degraded (because of LPCM ?) ?
Sorry if I went a bit off topic. I’m just trying to make sense of all this and I realize that it is much more complex than I thought. For example, I’ve always been sure that “Direct Play” meant just that : no conversion, nothing lost.
With the LCPM output from the AppleTV, the only thing lost is Atmos metadata. If you do not have an Atmos setup at home, there is no quality loss from a TrueHD to LCPM output.
If you do have an Atmos system at home, Infuse can do EAC3 (Dolby Digital) Atmos like that found in streaming services.
If the issue you had reported isn’t covered in this list, rest assured it wasn’t forgotten. But we wanted to provide an updated build covering a few fixes to improve QOL and gather further feedback as we continue our work.
PS: I will try to go over the form and add new folks this week. No promises on how many get added, as we already have a few hundred testers just for this and available slots are very limited (they’re shared with the overall limit that’s used for public beta testing).
