Can’t be certain on what the issue is without a sample that has the problem, I’m trying various files here and they all playback successfully.
I’ve made some tweaks that might solve the problem in the build below, if anyone is able to try it and see if the issue is fixed or not that would be helpful.
I can concur that whatever you changed, worked! All three movies I tested above, I tried again and they all played the clips I ran just fine. This is on my Shield 2017 Pro running the latest software from Nvidia, including the three Hotfixes.
I was going to try and post a video clip of what I was experiencing but it really was just as simple as seeing me try to start a movie with the TrueHD audio on, and seeing the loading wheel sit and spin and spin. Then if I switched to the 5.1 track it would start right up. I did capture that on a short video if it’s helpful.
But again, the version you just posted works great as far as I can tell. I appreciate you working on this for us as Plex customers!!!
MUCH better! I just installed the ARM64 version and can confirm that the endless spinner/failure to play issue hasn’t cropped up for me. Also, the audio dropout/freeze issue on TrueHD files seems to have been addressed.
The only lingering quirk that I’m seeing is that if I try to make large (anything more than ~30 second) jumps forward/backward it struggles to resume the clip. Specifically, the video freezes and doesn’t start back up no matter how long I wait. However, if I back out of the movie and then hit Resume from the main menu everything starts back up just fine.
The only lingering quirk that I’m seeing is that if I try to make large (anything more than ~30 second) jumps forward/backward it struggles to resume the clip. Specifically, the video freezes and doesn’t start back up no matter how long I wait. However, if I back out of the movie and then hit Resume from the main menu everything starts back up just fine.
Big thanks @Achilles. I side-loaded 8.30.2.xxxx yesterday snd was able to play Thor perfectly. Then went to CA The First Avenger (TrueHD audio) and played it all the way through without a hitch.
I used my Samsung S21 phone with the Easy Fire Tools app to side-load and it was an absolute breeze to do. So happy to be up and running again!
Just updated to 9.0.0.31675, and the problem persists. The same movies play (very few), and the same movies don’t play (most of them). If anyone has these, could you please give them a try:
Play fine:
Jungle Cruise UHD
American Underdog UHD
The Kingsman UHD
Don’t play at all:
Spider-man (2002) UHD
Spider-man - No Way Home UHD
The Hurt Locker UHD
Sing 2 UHD
Nightmare Alley UHD
Godfather trilogy UHD
House of Gucci UHD
Westside Story UHD
Those are just the ones I tried quickly. Like others have said already, the ones that don’t play when TrueHD/Atmos is selected will play if you select Dolby Digital before start.
EDIT: Nevermind, I just now realized that the beta that was pushed today is a lower version than the one @sixones posted earlier. That explains it
What do you mean by that exactly may I ask? I came off the beta’s and rolled back to the last working stable. However after @sixones post (and before I saw you findings) I fell for it again.
To be clear I’m now on 9.0.0.31675.
Spider-man (2002) UHD - Doesn’t play
Spider-man - No Way Home UHD - Spiining circle for around 90 seconds and then the picture kicks in at that 1 min 30 mark in the movie
Jungle Cruise - Plays fine (as you found)
I can add Ant-Man UHD Doesn’t play
Ant-man and the Wasp UHD plays fine.
Just home from a night shift… will try some others after some sleep.
I’m confused by this comment too. @sixones experimental build above is 31664. The public beta build is 31675 which would appear to be newer. Perhaps the change in 31664 did not make it into 31675?
it may not be as cut and dry though, as i’ve never had any issues playing Spider-man - No Way Home UHD even in the public releases (including the current public release).
I had no issues on the 8.3.0 public release with any movie.
I came off the beta once more and hopefully after some sleep the “latest” stable will be available and i will test again especially with Spiderman - No Way Home.
I get there was an experimental build (I was back on stable at the time) But the bottom line is the latest beta is newer and (also) offers potential fixes.
I may be dim but regardless of a build being labelled as beta or experimental I simply see it as the latest one available is the one I should be testing.
The TrueHD fix is contained within the latest beta release, if the latest beta does not work then the problem does not lie with the recent TrueHD changes and is something else.
The build I shared previously on this thread includes a new demuxer which will be released in v9.1. I’ve created a new build that uses the new demuxer, from the sounds of things this should solve the issue if your still having TrueHD files getting stuck loading.
