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 definition of power efficient, remove battery note #221

Merged
merged 6 commits into from
Jul 11, 2024
Merged

add definition of power efficient, remove battery note #221

merged 6 commits into from
Jul 11, 2024

Conversation

marcoscaceres
Copy link
Member

@marcoscaceres marcoscaceres commented Jul 4, 2024

closes #44


Preview | Diff

index.bs Outdated Show resolved Hide resolved
index.bs Outdated Show resolved Hide resolved
index.bs Outdated Show resolved Hide resolved
index.bs Outdated Show resolved Hide resolved
index.bs Outdated Show resolved Hide resolved
@chrisn chrisn requested review from Djuffin and aboba July 4, 2024 09:07
@marcoscaceres marcoscaceres requested review from youennf and removed request for Djuffin and aboba July 4, 2024 09:07
@chrisn chrisn requested review from Djuffin, aboba and jan-ivar July 4, 2024 09:10
@aboba
Copy link

aboba commented Jul 4, 2024

This PR raises the question of whether WebCodecs isConfigSupported() needs to return info on power efficiency. We had assumed that hardware acceleration support was sufficient, but your arguments against conflating acceleration and power efficiency seem sound.

efficient by default, as non-hardware-accelerated codecs can be just as
efficient, particularly with low-resolution video. User agents SHOULD
NOT take the device's power source into consideration when determining
encoding power efficiency unless the device's power source has side
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
encoding power efficiency unless the device's power source has side
power efficiency unless the device's power source has side

efficient, particularly with low-resolution video. User agents SHOULD
NOT take the device's power source into consideration when determining
encoding power efficiency unless the device's power source has side
effects such as enabling different encoding modules.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
effects such as enabling different encoding modules.
effects such as enabling different encoding or decoding modules.

@chrisn chrisn merged commit 9cb1295 into main Jul 11, 2024
2 checks passed
@chrisn chrisn deleted the power branch July 11, 2024 11:04
@tidoust
Copy link
Member

tidoust commented Jul 11, 2024

@chrisn, you didn't integrate your last suggested edits to drop "encoding" and add "or decoding" where the prose was focused on encoding. Is that intended?

@chrisn
Copy link
Member

chrisn commented Jul 11, 2024

Oops, thanks. I'll fix that.

@chrisn
Copy link
Member

chrisn commented Jul 11, 2024

Fixed in 35e5eaa.

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.

powerEfficient needs some objective definition
5 participants