MediaStream Recording options

A couple more questions about the getOptions/setOptions methods.

First, these APIs look dual, but in fact getOptions returns the set of
available options, not the options that have been set with setOptions.
Should this be renamed getAvailableOptions instead? That the
RecordingSettings and AvailableSettings are different types is a bit
confusing as well. Would renaming the methods be ergonomic enough to go
with a single RecordingSettings type?

Having getOptions return the set of current options might still be a good
idea.

Second. Are the options meant to be user-consumed? That is, is the idea
that retrieved options can be presented to the user? Or is this meant to
just be manipulated directly by app code?

Third. Have you considered options relating to audio sampling? For example
a "audioBitDepth" and "audioSampleRate" might be really nice. I'm guessing
this set of options is intended as the spot where further encoding options
can be added in. How many of these are intended to go here directly as
settings keys as opposed to, say, params on the mime type?

Fourth. "imageWidth" and "imageHeight" sound like photo capture sizes. The
comments on AvailableSettings makes it sound like this is capture size for
video as well, though. Is that right? Will this crop, downsample, or what?
I think this could use some additional documentation. Should these
parameters, for video, echo the names in MediaTrackConstraints? "width",
"height", "frameRate", etc.

Fifth. Is "takePhoto" and associated image parameters redundant to
MediaStream Image Capture? Any reason to have them in both spots?
Presumably the pre-encoding image capture will be lower latency and higher
fidelity.

Thanks!

-Greg Billock

Received on Friday, 19 July 2013 18:44:12 UTC