Skip to content
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

Enable Common Media Client Data (CMCD) support in Shaka player #3619

Closed
wilaw opened this issue Sep 1, 2021 · 1 comment · Fixed by #3662
Closed

Enable Common Media Client Data (CMCD) support in Shaka player #3619

wilaw opened this issue Sep 1, 2021 · 1 comment · Fixed by #3662
Labels
priority: P2 Smaller impact or easy workaround status: archived Archived and locked; will not be updated type: enhancement New feature or request
Milestone

Comments

@wilaw
Copy link

wilaw commented Sep 1, 2021

CMCD is a new standard that allows player clients to exchange mutually beneficial data with the CDN to allow the CDN to improve delivery performance and the publisher to retrieve real-time data about the health of their player population. It uses the media requests as the vehicle for transmitting the data. The specification is free to download and use. A working implementation by dash.js is available, as well as hls.js. A presentation on CMCD is available.

The request is for Shaka player to enable CMCD across your platform and browser matrix, with the following features:

  • Have CMCD be default off
  • Be able to activate it easily through single API call. This activation would turn on all available keys.
  • Be able to apply a separate filter list to explicitly enable certain keys. Only keys whitelisted by the filter would be sent.
  • Have an API method to enable setting the ContentID value and the RTP value, both as a fixed threshold and also as a multiple of encoded bitrate.
  • Custom keys - accepting both a key and value arguments.

If you have questions or would like more information about which publishers are interested in deploying this and are gated by the lack of a player implementation, please don't hesitate to contact me.

Cheers
Will Law
Chair - CTA WAVE and CMCD Spec Editor

@joeyparrish
Copy link
Member

Thanks, Will! No objections here. I appreciate your detailed requirements.

We would be happy to work with contributors on a plan for this and review PRs. The core team is currently occupied, though, so I can't promise any specific timeline in which we could implement this ourselves.

@joeyparrish joeyparrish added type: enhancement New feature or request priority: P2 Smaller impact or easy workaround and removed needs triage labels Sep 3, 2021
@shaka-bot shaka-bot added this to the Backlog milestone Sep 3, 2021
joeyparrish pushed a commit that referenced this issue Oct 20, 2021
Add support for including Common Media Client Data (CMCD) in outgoing requests.

Fixes #3619

NOTE: The following fields have not been implemented: rtp, nrr, nor, dl

Co-authored-by: Dan Sparacio <[email protected]>
@shaka-bot shaka-bot added the status: archived Archived and locked; will not be updated label Dec 19, 2021
@shaka-project shaka-project locked and limited conversation to collaborators Dec 19, 2021
@avelad avelad modified the milestones: Backlog, v3.3 May 4, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
priority: P2 Smaller impact or easy workaround status: archived Archived and locked; will not be updated type: enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants