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

feat: Add configuration to ignore SCTE214 supplemental codecs #7455

Conversation

gmcgarry
Copy link
Contributor

SCTE214 Supplemental codecs defines an attribute to AdaptationSet and Representation in the DASH manifest, to define alternative names of the media codec. These attributes are recommended to be used for codec extensions such as Dolby Vision Profile 8.

There are some issues with the ecosystem:

  • MediaSource.isTypeSupported() == true is not guaranteed to always decode the media
  • Browsers may behave differently depending on hardware DRM or software DRM or clear content
  • Necessary to force the base codec for testing and/or work-around platform bugs

For these reasons, having a configuration parameter to disable support for supplementalCodecs is useful.

commit 6a519767d96d9610c6d41b531352b75fdfb14705
Author: Gregory McGarry <[email protected]>
Date:   Wed Aug 7 14:23:20 2024 +1000

    Add missing comma.

commit e3ee8a42d1eec45ae4250fc45d609da3497cc35f
Author: Gregory McGarry <[email protected]>
Date:   Wed Aug 7 12:11:41 2024 +1000

    Add ignoreSupplementalCodecs into the right place for HLS.

commit 65344bc69426d8d46b33a445acac300da7b5ea68
Author: Gregory McGarry <[email protected]>
Date:   Wed Aug 7 09:55:16 2024 +1000

    Also ignore SUPPLEMENTAL-CODECS attribute in HLS manifest.

commit 5a4c9af6320007f0e293ae68fcee4ebb445bba3f
Author: Gregory McGarry <[email protected]>
Date:   Fri Jul 19 14:51:01 2024 +1000

    Provide configuration switch to disable supplementalCodecs.
@avelad avelad changed the title Add configuration to ignore SCTE214 supplemental codecs feat: Add configuration to ignore SCTE214 supplemental codecs Oct 21, 2024
@avelad avelad added type: enhancement New feature or request priority: P3 Useful but not urgent labels Oct 21, 2024
@avelad avelad added this to the v4.12 milestone Oct 21, 2024
@avelad
Copy link
Member

avelad commented Oct 21, 2024

Please fix the lint errors, thanks!

Copy link
Member

@tykus160 tykus160 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add unit test.
Additionally, do you have any device on your mind with this change?

@@ -1189,6 +1190,10 @@ shaka.extern.xml.Node;
* If false, disables fast switching track recognition.
* <br>
* Defaults to <code>true</code>.
* @property {boolean} ignoreSupplementalCodecs
* If false, ignores supplemental codecs
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If true

@@ -1294,6 +1300,10 @@ shaka.extern.DashManifestConfiguration;
* https://www.akamai.com/blog/performance/-using-ll-hls-with-byte-range-addressing-to-achieve-interoperabi
* <br>
* Defaults to <code>true</code>.
* @property {boolean} ignoreSupplementalCodecs
* If false, ignores supplemental codecs
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If true

@avelad avelad added the status: waiting on response Waiting on a response from the reporter(s) of the issue label Oct 23, 2024
@shaka-bot
Copy link
Collaborator

Closing due to inactivity. If the author would like to continue this PR, they can reopen it (preferred) or start a new one (if needed).

@shaka-bot shaka-bot closed this Oct 30, 2024
@shaka-bot shaka-bot removed the status: waiting on response Waiting on a response from the reporter(s) of the issue label Oct 30, 2024
@gmcgarry
Copy link
Contributor Author

I have made some revisions to address the comments. Can this PR be re-opened?

@avelad avelad reopened this Nov 20, 2024
@avelad
Copy link
Member

avelad commented Nov 27, 2024

I have made some revisions to address the comments. Can this PR be re-opened?

Any update?

@avelad avelad modified the milestones: v4.12, v4.13 Dec 5, 2024
@avelad
Copy link
Member

avelad commented Dec 5, 2024

I'm going to create a separate PR with all the necessary fixes, it seems that when you created the PR you didn't check the option to allow maintainers to edit your PR :(

@avelad
Copy link
Member

avelad commented Dec 5, 2024

#7717

@avelad avelad closed this Dec 5, 2024
@shaka-bot shaka-bot added the status: archived Archived and locked; will not be updated label Feb 3, 2025
@shaka-project shaka-project locked as resolved and limited conversation to collaborators Feb 3, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
priority: P3 Useful but not urgent status: archived Archived and locked; will not be updated type: enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants