The issue was fixed as soon as we noticed the problem in v8.31 with TrueHD, and was released in v8
31.1 - which was published a day after v8.30 was released. However the version got stuck in review at Google, and has only just been made available - its on a staged rollout so its not availabile to everyone yet.
The latest beta (v9.0) that was released today also includes the fix.
In v8.31 we added support for TrueHD at 192kHz, and this caused a regression for normal TrueHD playback which was fixed as mentioned above.
From what I understand, this is due to Google versioning standards. Once you reach minor version x.31.x the next versioning would be to increment the major version number. In this specific case, 8.31.x â 9.0.x
I thought it was something along those lines, but then I checked older major versions, and anything before v8 had many more minor builds. From looking at the changelog it doesnât appear that anything major was added or changed, but who knows. Wondering if 9.0.x has the new demuxer.
Both the current stable and the current beta have the fix and have been approved by Google. Iâm on 9.0.0.31509 right now, and everything seems to work just fine*.
*except for 96kHz TrueHD, which is still âborkedâ, but thatâs another storyâŠ
Which title? I have problem with one title that is VC1 1080i / TrueHD 5.1 96kHz but I am ok with other titles that are both TrueHD 5.1 96kHz and DTS-HD 5.1 96kHz.
The go-to is the UHD release of My Fair Lady. When I tried that tonight, the audio was still dropping in and out, just like with all previous clients. I believe this is an issue with the SHIELD in general, rather than Plex.