- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Thu, 12 Sep 2024 18:21:20 +0000
- To: public-webrtc-logs@w3.org
> Is the problem not knowing how long to wait to do this step to ensure a clean {360p, off} → {360p, 720p} instead of {360p, off} → {360p, 360p} → {360p, 720p}?
Not knowing how long to wait, but also we don't want to wait as that would be a user visible glitch. But yeah the race is {360p, off} → {360p, 360p} → {360p, 720p} instead of {360p, 360p} -> {360p, 720p}. If it happened it would only be a very brief 360p.
> Is shaving off a few 360p frames a significant saving during this transition to using more bandwidth?
When you phrase it like that, I suppose the momentarily going from 360p -> 720p is similar to normal ramp up. I think the bigger concern is that it may be _confusing_ for the receiver to get {360p, 360p}, but perhaps that's ok.
Do you prefer to allow the 360p in order to keep spec + implementation simpler?
--
GitHub Notification of comment by henbos
Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/222#issuecomment-2346959178 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 12 September 2024 18:21:21 UTC