- From: guest271314 via GitHub <sysbot+gh@w3.org>
- Date: Sun, 15 Sep 2019 02:19:19 +0000
- To: public-webrtc-logs@w3.org
@jan-ivar It must be noted here that all branches at https://github.com/guest271314/MediaFragmentRecorder besides master https://github.com/guest271314/MediaFragmentRecorder/blob/master/MediaFragmentRecorder.html were written due to the fact that Chromium crashed the browser when trying to record a variable resolution video where HTML `<video>` element `src` was set to `MediaSource`. Initially considered the bug to be `MediaSource`, though that is apparently not the case https://bugs.chromium.org/p/chromium/issues/detail?id=1001948, and Chromium **_still_** crashes the browser when such recording is attempted. Mozilla Firefox and Nightly had and have no issues. The meaning of the above statement of facts is that the goal was and is always to write code that ouputs the same result at Mozilla browsers and Chromium, Chrome browsers. Otherwise would have simply used Mozilla for the purpose of recording media fragments potentially having variable resolution. Therefore, whatever specification change (if that actually does occur) arises from https://github.com/w3c/mediacapture-record/issues/167 should ultimately be implemented at browsers in the same manner, else the words in the specification will be void as to the true intent of the numerous issues that have filed relevant to `MediaRecorder` having the ability to record multiple tracks from varying sources. Perhaps it is not possible for Mozilla and Chromium, Chrome authors to actually work together to achieve a single aim. We shall see. -- GitHub Notification of comment by guest271314 Please view or discuss this issue at https://github.com/w3c/mediacapture-record/pull/186#issuecomment-531528379 using your GitHub account
Received on Sunday, 15 September 2019 02:19:20 UTC