mediacapture-record icon indicating copy to clipboard operation
mediacapture-record copied to clipboard

MediaStream Recording

Results 39 mediacapture-record issues
Sort by recently updated
recently updated
newest added

At the moment implementations of the MediaStream Recording API don't write seekable webm files. The WebM format doesn't make this particularly easy, as to write the cues in a useful...

enhancement

Hi all - I'm trying to capture a canvas with expensive draw computations (e.g. variable-length network I/O and complex 3D rendering) asynchronously, separating out the render work from the capture....

enhancement

From https://lists.w3.org/Archives/Public/public-media-capture/2018Feb/0005.html Current specification and implementation also adds an isTypeSupported method which provides drive-by fingerprinting surface, not currently constrained by user permissions or interaction. The current draft of our Mitigating...

privacy-needs-resolution

Alternative fix for https://github.com/w3c/mediacapture-record/issues/167. *** Preview | Diff

TPAC 2019

Videos produced via the MediaRecorder API have highly inconsistent frame rates. Using the same stream settings and MediaRecorder configuration, captured videos can range from average frame rates that are good...

enhancement

The current spec and implementations don't allow a developer to establish the timing of the recording produced in any way accurately. I've been struggling for over 2 weeks to empirically...

enhancement

> I think the Right Solution is to make MediaRecorder have a method that allows you to specify which tracks go with what number in the container-dependent ordering. This change...

enhancement

The description of pause and resume is not very clear to me. The spec says that: - Stop gathering data into blob (but keep it available so that recording can...

editorial

The spec states that: "the individual Blobs need not be playable, but the combination of all the Blobs from a completed recording MUST be playable". This does not put any...

enhancement

Chrome and Firefox do not seem to agree on edge cases related to firing start and stop events when synchronous calls are made. See for instance https://jsfiddle.net/ukqwrvL3/ or https://jsfiddle.net/1kxtpefw/. From...