1,295
edits
Talk:MediaStreamAPI: Difference between revisions
→Processing graph only works on uncompressed data
| Line 28: | Line 28: | ||
Most filter graph APIs have a notion of data types on each stream connection, so encoders, decoders and muxers are possible worker types, as well as filters which work on compressed data; anything that doesn't need to talk directly to hardware could be written in Javascript. As it stands, the API seems to disallow implementations of: compressed stream copying and editing for things like efficient frame dup/drop to maintain sync, keyframe detection, codecs written in javascript, and feeding compressed data obtained elsewhere into the graph. | Most filter graph APIs have a notion of data types on each stream connection, so encoders, decoders and muxers are possible worker types, as well as filters which work on compressed data; anything that doesn't need to talk directly to hardware could be written in Javascript. As it stands, the API seems to disallow implementations of: compressed stream copying and editing for things like efficient frame dup/drop to maintain sync, keyframe detection, codecs written in javascript, and feeding compressed data obtained elsewhere into the graph. | ||
''roc: I think this could be added to the framework outlined here. I don't plan to address these use-cases at this time.'' | |||
== <mediaresource> as an HTML element == | == <mediaresource> as an HTML element == | ||