W3C home > Mailing lists > Public > public-media-capture@w3.org > May 2014

Re: Capturing streams from DOM nodes: open issues

From: Martin Thomson <martin.thomson@gmail.com>
Date: Thu, 15 May 2014 07:15:31 -0700
Message-ID: <CABkgnnV5LuQYTYUPUXSRbuCiG_sgOULxftayGb5xoZ=HSqZgug@mail.gmail.com>
To: Jim Barnett <1jhbarnett@gmail.com>
Cc: "public-media-capture@w3.org" <public-media-capture@w3.org>
On 15 May 2014 06:49, Jim Barnett <1jhbarnett@gmail.com> wrote:
> 1) are you thinking of an API other than pause/resume for "don't record that
> stuff"?

Yes, because of propagation delays inherent in the application.

1. Stream pauses.
2. Browser generates and dispatches event.
3. Application receives event, processes it.
4. Application issues pause() to recorder.
5. Recorder acts.

The time between 1 and 5 is such that you can't be sure you haven't
recorded at least some dead air.  You could block recording in
anticipation of such an instruction, but that will probably cause
other problems.

And it's far worse in the other direction, where you miss the first
frames of the newly resumed stream.

> 2) under which of the circumstances that you list below would the
> MediaStream "end"?

None of them.  That being the point.  These are cases where the stream
enters a temporary state of suspension.
Received on Thursday, 15 May 2014 14:15:59 UTC

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