Transmuxing Error for some HLS streams #7812
Labels
component: transmuxer
The issue involves our built-in transmuxer
priority: P1
Big impact or workaround impractical; resolve before feature release
type: bug
Something isn't working correctly
Milestone
Have you read the FAQ and checked for duplicate open issues?
Yes
What version of Shaka Player are you using?
4.12.5, 4.9.2-caf3, 4.9.2-caf2
Can you reproduce the issue with our latest release version?
Yes
Can you reproduce the issue with the latest code from
main
?Yes
Are you using the demo app or your own custom app?
Demo app
If custom app, can you reproduce the issue using our demo app?
Yes
What browser and OS are you using?
Latest Chrome version, macOS
What are the manifest and license server URIs?
These streams are from Exoplayer's Cast demo app.
HLS (adaptive): Apple 4x3 basic stream (TS/h264/aac)
https://devstreaming-cdn.apple.com/videos/streaming/examples/bipbop_4x3/bipbop_4x3_variant.m3u8
HLS (1280x720): Designing For Google Cast (TS/h264/aac)
https://commondatastorage.googleapis.com/gtv-videos-bucket/CastVideos/hls/DesigningForGoogleCast.m3u8
I don't use any extra configuration.
What did you do?
Tested casting the streams from the Exoplayer Cast Demo app and they gave an error like below.
Also tested at https://shaka-player-demo.appspot.com but still produces errors like:
What did you expect to happen?
These streams were working on Web Receiver if you dont opt-in with
useShakaForHls: true
and add a line likeloadRequestData.media.hlsSegmentFormat = cast.framework.messages.HlsSegmentFormat.TS;
However, after opting-in to use Shaka for HLS streams, they showed errors.
For versions of
4.12.5
,4.9.2-caf3
,4.9.2-caf2
they produce the transmuxing error.Interestingly downgrading my Web Receiver's Shaka version to
4.3.4
makes the firstHLS (adaptive): Apple 4x3 basic stream
stream work. But, produces different error for the second stream like below:Are you planning to send a PR to fix it?
It's probably beyond my level of understanding
The text was updated successfully, but these errors were encountered: