There are three causes for the frame loss in the faulty versions.
So, for example, if you edit a VOB and the resulting file has an IBBPBBP... opening GOP, you will lose a total of 5 frames, with 2 lost at the start and 3 lost at the end.
In addition to the lost frames, MPEG2DEC does not implement random frame access correctly. In fact it always throws away the first B frames in the GOP prior to the first P frame. If they are (say) frames 12 and 13 (in display order) and you try to seek to 12, MPEG2DEC will toss them and return frame 14 to you, without any warning or indication about it.
Finally, when 3 above applies the TFF/RFF flags in the D2V file are misaligned to the frames.
I have created fixed versions of DVD2AVI and MPEG2DEC3 that solve these problems. I modified MPEG2DEC to not truncate B frames prior to the first P frame and to not unconditionally reduce the frame count by two. I rewrote the decoding and random access code to work correctly with the D2V files generated by the fixed DVD2AVI.
For DVD2AVIdg, if your input stream starts with an open GOP, a message box will pop up warning you that the first few frames may not be decoded properly, but the frames will be retained. To avoid this problem, always cut your VOBs on cell boundaries. Do not make arbitrary VOB cuts with a binary splitter (such as VOBSplit).
These fixes currently apply only when Save Project is used in DVD2AVIdg and then MPEG2DEC3dg.dll or DVD2AVIdg.vfp (VFAPI) is used for decoding. Future versions may add support for DVD2AVI's Preview and Save AVI features.
DVD2AVIdg and MPEG2DEC3dg are intended to be used as a pair. If you use faulty versions of either of them, incorrect and/or undefined behavior may result.
DVD2AVIg is baselined off DVD2AVI version 1.77.3. MPEG2DEC3dg is baselined off MPEG2DEC3 1.10.
Copyright (C) 2003, Donald A. Graft, All Rights Reserved.