-
Notifications
You must be signed in to change notification settings - Fork 6k
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
LG G5: No sound when playing ALAC audio track #5938
Comments
The m4a stream you posted does contain an ALAC file. The device doesn't have a decoder for this so the track can't be played with the default renderer. When I add the uri to the demo app it gives me the following output:
If you want to play files of that format with ExoPlayer you need to use the ffmpeg extension. |
Well, the android.media.MediaPlayer can play that m4a file without any issue. I'd expect ExoPlayer to play it without the ffmpeg extension since android.media.MediaPlayer can play it. |
I did not manage to play the file on a Pixel 3 with P. Can you give me some details how you did this? |
I'm sorry. I should clarify that I was able to play that file using MediaPlayer on my LG G5 phone. However, ExoPlayer still fails to paly it on LG G5. And you are right that it failed to play with both MediaPlayer and ExoPlayer on Pixel 3. |
….decoder ISSUE: #5938 PiperOrigin-RevId: 261097045
Android considers ALAC initialization data to consider of the magic cookie only, where-as FFmpeg requires a full atom. Standardize around the Android definition, since it makes more sense (the magic cookie being contained within an atom is container specific, where-as the decoder shouldn't care what container the media stream is carried in) Issue: #5938 PiperOrigin-RevId: 261124155
Issue: #5938 PiperOrigin-RevId: 261150349
Fixed in the |
….decoder ISSUE: #5938 PiperOrigin-RevId: 261097045
Android considers ALAC initialization data to consider of the magic cookie only, where-as FFmpeg requires a full atom. Standardize around the Android definition, since it makes more sense (the magic cookie being contained within an atom is container specific, where-as the decoder shouldn't care what container the media stream is carried in) Issue: #5938 PiperOrigin-RevId: 261124155
Issue: #5938 PiperOrigin-RevId: 261150349
[REQUIRED] Content description
The m4a file loads in ExoPlayer without any error. The time bar even progresses normally when it plays but no sound comes out.
[REQUIRED] Link to test content
http://feeds.soundcloud.com/stream/624159534-the-stemma-report-ep05.m4a
[REQUIRED] Version of ExoPlayer being used
2.10.1
[REQUIRED] Device(s) and version(s) of Android being used
Pixel 3 Android P
The text was updated successfully, but these errors were encountered: