Skip to content
  • Ronald S. Bultje's avatar
    Riff, EBML, fourcc etc. work. Not fully finished, but better than what we used... · 12e856c2
    Ronald S. Bultje authored
    Riff, EBML, fourcc etc. work. Not fully finished, but better than what we used to have and definately worth a first b...
    
    Original commit message from CVS:
    Riff, EBML, fourcc etc. work. Not fully finished, but better than
    what we used to have and definately worth a first broad testing.
    
    I've revived rifflib. Rifflib used to be a bytestream-for-riff, which
    just dup'ed bytestream. I've rewritten rifflib to be a modern riff-
    chunk parser that uses bytestream fully, plus adds some extra functions
    so that riff file parsing becomes extremely easy. It also contains some
    small usability functions for strh/strf and metadata parsing. Note that
    it doesn't use the new tagging yet, that's a TODO.
    
    Avidemux has been rewritten to use this. I think we all agreed that
    avidemux was pretty much a big mess, which is because it used all
    sort of bytestream magic all around the place. It was just ugly.
    This is a lot nicer, very complete and safe. I think this is far more
    robust than what the old avidemux could ever have been. Of course, it
    might contain bugs, please let me know.
    
    EBML writing has also been implemented. This is useful for matroska.
    I'm intending to modify avidemux (with a riffwriter) similarly. Maybe
    I'll change wavparse/-enc too to use rifflib.
    
    Lastly, several plugins have been modified to use rifflib's fourcc
    parsing instead of their own. this puts fourcc parsing in one central
    place, which should make it a lot simpler to add new fourccs. We might
    want to move this to its own lib instead of rifflib.
    
    Enjoy!
    12e856c2