Re: validity?
Moritz Bunkus <[email protected]>
| Newsgroups | gmane.comp.multimedia.matroska.devel |
|---|---|
| Message-ID | <[email protected]> |
Hey, > The order is unimportant here. What matters is that a demuxer can find > them, without fully scanning the entire file. So if some elements like > tracks or tags come after the first cluster, they must be linked from a > seek head element before the first cluster. I'd say we should specify > that all level-1 elements that are not clusters, void, or crc elements > must be discoverable in this way. Not really. There's no reason to enforce the presence of meta seek elements if all the other important level 1 elements are located before the first cluster. I guess that's what you actually meant. > This is unnecessarily vague, and I'd say even completely incorrect. Yeah you're right, the cases you've listed are important, too. I was thinking about the order _within_ e.g. track, cues, meta seek heads, attachments… Those don't matter, and demuxers must not rely on any certain order within those elements. > Packets must be in the order the encoder outputs them, and the decoder > expects them. Consequently, what is important is not necessarily the > order of timestamps. I was talking about the order of clusters, not of the blocks of a single track. As clusters contain packets of various differing tracks you cannot impose an order on the clusters themselves that way, only for the blocks belonging to a single track. > The "Timecode" Cluster-subelement must come before any blocks, because > otherwise the demuxer would have to buffer blocks for completely > nonsensical reasons. (You can't feed packets to a decoder without > having the timestamp.) Correct. > It would also be completely ridiculous to demand that the demuxer does > any kind of reordering. I areee for clusters and blocks agree, for other things (like the ones mentioned above, even chapters should probably be sorted by their start timecode within their hierarchy by the demuxer) I disagree. Kind regards, mosu _______________________________________________ Matroska-devel mailing list [email protected] http://lists.matroska.org/cgi-bin/mailman/listinfo/matroska-devel Read Matroska-Devel on GMane: http://dir.gmane.org/gmane.comp.multimedia.matroska.devel
signature.asc
(application/pgp-signature, 819 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAABCAAGBQJVv6LYAAoJEHSvAK3y4yyFY/sQAL212floyVaiJVfBFnfhMJqC 0JgMGJ/CPK2KF4NRvYWlwigywEGeMbDqv2LXZNn3OM88H+nA3RXK8Mb468jEKZd3 FId9mlXJlX7EqerGp3k5/y1/fyKqBr20Ss/cMzw8RvnJZeXT8wcJiT9voD7yCmAg d2A5jTCh7Rs4bMoLs4ncES6sVPujYrJvYVia9d6CGXkI0HmijonC8ysFVWNqVf6Y Z6sKIO/sj9zYx9t3IJBbxu+UUp3/+Ayt80ceRM0rqb3U8rCZwHeO+7wmxVR7E/XD Pfa5QrX6B/1cxXIvVwGCpLH4Ildo9iWNDiuqYqcFs58S9ZIQumTpmUvh8ODfDAu4 1p7K5os24sDzKcWlS1d4LkdBnNoDTnZB+DE6vU49B+A7mPK+6NPiGaOEV1uezvHK CLjUcg/vgtxx/p2jjZLXWOszXjj0TA/GTsKqjxYp8lGu39M9z54teUfl9bICblZE YHO4fZM8ef2kswfNpS2XuSGkYaT7BxT1Rg+6FpejBHi2Zuc58fWRy+/LRcHI3I7p a8fghntO3V5eCn0j9X36lJR55jWGxgLBiBe4z18gUVX8wVEeAfi0x16apueQ11mO CJWR5W89aRq2tk76lhMvNS1r5lIe70aMwoO60tdq4XyEvUviFO/u/Hv6pirXQWGD 3hmV7S0d0t6EyX7/xN5U =Bk1J -----END PGP SIGNATURE-----