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

Add EventHandler for Encoder/Decoder power efficiency changes #645

Closed
wants to merge 2 commits into from

Conversation

aboba
Copy link
Collaborator

@aboba aboba commented Mar 1, 2023

@aboba aboba changed the title Add EventHandler for Encoder/Decoder changes Add EventHandler for Encoder/Decoder power efficiency changes Mar 2, 2023

: <dfn event for=VideoEncoder>onEncoderChange</dfn>
:: Fired at the {{VideoEncoder}} when the {{VideoEncoder/powerEfficient}} or
{{VideoEncoder/decoderId}} value changes.
Copy link

Choose a reason for hiding this comment

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

Are these valid references? I don't find an attribute for powerEfficeint on the VideoEncoder or AudioEncoder. The only powerEfficient reference I find is to MediaCapabilities, but that is the capability of a query, not what is used by an encoder atm.

@dalecurtis
Copy link
Contributor

  1. Chrome only has fallback for no-preference when hardware encoder encounters an error. It will try software encoding.
  2. Spec doesn't currently have any language allowing fallback. We could add a note forbidding fallback.
  3. @dalecurtis to gather stats on current fallback mechanism.
  4. Way forward for current users is to specify prefer-hardware or prefer-software which won't trigger fallback in Chrome.
  5. @aboba to ask media WG (Mar 7th) for opinions on whether developers prefer automatic fallback or want explicit control even in no-preference case.

@chrisn chrisn added the agenda Add to Media WG call agenda label Mar 2, 2023
@aboba aboba closed this Mar 16, 2023
@chrisn chrisn removed the agenda Add to Media WG call agenda label Mar 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Information on encoder/decoder performance?
4 participants