From a16873b032ea083b12991472fefcf7be99747bcd Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marcos=20C=C3=A1ceres?= Date: Thu, 4 Jul 2024 19:05:54 +1000 Subject: [PATCH] Update index.bs --- index.bs | 21 +++++++++++---------- 1 file changed, 11 insertions(+), 10 deletions(-) diff --git a/index.bs b/index.bs index 6824bfc..c6c050b 100644 --- a/index.bs +++ b/index.bs @@ -783,16 +783,17 @@ spec: encrypted-media-draft; for: EME; urlPrefix: https://w3c.github.io/encrypte

- Encoding or decoding is power efficient when the power draw is optimal. - The definition of optimal power draw from encoding or decoding is left to the user agent but common - implementation strategies would be to consider using hardware as optimal power draw. - User agents SHOULD NOT mark as power efficient hardware encoding or decoding, as - non hardware-accelerated codecs can be as efficient as accelerated ones (for example, with low resolution video). - The user agent SHOULD NOT - take into consideration the current power source in order to - determine the encoding power efficiency unless the device's power - source has side effects such as enabling different encoding - modules. + Encoding or decoding is considered power efficient when the + power draw is optimal. The definition of optimal power draw for encoding + or decoding is left to the user agent. However, a common implementation + strategy is to consider hardware usage as indicative of optimal power + draw. User agents SHOULD NOT mark hardware encoding or decoding as power + 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 + effects such as enabling different encoding modules. +