W3C home > Mailing lists > Public > public-media-capture-logs@w3.org > December 2016

[mediacapture-record] Odd overriding of bitrate parameters

From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
Date: Wed, 07 Dec 2016 14:48:57 +0000
To: public-media-capture-logs@w3.org
Message-ID: <issues.opened-194068871-1481122134-sysbot+gh@w3.org>
alvestrand has just created a new issue for 

== Odd overriding of bitrate parameters ==
The current text says about BitsPerSecond parameter:

This parameter overrides either audioBitsPerSecond or 
videoBitsPerSecond if present

"Overrides" normallly means "totally renders them powerless".

It seems natural to say things like { bitrate: 4M, audioBitsPerSecond:
 128k }
to indicate that a certain bitrate should be set aside for audio, 
while video can fill the rest.
OTOH, in

{bitrate: 4m, audio: 1m, video: 5m}

bitrate will clearly render the desired video bitrate null and void.
Should it instead say that bitsPerSecond is capping the sum of the 
audio + video bitrates?

Please view or discuss this issue at 
https://github.com/w3c/mediacapture-record/issues/101 using your 
GitHub account
Received on Wednesday, 7 December 2016 14:49:05 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:27:30 UTC