Server Version#: 1.23.2.4656
Player Version#: 7.19 (1585)
There is no audio from Apple TV 4K (2021) and iPhone 12 PM on tvOS/iOS 15 beta using the latest Plex beta app from Testflight.
Another discussion of this here:
Audio plays correctly if the Old video player is enabled and Direct Play is disabled.
(They let you out of the MR forums?)
3 Likes
Also macOS 12 Monterey Beta has the same issue with audio.
3 Likes
Same issue here across all devices on new betas (iOS, iPadOS, tvOS).
2 Likes
Guess we could have these two threads merged. Not sure how I missed your post which is literally right below this one. 
1 Like
The new testflight build 7.19 (1586) fixed the issue
1 Like
Are you sure? i’m using the newest build and find that it has not yet solved the issue. As a reminder, this only seems to affect certain audio types etc… so maybe you viewed one that doesn’t have the same audio?
You’re right. It seems to affect AC3/EAC3 5.1 audio.
Oddly, I found that switching to PIP will allow the audio to play. Perhaps doing that switches the player/direct play settings, but I’m just throwing it out there in case it helps anyone (in a pinch, or as a dev).
As always - the old player fixes everything.
5 Likes
Any updates on this issue. How do we know if DEVS are actively fixing this?
My fingers are crossed for a new Apple iOS/tvOS beta release today.
I’m also looking forward to a fix. But Plex would be a little bit crazy to chase bugs in a WWDC day 0 developer-only Apple beta.
This issue affects Plex on iOS, tvOS, and macOS. I think there’s a high chance this is an Apple audio toolbox decoder issue.
We’ll make sure everything is working by the time iOS/tvOS 15 is publicly released, but this is only developer beta 1, and not even a public beta of the OS yet, so please be patient and bear with us 
5 Likes
Thanks for the update. Noted and appreciated. Now everyone knows.
1 Like
Good morning. IOS15 beta 2 won’t fix the problem.
1 Like
Did this and it also fixed my problem. Thank you.
1 Like
This problem seemingly persists now through Beta 2, across iOS, iPadOS, tvOS 15 and Monterey. So, looks like it’s here to stay. Are devs actively working to fix this?
These are still betas, and all issues will be resolved prior to public release. I can’t comment on any ETA beyond that, I’m afraid.
3 Likes
Yes. Understood they’re betas, and the risks that come with all that. But this issue persists now through two betas across four different OSes, and for over a month at this point.
The likelihood the issue will persist in future betas and the GM is pretty much absolute, so why not dedicate resources (or have already dedicated resources, by this point) to find and fix the issue ahead of the public release?
Saying we’ll have to wait literal months isn’t a sufficient response when your target demo is power users who are going to disproportionately adopt betas, and when your program is pretty much a daily driver.
So, you’re saying we should just wait months to effectively use your program?
1 Like
I didn’t say you’d have to wait months, only that I cannot provide an ETA, but we will have things resolved prior to the public releases.
2 Likes
