watched Spiderman No Way Home (full remux including DV layer) last night using client version 8.31.1.31487 and had no issues with TrueHD audio.
1 Like
Yeah the reports on spider man donât make sense because it has no branching stuff.
They absolutely make sense, because the issue being discussed in this thread has nothing to do with seamless branching.
1 Like
Some titles have issues due to seamless branching and some titles have issues due to a regression with Plex app.
Agreed, but the issue raised here affects any and all TrueHD/Atmos titles. Itâs the regression thatâs being discussed here, which now seems to be fixed, while the seamless branch issue is very likely not fixed.
Personally, I havenât encountered the reported issues (in this thread) regarding Dolby TrueHD bitstreaming/passthrough. However, I am not disputing that this Plex app regression does exists with certain AV setups. Itâs been difficult for me to help anyone when I havenât been able to replicate it myself.
As I stated earlier, the resolution for this regression is a WIP with the developer. I have yet to update the public channel app v8.30.2.31202 on my production units. Google hasnât offered v8.31.1.31487 and I havenât bothered to side load it with adb.
1 Like
Makes sense that you havenât encountered it, because it was a regression in the 8.31.0.x builds.
Anyway, I just thought the thread was getting derailed by all the talk about seamless branching and MakeMKV.
Hopefully, the final 8.31.1.x will finally make its way to us today 
All I can say is, I have the alpha channel app installed in parallel with the public channel app on both of my 2019 Shield Pros I use as production. It is even more painful than the issues reported here for the beta channel app. The developer is working diligently to solve the issues I have reported.
2 Likes
Yeah, that might be my fault⊠Sorry yaâll 
1 Like
I only have so much time in my life to allocate for volunteer alpha and beta testing. Like you guys, I want a no-holds-barred experience with the Nvidia Shield Pro. For now it is the only platform that has the potential to do everything.
I split a lot of my free time between testing with Plex and testing with Nvidia to ensure all video and audio codecs work properly. When it comes to AV setup, I am OCD and strive for perfection. My AV setup is entering into the $100,000 range so I donât want to compromise because of deficiencies and regressions in the source player.
It is easy to get caught up in the passion of AV enthusiasm and forget that using alpha and beta applications come with no guarantee of proper functionality. I can not speak for the Plex staff as to why you all did not get a response to this thread. Rest assured though that I am always championing for full video and audio codec functionality with the dev(s) that work on the AndroidTV appâparticularly for the Shield Pro.
>> And I get funny looks from my family and friends when I tell them Iâve hit the ÂŁ7000 mark, but thatâs just another level AND some !! lol
I am trying to procure the LG OLED97G2 or a Samsung 101" ”LED for my new movie theater room in my new home construction.
Maybe I should clarify. Iâm not saying it doesnât make sense for people to make posts about it, Iâm just saying it doesnât make sense like I donât understand it. Because I have watched this same spider man remux about four times now and I have not been able to see what you are talking about. Thatâs all I was saying. No need to get your panties in a twist especially since it sounds like your issue has actually been fixed while this seamless branching thing has been going on way longer.
Youâre out of line here, bud, and clearly this thread is not for you.
Thatâs the nature of software bugs right? Logic is broken thus a function becomes defunct.
If your prior action still holds true, you wouldnât be seeing an issue with your remux.
just wanna chime in as another user with really, really bad hitching in the current android tv beta (nvidia shield pro) on personal bluray and uhd rips, and flawless playback with the current non-beta player. (wired gigabit ethernet, no transcoding)
low bitrate content seems to play completely fine in the current beta
I believe there is a memory leak at the root of it all.
Much like I suggested quite some time agoâŠ
Put it this way, the buffer hits 512.00MB and then has to flush thus a drop in frames or pauses. It happens every time I observe the stats of the player.
Yeah thatâs actually correct I did roll back so I suppose I never saw this bug regression thing.
