Re: [mediacapture-main] How is adaptive frame rate to be handled?

Not surprised you get fluctuations; in other experiments with JS 
timing I've observed 10-15 ms delay variation just from the simple 
"wait a bit" function. On my computer, the measurement is between 24.7
 and 25.2 fps; if I turn off the light above my head, I get between 12
 and 13.

If the drivers can't tell what the camera is currently sending, 
something sensible has to happen; if the app were to open the camera 
at the asked-for frame rate, and then observe the frame rate and 
behave accordingly (as described above), I would call that sensible - 
if opening a variable-rate camera in a dark room with frameRate: { 
min: 30 }, this will cause an instant overconstrained event - but 
that's what you asked for, so you should get it.

-- 
GitHub Notif of comment by alvestrand
See 
https://github.com/w3c/mediacapture-main/issues/193#issuecomment-118166410

Received on Thursday, 2 July 2015 20:57:27 UTC