This is a known issue on the main Plex app, but the workaround there is to go into settings and disable support for EAC3 (which still doesn’t really solve the issue as it forces a transcode, and requires users to really know what they’re doing).
I was hoping this would be fixed on the new app but it’s actually worse. The problem on the new app is that such a workaround doesn’t exist aside from disabling direct play/stream for all content!
This is what I’m greeted with when attempting to play EAC3 content with Atmos metadata present.
I’m experiencing the same issue on a Pixel 8 Pro and and a Pixel Tablet, quite frustrating. I was able to rectify this in the main app by disabling AC3 and EAC3 audio in the client settings, which apparently causes transcoding, but I don’t see those more advanced settings in the new Preview app.
Any chance anyone from Plex can acknowledge these issues? I’m worried that this app is going to launch and be completely useless for a lot of Pixel owners. @BigWheel@RuudBurger
Is there an ETA yet for this? At least to add back the client ability to disable eac3 and force transcoding? I still cannot play files with eac3 audio on my Pixel9 that work on all my other devices. Thanks!
Interesting, maybe I have a different issue. I am unable to play this type of file on my Pixel 9 with Plex 2025.23.0 but it plays on my Samsung S22, FireTV, and iPad. Trying to play produces just a black screen, never plays. Eventually times out with a “Error Occurred” “Source Error”. I have tried many files with this same codec format, always the same. Changing quality from “Original” to anything lower does not help. Appreciate if you have any ideas!
yes the server update for ffmpeg is needed but just running that forum preview will not fix things. There are other server things that need to be done afterwards then a client update when the server can tell it the difference between the two so it only transcodes the one with Atmos
