On 3/2/2015 9:18 PM, Robert O'Callahan wrote:
Blocking was mainly intended to support three kinds of use-cases: 1) Eliminating spurious "dead time" for recording (or other non-real-time-playback media sinks). For example, if you stream a MediaElement over the network and transcode it to store locally via MediaRecorder, time intervals during which playback was stalled due to buffering should not be recorded.
Are these are features we care about, or will care about? Can we address them in simpler/better ways than with the MediaStream blocking concept? Or should we just ignore them, take out the blocking support, and add it back in if/when we need to?
Recording is a critical use-case that we need to make work correctly. "youtube downloader" addons are a critical use case for Firefox extensions, and now that we're together switching away from Flash to MSE, I think we should have a compelling story for how users will continue to be able to download their youtube videos. I also feel like that's something we should consider adding to Firefox itself, so that "save as" works for videos even if they are delivered via MSE.
I don't have any informed opinion about whether the blocking MSG infrastructure is the best way to achieve that goal.
--BDS _______________________________________________ dev-media mailing list [email protected] https://lists.mozilla.org/listinfo/dev-media
