- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Sat, 21 Dec 2024 21:47:38 +0000
- To: public-webrtc-logs@w3.org
Note that framerate and resolution aren't comparable metrics (they measure different things). So the term "50/50" is meaningless in this context; "compromise equally" means "take a decision that, in whatever metrics the implementor is optimizing on, will impact both framerate and resolution, in a way that doesn't favor either of the positions described by 'maintain-framerate' and 'maintain-resolution'". If they had been comparable metrics, or if we could find a MOS score-like metric that weighted them in a way that made them comparable, saying something like "50/50" might make sense, but I think we have to be fairly loose here - which means that "balanced" is as much "implementation-defined" as "no value" is. I think we agree on what we want to achieve, it's how to express it that is being questioned. -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/mst-content-hint/issues/37#issuecomment-2558248965 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 21 December 2024 21:47:39 UTC