W3C home > Mailing lists > Public > public-webrtc@w3.org > January 2012

Proposal for Hints Information

From: Cullen Jennings <fluffy@cisco.com>
Date: Mon, 23 Jan 2012 08:32:55 -0800
Message-Id: <5A7593E9-0366-4BD1-B7AC-F1E246690E75@cisco.com>
To: public-webrtc@w3.org

Here is a rough sketch of the information I think we likely need in the Hints API. Note all of these are hints and can be ignored. 

For Video: ----------------------------

min / max height 

min / max width 

aspect ratio 

min / max frame rate 

codingPreference - enum with values "detail" "action". This provides a hint of it the video coder should prefer to put bits into temporal or spacial resolution. It could use a better name but I'm trying to pick values where they both are appealing to web developers and do not seem like one is better than other. For example, if we called these "goodDetail" and "badDetail", I doubt badDetail would be used as often as it should. 

preferredCamera - enum of front, back, left, right, middle, presentation, speaker, whiteboard

interactive: boolean indicating if this is for an interactive session or not. This would imply the browser would favor lower latency and shooter GOP sequence 


For audio: ------------------------------

maxChannels - integer. 1 indicates mono, 2 stereo, and so on. 

codingPreference - enum of "music", "speech", "scientific" - Music implies very trying to select a codec that can represent most things we hear. Speech implies this is human speech from mostly one speaker at a time. Scientific means we want to process this in ways beyond what the human ear does and prefer as faithful a reproduction as the original waveform as possible. 

interactive: boolean indicating if this is for an interactive session or not. This would indicate the browser should try and do echo cancelation 
 
disableAudioFiltering - boolean to disable VAD and other noise processing needed E911 

useHeadsetInput - boolean

useHaedsetOutput - boolean 
Received on Monday, 23 January 2012 16:33:23 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 23 January 2012 16:33:24 GMT