Server Side Ads Insertion, HLS Live (MPEG2-TS) - Unable to parse start time
See original GitHub issueHave you read the FAQ and checked for duplicate open issues? Yes
What version of Shaka Player are you using? v3.0.4-uncompiled, v3.0.4, master mux.js-5.6.3
Can you reproduce the issue with our latest release version? Yes, v3.0.4
Can you reproduce the issue with the latest code from master
?
Yes
Are you using the demo app or your own custom app? Both
If custom app, can you reproduce the issue using our demo app? Yes
What browser and OS are you using? Google Chrome, 84.0.4147.89 (Official Build) (64-bit) Linux
For embedded devices (smart TVs, etc.), what model and firmware version are you using?
What are the manifest and license server URIs? The stream from https://shaka-player-demo.appspot.com/docs/api/tutorial-ad_monetization.html : assetKey = ‘sN_IYUG8STe1ZzhIIE_ksA’; or without IMA SDK: https://pubads.g.doubleclick.net/ssai/event/sN_IYUG8STe1ZzhIIE_ksA/master.m3u8 (it is reproducible on my own streams as well)
What did you do?
- Follow the instruction https://shaka-player-demo.appspot.com/docs/api/tutorial-ad_monetization.html (Streaming with Server Side Ads Insertion, Live stream).
- Start the page and wait for the playback
Issue reproducible also without IMA SDK: just load the stream on Shaka Player Demo, and try to play: https://pubads.g.doubleclick.net/ssai/event/sN_IYUG8STe1ZzhIIE_ksA/master.m3u8
What did you expect to happen? Playback started, no error messages
What actually happened? CORS error, Error code 4030 No playback
/demo/#audiolang=en-US;textlang=en-US;uilang=en-US;asset=https://pubads.g.doubleclick.net/ssai/event/_JEZWdv1SFuQ2crFV754hg/master.m3u8;panel=CUSTOM%20CONTENT;build=compiled:1 Access to fetch at 'https://dai.google.com/linear/pods/v1/p/_JEZWdv1SFuQ2crFV754hg/2f93c73a-9dc0-4089-afac-18eebc542ef7:GRQ/141548/slate/0/85cb9fffed0691a74715156f4c75ba45/5.ts' from origin 'https://shaka-player-demo.appspot.com' has been blocked by CORS policy: Request header field range is not allowed by Access-Control-Allow-Headers in preflight response.
http_fetch_plugin.js:112 GET https://dai.google.com/linear/pods/v1/p/_JEZWdv1SFuQ2crFV754hg/2f93c73a-9dc0-4089-afac-18eebc542ef7:GRQ/141548/slate/0/85cb9fffed0691a74715156f4c75ba45/5.ts net::ERR_FAILED
hls_parser.js:1720 Unable to fetch a partial HLS segment! Falling back to a full segment request, which is expensive! Your server should support Range requests and CORS preflights. https://dai.google.com/linear/pods/v1/p/_JEZWdv1SFuQ2crFV754hg/2f93c73a-9dc0-4089-afac-18eebc542ef7:GRQ/141548/slate/0/85cb9fffed0691a74715156f4c75ba45/5.ts
The issue is not reproducible on:
- other players: HLS.js, and on our native player - so it seems to be everything fine with the stream
- DASH streams
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (6 by maintainers)
Top GitHub Comments
@joeyparrish are you trolling me? 😃 Please close whatever you like! :p
// Closing as a duplicate of #2615
It seems like this boils down to a duplicate of #2615. @ismena, is it okay to close it as such?