-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Support raw AAC through mux.js #2615
Comments
We can't support raw AAC directly at this time. If mux.js can transmux raw AAC, it's possible we could leverage that to support raw AAC in the future. I'm going to mark this as an enhancement and rename it accordingly. Thanks! |
@joeyparrish |
Checking in to see if this is being considered in the near future to be supported. When importing RTP streams in to AWS MediaLive, we can output video in to various flavors in TS output container. For supporting multiple audio tracks in different languages, however, the only option for output containers with AAC codecs is raw ".aac" segments. It does not appear too support aac audio transmuxed in to TS segments. All native players for various platforms (iOS/tvOS, Android/Android TV, Roku and several other HTML5 players fully support this). We have use cases where ShakaPlayer must be used (such as VIZIO TVs to support DRM) so this limits our ability to have multiple languages on live streams. |
I'm going to close this in favor of #2337 (direct support of raw AAC and other containerless formats), which is on our roadmap for the near term. |
Have you read the FAQ and checked for duplicate open issues?
Yes
What version of Shaka Player are you using?
v2.5.12 (the demo app)
Please ask your question
I'm testing a HLS MPEG-2 TS VOD content, which has .aac audio in Windows 10 + Firefox 76 using the demo app.
The video is being reproduced ok, however there is no audio. The demo app has mux.js so I would assume content is being transmuxed as expected.
I debugged a bit and I ended up seeing that that the stream info for the audio is not being created, as it fails when trying to get the start time from the segment (https://github.com/google/shaka-player/blob/9584804b6cfad07aa4a44e4c7537ef6413c43194/lib/hls/hls_parser.js#L1783) because the mimeType is audio/aac and RAW AAC its not supported.
Manifest looks like
I would like to understand if this is the expected behavior for this type of content or I'm missing something here.
The text was updated successfully, but these errors were encountered: