bond
13th July 2004, 17:58
an old thread, but still the main one for discussing koepis statsreader tool i assume :)
so here is what i found today:
i used statsreader 2.1 (able to open xvid 1.0 style .pass files) to analyse a .pass file i created with xvid 1.0.1
after opening the .pass i noticed that the displayed framenumber showed some frames more than in the input source (i tested virtualdub and virtualdubmod (both latest versions available today), with both the classic dvd2avi/mpegdecoder and new dgindex/dgmpegdec combination)
the .pass file produced with virtualdub showed 1 frame more than the input
the .pass file produced with virtualdub showed 2 frames more than the input
i checked the .pass files manually too: no d/n (delay frames) marked
i used 2 b-frames (no packed bitstream, other b-vop settings on default), gmc, qpel, vhq4, chroma, trellis, aq (well the whole stuff :D )
can anyone reproduce this? can anyone plz try it and check manually (for example in word) whether the number of frames is the correct one in the .pass itself
i assume its an issue in handling b-frames in vd(m), but might also be in statsreader
so here is what i found today:
i used statsreader 2.1 (able to open xvid 1.0 style .pass files) to analyse a .pass file i created with xvid 1.0.1
after opening the .pass i noticed that the displayed framenumber showed some frames more than in the input source (i tested virtualdub and virtualdubmod (both latest versions available today), with both the classic dvd2avi/mpegdecoder and new dgindex/dgmpegdec combination)
the .pass file produced with virtualdub showed 1 frame more than the input
the .pass file produced with virtualdub showed 2 frames more than the input
i checked the .pass files manually too: no d/n (delay frames) marked
i used 2 b-frames (no packed bitstream, other b-vop settings on default), gmc, qpel, vhq4, chroma, trellis, aq (well the whole stuff :D )
can anyone reproduce this? can anyone plz try it and check manually (for example in word) whether the number of frames is the correct one in the .pass itself
i assume its an issue in handling b-frames in vd(m), but might also be in statsreader