On 02/28/11 15:35, Bjartur Thorlacius wrote:
On 2/28/11, Harald Alvestrand<har...@alvestrand.no> wrote:
- Let users control access to microphone (whether my app can reach it or
not)
- Let users turn off and on their microphone
Seems to be out of HTML's scope.
I would very much want to avoid having the "record to file/buffer" be a
fundamental part of the microphone abstraction, since it's irrelevant to
my application (if anything should be recorded, it's the conversation,
not the output from the microphone), so I think we should try to find a
model where a microphone is an object that provides a data stream, and
that data stream can be connected to a different object that acts as a
recorder; if I don't need recording, I should not have to instantiate a
recorder.
In effect, you want to create pipelines in JS/ES?
I need pipelines that can be manipulated from Javascript, yes.
Javascript is not a millisecond-precise language; the running of the
pipelines has to happen elsewhere.
