- From: Tackoil via GitHub <sysbot+gh@w3.org>
- Date: Wed, 15 Jan 2025 05:58:18 +0000
- To: public-webrtc-logs@w3.org
Thank you for your reply. But I think there is still some strange thing to be discussed. Virtual cameras will usually not change their output resolution following the request from browsers or some other software. (Maybe limited by OS, I think.) Only the user of virtual cameras may change it as they desired. If the virtual cameras claim their capability with a huge range of width/height, following the rules of *If they are not known, then theoretical min/max values can be used*. As a fact, they may not deliver their promises unless matching the user setting coincidently. The following figure may describe it intuitively.  At the position of question mark in figure, the user agent may have two solutions in my mind. 1. Stretch the video stream to fit the initial settings, but the web user will get a stream with unexpected image. 2. Destroy all initial settings to match the new resolution, but the web user will get a stream with unexpected resolution. I'm not quite sure which is better, or is there any better solution for this situation? -- GitHub Notification of comment by Tackoil Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/1027#issuecomment-2591714111 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 15 January 2025 05:58:20 UTC