mediacapture-record

The MiniDV analogy is a really good one for explaining how MediaRecorder works, but also a good one to explain why it is a poorly designed API. The video needs to be stored for its consumption, like any video, in a container format (like MP4 or Matroska) and these formats more often than not, require to revise what was initially written and rewrite some chunks when the recording has finished up. (I'm talking here about e.g. metadata that goes at the beginning of the file but the actual values cannot be known until the file is complete) I wonder how you guys at Mux handle this limitation of the API; do you store the recorded videos at all on file? You would think an API meant to generate some type of video, would be ready to properly do it, right? Or as someone put in a way that made me laugh (from the Chrome bug report, linked below at [1

I guess this could be used to remux the broken files that are spitted by the MediaRecorder API, which have missing metadata that prevents from seeking and thus far has been ignored / sweeped away in Chrome [1], Firefox [2], and even the standard itself [3], which ignored in its design the basic fact that encoding any file should include a "closing" stage (where metadata is written) before yielding it as a finished file. [1]: https://bugs.chromium.org/p/chromium/issues/detail?id=642012 [2]: https://bugzilla.mozilla.org/show_bug.cgi?id=1283464 [3]: https://github.com/w3c/mediacapture-record/issues/119

In general async executions really are big sources of race conditions in single threaded program. JS avoids this problem by blocking/queuing tasks until the current task is done but this is not the case in most lower-level environments. 1. Reentrancy. Flow of tasks can be interrupted by hardware interrupts and OS signals. In that case race conditions can happen by interrupt handlers. Bare metal embedded system programmers often have big headaches because of this. 2. JS implementations and JS API design can have race condition bugs. So JS API designers have to consider it. One of example is because of the order of queuing tasks/handlers. [1] [1]: https://github.com/w3c/mediacapture-record/issues/150#issuec...