This allows the identification of a converted view as the needed base view; this means that that view is stored in the file twice (once as a non-base-view and once as a base view). If the use case is purely for servers, we could use hint tracks with ‘fat’ hint samples – but it is not. We could use a combination of data copy-and-rewrite and extractors (or copies) to do some of this. Hm, we might not have dealt with the case that a set of tracks contain the same view coded as base and nonbase, or that that set of tracks contains several apparently base views. Nor do the view declarations in a track indicate whether a view is coded as a base.
We need to label virtual base views, and make sure that either extractors point at them, or this box (or something like it), and that they are not used other than in the track they are in, or tracks that explicitly get them by extraction or by this reference. Then we can include this as well. Editors to find a way to label “in this track this is view N transcoded as a base view” in the sample entry…
Dostları ilə paylaş: |
