After the video starts, all the requests made from the player are intercepted and the validator checks for the CMCD data
In green appear the requests from the player that have correct CMCD data.
In red appear the requests from the player that have incorrect CMCD data.
There are some requests that don't have CMCD data.
Taking a deeper look at the requests that don't have CMCD data, we noticed that those requests without CMCD data are the ones looking for the byte ranges associated at the indexRange of the SegmentBase that's in the manifest.
We found this to be happening only with DASH content that's fragmented mp4.
What did you expect to happen?
For all the requests to the CDN that come out of the player to have CMCD data, including all audio/video and initial requests for the index range of a fragment.
What actually happened?
When a DASH fragmented mp4 is played the initial request asking for the index range of a fragment does not contain CMCD data in the URL (as queryparams). This causes the (our validator) app to report an error.
This happens for both video and audio track requests.
Additional information
The CMCD validator currently has a bug that doesn't list audio requests. It will get fixed under #112.
The CMCD validator is an open-source project, proposed by Will Law at the Monte<video> Tech meetup and developed by Qualabs (organizer of the meetup). You can find the repository here: https://github.com/montevideo-tech/cmcd-validator/
Have you read the FAQ and checked for duplicate open issues? Yes.
What version of Shaka Player are you using?
shaka-player-react: 1.1.5
Can you reproduce the issue with our latest release version? Yes, using latest (at the moment of writing this issue).
Can you reproduce the issue with the latest code from
main
? Haven't tried. Using directly from npm when doingnpm install
.Are you using the demo app or your own custom app? Using own custom application made with react.
If custom app, can you reproduce the issue using our demo app? Haven't tried the shaka demo app.
What browser and OS are you using?
For embedded devices (smart TVs, etc.), what model and firmware version are you using? N/A
What are the manifest and license server URIs?
N/A
What configuration are you using? What is the output of
player.getConfiguration()
?This is the output:
What did you do?
Using the following asset: https://dash.akamaized.net/dash264/TestCasesHEVC/2a/1/TOS_OnDemand_HEVC_MultiRes.mpd This is a DASH fragmented mp4.
Go into: https://montevideo-tech.github.io/cmcd-validator/
Paste the link and click on Start Shaka
After the video starts, all the requests made from the player are intercepted and the validator checks for the CMCD data
In green appear the requests from the player that have correct CMCD data. In red appear the requests from the player that have incorrect CMCD data.
There are some requests that don't have CMCD data. Taking a deeper look at the requests that don't have CMCD data, we noticed that those requests without CMCD data are the ones looking for the byte ranges associated at the indexRange of the SegmentBase that's in the manifest.
We found this to be happening only with DASH content that's fragmented mp4.
More samples from the dashif test assets database:
What did you expect to happen? For all the requests to the CDN that come out of the player to have CMCD data, including all audio/video and initial requests for the index range of a fragment.
What actually happened?
When a DASH fragmented mp4 is played the initial request asking for the index range of a fragment does not contain CMCD data in the URL (as queryparams). This causes the (our validator) app to report an error.
This happens for both video and audio track requests.
Additional information
The CMCD validator currently has a bug that doesn't list audio requests. It will get fixed under #112.
The CMCD validator is an open-source project, proposed by Will Law at the Monte
<video>
Tech meetup and developed by Qualabs (organizer of the meetup). You can find the repository here: https://github.com/montevideo-tech/cmcd-validator/