-
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
SmoothStream audio track language metadata is not made available #1095
Comments
@AquilesCanta - Fancy looking at this? |
@bartsidee - Your fix looks good to me (aside from the one comment in just added to one of the ref'd changes). Are you planning to send a pull request to fix this, or do we need to do it ourselves? Thanks! |
…r instead of the track parser
…can access it from the track parser
Created a pull request and a new branch which has dev as origin (current was master) |
Fixed in #1155. |
When we request the Audio tracks on a SmoothStream stream the language attribute on the manifest xml is not made available on the MediaFormat language property return from the getTrackFormat method:
ExoPlayer/library/src/main/java/com/google/android/exoplayer/ExoPlayer.java
Line 327 in 0c060f4
It seems the language attribute is parsed and passed down to the StreamElement
https://github.com/google/ExoPlayer/blob/master/library/src/main/java/com/google/android/exoplayer/smoothstreaming/SmoothStreamingManifestParser.java#L580
But when the MediaFormat instance is created the language property is linked to the TrackElement (not to the StreamElement):
ExoPlayer/library/src/main/java/com/google/android/exoplayer/smoothstreaming/SmoothStreamingChunkSource.java
Line 417 in c9caaad
The TrackElement does not contain the language flag:
https://github.com/google/ExoPlayer/blob/master/library/src/main/java/com/google/android/exoplayer/smoothstreaming/SmoothStreamingManifest.java#L134
As a result the getTrackFormat will always return a MediaFormat with a language set to null, even if the metadata is available on the manifest.
The text was updated successfully, but these errors were encountered: