Ah,... forgot to answer this one.. Am Montag, 9. Juli 2007 22:12 schrieb Michael Riepe: > Hi again, > > Ralph Glasstetter wrote: > > BTW,... just noticed a strange thing... > > > > The variable "pictures" (which I use to export everything... returned > > from generate/loadindex()) is a few frames larger than the last frame > > shown in DVBcut!?! > > > > 11036 instead of 11041 in my example... any idea? > > Probably the difference between index::pictures and index::realpictures. > The latter excludes all frames that can not be decoded because their > reference frame is missing - i.e. B and P frames that are encountered > before the first I frame.
That has to be the difference... linslider->setMaxValue(pictures-1); in dvbcut::open uses the local "pictures" which is returned from load/generateindex, which in fact is realpictures from index::check(). But when I used pictures in dvbcut::exportFile() it seems that I used (implicitely) the global index::pictures, right? It's not very nice to use the same name for two different things... :-( So in exportFile realpictures should be used for the stop picture? And what about the offset index::skipfirst... neither realpictures does include this pictures nor does the index, so it's ok when we start at 0? I'm a little bit confiused... ;-) ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ DVBCUT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dvbcut-user
