Networking/Archive/DASH/Implementation: Difference between revisions

Jump to navigation Jump to search
m
(Add images for high level views of options)
Line 44: Line 44:


: To avoid this, we could require that each segment include extra packets to allow correct decoding.  Or, we can just support no audio adaptation to start with (similar to Apple HLS).  Rob O'Callahan is working on a Media Streams API which includes cross-fading - this may be a longer term solution, after starting with non-adaptive audio.
: To avoid this, we could require that each segment include extra packets to allow correct decoding.  Or, we can just support no audio adaptation to start with (similar to Apple HLS).  Rob O'Callahan is working on a Media Streams API which includes cross-fading - this may be a longer term solution, after starting with non-adaptive audio.
== Use of libdash from ITEC ==
Code from libdash has been released under MPL2.0 by Christian Timmerer and Christopher Mueller of ITEC, Austria.  The plan is to fork the codebase and integrate it with Gecko code.  At a high level this involves switching the DOMParser/libxml and HTTP code in libdash for nsDOMParser and Necko's HTTP code.  As of Feb 16, 2012, this is under way.
This adds extra components in the above high level diagram, namely DASHManager, MPDParser and the MPD classes, as well as the Adaptation Logic.  The following sections will reflect the base design used in libdash including any changes.


== MPD ==  
== MPD ==  
88

edits

Navigation menu