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

Re: Proposal for Hints Information

From: Dan Burnett <dburnett@voxeo.com>
Date: Tue, 24 Jan 2012 09:07:05 -0500
Cc: public-webrtc@w3.org
Message-Id: <954413B1-1F86-47FF-884D-ADF324D5490E@voxeo.com>
To: Cullen Jennings <fluffy@cisco.com>
I agree with your axes of information for hints.  However, the lack of flexibility in how they are combined concerns me.  While I might like having 640x480 or 1024x768, I would hate to have to request Height=480/768, Width=640/1024 and end up getting a 640x768 window!  You do list aspect ratio, but the point here is that sometimes my application needs a specific aspect ratio, sometimes it needs specific values of height or width, and sometimes it should have both but with one characteristic (aspect ratio, height, width) having priority.

On Jan 23, 2012, at 11:32 AM, Cullen Jennings wrote:

> 
> 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 Tuesday, 24 January 2012 14:07:46 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:26 UTC