-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Windows][macOS][iOS][tvOS] M4A audio playback via NetStream doesn't work with AIR 33 #224
Comments
Confirming that this serious issue is still present in AIR 33-1-1-98 on Mac OSx. |
I confirm I have the same issue even with the latest SDK 33.1.1.300. It's really a big problem as now we have other major issues (such as #320) that have been fixed in the latest releases but I can't use them as this is a major problem for our app. |
It works fine with latest AIR SDK 33.1.1.345 for Windows and macOS, but still doesn't work for iOS and tvOS. |
Problem Description
M4A audio files playback via
NetStream
doesn't work with AIR 33 with Windows, macOS and also iOS/tvOS. "Correct" events dispatches and in traces it looks correctly but no audio sound at all.It has been tested with latests AIR 33.0.2.338 and AIR 33.1.0.16 beta with many different Windows, macOS and iOS devices. Also tested with Apple TV 4K A1842 with tvOS 13.3. Tested with different M4A audio files.
Same problem in all cases.
It works fine with AIR 32.0.0.89, AIR 32.0.0.144 with Windows, macOS and Android.
Also It works fine with AIR 33.0.2.338 and AIR 33.1.0.16 beta with Android.
With iOS and tvOS it doesn't work with any AIR version.
NetStream::useHardwareDecoder=false
doesn't help.Related (not the same) issues:
#80
#211
#180
#171
#155
Steps to Reproduce
Launch code below with Windows, macOS, iOS or tvOS device. It will try to play M4A audio file.
Application example with sources and example of audio file attached.
m4a_bug.zip
Actual Result:
Meta data will be received,
NetStream.Play.Start
andNetStream.Buffer.Full
events dispatched but no audio playback.Expected Result:
Audio correctly playback.
Known Workarounds
none
The text was updated successfully, but these errors were encountered: