[Matroska-devel] Added lacing
steve.lhomme at free.fr
Wed Oct 15 13:18:03 CEST 2003
Alexander Noé wrote:
> Most of the size elemens you have to code will be small; small enough to
> fit in
> 2 bytes. So a small lookup table could catch most encode inquiries.
>> And the lookup-table is overkill IMO, especially for VBR codex (where
>> any size of frame can occur).
> You could use a lookup table for example for 0-16383 and use normal
> encoding for
> higher numbers. The, all methods, whetever you could possibly think of
> to store signed
> ebml ints, would take the same amount of time.
Mmm, would the lookup table need to be generated on a Block basis ? on a
Cluster basis ? On a file basis ? It sounds like some compression to me.
That's why I think it's overkill. And looking for a size in a table
would take more time than having the size directly.
More information about the Matroska-devel