This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Suggestion: browser should honour user defined format and frame rate. possibly subject to camera providing given format and frame rate, afaict There is currently no defined way to negotiate the video format A camera may offer a variety of formats and frame rates The user may have chosen a desired format and frame rate The browser may auto-select a format and frame rate Evidence: Method: set format and frame rate:** $ v4l2-ctl --set-fmt-video=width=320,height=240 //320x240 $ v4l2-ctl --set-parm=60 //60fps $ v4l2-ctl --all // check current settings load http://www.gnote.org in browser check format and frame rate again: $ v4l2-ctl --all // ie did they change? Results: Chrome v24.0.1312.52 format is changed to 640x480 user defined fps is retained Opera v12.12.1707 user defined format is retained fps is changed to 25fps Firefox 21.0a1 (2013-01-21) format is changed to 640x480 fps is changed to 30fps Tests were not exhaustive, it may be helpful to have other tests, particularly using a UVC compliant camera my apologies if I missed something obvious. ~:" ** v4l2 is a Linux API to control camera output v4l2-ctl provides an interface to this API Camera: Sony Eye Camera available formats: 640x480@15 640x480@30 640x480@40 640x480@50 640x480@60 320x240@30 320x240@40 320x240@50 320x240@60 320x240@75 320x240@100 320x240@125
https://bugzilla.mozilla.org/show_bug.cgi?id=833314 DSK-381252@bugs.opera.com
Discussion of this topic was present in the "version 6" constraints proposal, and should probably be added as an informative section of the spec. Assigning to Dan for now.
Discussion of resolution is added in the May 29 version of the spec: http://dev.w3.org/2011/webrtc/editor/getusermedia.html#the-model-sources-sinks-constraints-and-states It is clear that the browser CAN change the format and frame rate.
Closing as fixed.