[NUT-devel] info packets/frames

Michael Niedermayer michaelni at gmx.at
Wed Feb 15 15:23:30 CET 2006


Hi

On Wed, Feb 15, 2006 at 12:59:50PM +0200, Oded Shimon wrote:
> On Wed, Feb 15, 2006 at 11:25:13AM +0100, Michael Niedermayer wrote:
> > Hi
> > 
> > On Wed, Feb 15, 2006 at 10:34:04AM +0200, Oded Shimon wrote:
> > > TotalTime is unecessary thanks to max_pts in index
> > 
> > ok
> > 
> > 
> > > no more null termination of info packets
> > 
> > ok
> > 
> > 
> > > stream_id coded sperately
> > 
> > ok if multiple stream_ids per info packet are possible
> 
> Hmm, no such possilbity, it's all or one... What's the usefulness?

just a factor of 10 reduction of overhead
for example take a movie with a few audio and subtitle streams, then
lets assume it does contain some info packets which apply to all the streams
like the movie name, and various other metadata ...
now add another audio stream of your favorite music as background music,
none of the "global" info applies so you must duplicate all the info packets
for every stream
or add a fansubbed sutitle stream, many things like studio, producer, director
and so on wont apply to it while they apply to all other streams


> 
> > > seperate to 4 basic types for extendibility, now we can add new fields 
> > > without breaking old demuxers
> > 
> > please elaborate
> 
> If someone makes up a new header, and we decide we like it and add it to 
> info table, using the old method, old demuxers not knowing the new info 
> entry would crap out on the entire info packet because of the v/vb stuff. 
> With the type stuff, it can be done in backwards compatible way, lacking 
> the demuxer just understand the new header...

just store the f* table in the main header :)

[...]

-- 
Michael




More information about the NUT-devel mailing list