Re: Extending MediaRecorder to record from Web Audio node faster than real time?

On Thu, Aug 28, 2014 at 4:26 AM, Chris Wilson <cwilso@google.com> wrote:

> ROC, the challenge I have here is it's quite easy to prevent
> MediaStreamAudioDestinationNode from being created in an offline context -
> we simply remove the constructor from OfflineAudioContext.  There's an open
> issue on this (https://github.com/WebAudio/web-audio-api/issues/308), I
> just haven't gotten to it yet.  But once you can construct a recorder and
> hand it an arbitrary node, we'll have to deal with the interaction between
> OfflineAudioContext and MediaStreamRecorder in some way.
>

Right, but I don't think there's much new we need to say here. Recording an
offline AudioNode is just like recording the stream generated by a
non-offline MediaStreamAudioDestinationNode; the input data just arrives
faster (or maybe slower) than real time.

When a timeSlice parameter is given to MediaRecorder, we have to clarify
that data callbacks arrive every timeSlice-worth of *input* data, not every
timeSlice-worth of real time, since those are no longer even approximately
the same.

This seems like mostly convenience over the current way.  Am I missing
> something?
>

It is only convenience for the online AudioContext case. For the
OfflineAudioContext case it will be the only way to do recording (until we
add full-fledged offline MediaStreams I guess).

Rob
-- 
oIo otoeololo oyooouo otohoaoto oaonoyooonoeo owohooo oioso oaonogoroyo
owoiotoho oao oboroootohoeoro oooro osoiosotoeoro owoiololo oboeo
osouobojoeocoto otooo ojouodogomoeonoto.o oAogoaoiono,o oaonoyooonoeo
owohooo
osoaoyoso otooo oao oboroootohoeoro oooro osoiosotoeoro,o o‘oRoaocoao,o’o
oioso
oaonosowoeoroaoboloeo otooo otohoeo ocooouoroto.o oAonodo oaonoyooonoeo
owohooo
osoaoyoso,o o‘oYooouo ofooooolo!o’o owoiololo oboeo oiono odoaonogoeoro
ooofo
otohoeo ofoioroeo ooofo ohoeololo.