Latest update: Version 2025.25.0.
6 updates, 2 months 3 weeks since first report, issue is still there and hasn’t been fixed yet.
Latest update: Version 2025.26.0.
7 updates, 3 months since first report, issue is still there and hasn’t been fixed yet.
How is this being ignored by the dev team?
1 Like
Im also running into this issue after the update. I identical logs to @Ntn_Grts .
I did notice that Plex thinks my file has EAC3 5.1:
<Stream id="11412" streamType="2" selected="1" default="1" codec="eac3" index="1" channels="6" bitrate="768" language="English" languageTag="en" languageCode="eng" audioChannelLayout="5.1(side)" requiredBandwidths="768,768,768,768,768,768,768,768" samplingRate="48000" streamIdentifier="2" displayTitle="English (EAC3 5.1)" extendedDisplayTitle="English (EAC3 5.1)"></Stream>```
However ffprobe gives a different result EAC3 7.1:
Stream #0:1[0x2](eng): Audio: eac3 (ec-3 / 0x332D6365), 48000 Hz, 7.1, fltp, 768 kb/s (default)
Metadata:
creation_time : 2023-07-06T20:51:24.000000Z
handler_name : E-AC-3 7.1
vendor_id : [0][0][0][0]
Side data:
audio service type: main```
Latest update: Version 2025.27.0.
8 updates, 3 months 1 week since first report, issue still has not been addressed and fixed.
While there is no direct answer as to when this will be fixed there is an official statement about the prioritisation in general and this bug in particular here
Thanks for the link, MG-X.
I’m not saying this EAC3 7.1 playback issue should be at the top of their list. I’m sure there are similar if not more urgent bugs and security fixes which needs to be patched, that we probably don’t know about and was reported a long(er) time ago.
Truth be told, being assigned means nothing if there’s literally 0 progress 3 months in. If I was assigned something at work (and I work as software developer) and I made 0 progress 3 months in.. no - 1 week in - I’d probably be out of a job by the end of that month.
- Clear logos on mobile devices were improperly aligned. (2025.26.0)
- Consent screen only showing up once per install. (2025.24.0)
- Pull to refresh did not work in the friends list. (2025.23.0)
But yeah, I’ll give them the benefit of the doubt. Clearly, stuff listed above are of utmost importance, and they should be in the top priority of their todo list, compared to fixing basic functionality of what the app is supposed to do (media playback) which actually was working fine before they forcefully shoved this broken ass “new experience” down our throat.
Ah well.
I’ll just wait til the next update, post here as a reminder of how long has it been, and be disappointed all over again. It’s gonna be fun if it ever gets to the point of “1 year later: x updates in, issues still exist”
Thanks again MG-X. Hope it doesn’t get to that point, but I wouldn’t be surprised if it did.
Is there anything we can do to help the developers in fixing this issue faster? I already have the beta test flight for iOS app. I think this issue doesn’t trigger much errors so going unnoticed.
The information that was required has been submitted as logs and samples numerous times, so at this point it’s a wait till a release comes ago.
Issue fixed by switching to jellyfin.
Just to add to this, I’m seeing the same on my iPad but as markolonius states using Jellyfin the file plays fine. In fact, not only does the file play, it direct plays (eg no transcoding)
Which in my mind does raise the question of Apple not supporting EAC3 7.1 on iOS any longer as I think was pointed out somewhere in the thread, as it seems to support it in Jellyfin (with the Swiftfin app) just fine
Latest update: Version 2025.28.0.
8 updates / 4 months in since first report, issue still has not been addressed and fixed despite it being easily reproducible with logs, etc. 
Also @chris.round: It’s not an Apple issue because this worked fine before the unnecessary app rewrite / new experience thing they shove to everyone.
1 Like
Probably a good reason why they haven’t pushed this out on the appletv, would be chaos
1 Like
Latest update: Version 2025.29.0.
9 updates in, 4 months, 2 weeks and 4 days since first report. With logs and easily reproducible, issue is still being ignored completely by the team.
3 Likes
2025.30 ddp/eac3 still broken
The latest Public Beta added fixes concerning EAC3. In case this was supposed to fix the descibed issue here, it didn’t work. The issue persists with PMS 1.43.0.10346 and iOS 2025.30
Its not server side, its a flaw in new player, the old tvos/ios 8.45 app plays eac3/dd+ just fine. Luckily its still public and what my sister, mom, etc have.
Latest update: Version 2025.30.0.
We’re up to 10 updates, in the span of 5 months (this is getting ridiculous) since the issue was first reported here. We have provided logs and the bug can easily be reproduced (doesn’t take a rocket scientist), and there’s still no fix to this issue.
Latest update has a bug fix that says
Player: Error messages shown when unable to start playback.
But even the error message is not shown at all when direct playing files with EAC 7.1 audio. It would’ve been a nice tiny step to the right direction if it did, but all it just keeps on loading indefinitely, as it did 5 months ago.
The app literally had one job: play media files. It doesn’t do that, and it’s embarassing.
Absolutely ridiculous lol, hope everyone here knows this is a clear middle finger to all the local media power users of plex, they want you out of here. Go donate and contribute to Jellyfin, at least there the progress is transparent, plex is never going to prioritize this.
“Power users”? Lol DD+ is a basic lossy compressed normie audio format.
Unfortunately I still have to use both media server & client. While Jellyfin is nice and all, I don’t get how we’re close to 2026 and it still has issues with subtitles synchronization, especially during playback / seeking / fast forwarding if a file is transcoding. Yes, there’s the subtitle extract plugin which supposedly helps to mitigate this, but it still happens often enough to be an annoyance.
I read that you’re supposed to turn on automatically burn subtitles. The problem: it is done on the playback client. Not a user setting, not a server-wide setting, but per-client setting. It’s also not enabled by default on new installs for god knows why. It’s.. dumb. So if you have 10 users, you gotta tell all 10 of them to enable it. The official app having two different setting screens aren’t making it easy either. PGS subtitles also doesn’t show up. Swiftin for iOS is the only great app among all other jellyfin clients that I know (even by referencing from awesome-jellyfin/CLIENTS.md at main · awesome-jellyfin/awesome-jellyfin · GitHub ) but even that lacks the ability to transcode and forces direct play. Direct play is good. I can do that with ease so Swiftin solves this problem FOR ME. But where I come from we have ■■■■■■ internet (20Mbps is the norm for most household and it comes at like 10% of the minimum wage here). And not everyone I share my library with have a good enough internet connection. Sometimes they even watch on-the-go. We do have 5G but we’re lucky to get anywhere past 50Mbps with the 5G connection unfortunately.
But that’s another discusson for another day and we’re getting a bit off topic.
I wish Plex would solve this playback issue already. Sheesh.
