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.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?
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.