MediaRecorder doesn't respect track addition/removal in source stream
Reported by
thunderc...@theflux.co.uk,
Sep 8 2016
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.101 Safari/537.36 Example URL: https://jsfiddle.net/8eo78o43/7/ Steps to reproduce the problem: 1. Create a MediaRecorder using some MediaStream as a source 2. Remove a track from the source MediaStream 3. Add a track to the source MediaStream What is the expected behavior? MediaRecorder should stop recording the removed track and start recording the new track What went wrong? The MediaRecorder seems to just latch onto the tracks present in the source MediaStream at point of instantiation and does not update if the stream updates. Did this work before? No Is it a problem with Flash or HTML5? HTML5 Does this work in other browsers? Yes Chrome version: 53.0.2785.101 Channel: stable OS Version: OS X 10.11.3 Flash Version: Shockwave Flash 22.0 r0
,
Sep 26 2016
give to media recorder team.
,
Oct 7 2016
mcasas@ what does the spec say?
,
Jan 18 2017
Section 5 "Event Summary" [1] says that an |error| event will be fired if: "An error has occurred, e.g. out of memory or a modification to the stream has occurred that makes it impossible to continue recording (e.g. a Track has been added to or removed from the said stream while recording is occurring)." So, Spec-wise behaviour is good. thundercloud@ if this is non-intuitive I suggest you send a mail to https://lists.w3.org/Archives/Public/public-media-capture/ and/or file a Spec issue in the Spec github repo. [1] https://w3c.github.io/mediacapture-record/MediaRecorder.html#event-summary
,
Jan 18 2017
,
Jan 18 2017
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by ellyjo...@chromium.org
, Sep 14 2016