search for: liboggstream

...for the libogg2 convience library, seperating it into two libraries in the effort to allow 3rd party media frameworks to more directly utilize the functions provided by OggFile, while still providing VorbisFile-like convience for the most common uses of Ogg encoders/decoders. In this new model, liboggstream provides the functionality of "codec plugins", inputting and outputting Ogg packets (because Ogg packets are a convient, general form to handle granule-stamped encoded and decoded multimedia data). It will, as per configuration, launch a seperate application when an unknown codec is...

...hich > has already reduced the workload. And anyway, it's a component system, with > controlled memory passing, you can't just chuck a few callbacks at it. OggStream doesn't use callbacks. Go back a few days on the list and read what I wrote about what I'm doing with the liboggstream vs liboggfile split, OggStream is basically an Ogg codec plugin handler, processing data on the packet level only, leaving muxing, seeking, etc to higher level code. It's designed to be used by existing frameworks and is no more complicated than the rest of libogg2. However, if Windows is...

On Tue, Nov 08, 2005 at 04:59:33PM -0800, Arc wrote: > This is also interesting work in that, once we're done, we'll have a standard to > use for a compressed lossless format.. a FLAC for video, for editing or archival > purposes, similar to HuffYUV. Well, we're talking about an uncompressed format. OggMNG is already "FLAC for video". However, it doesn't do