Doom9's Forum - View Single Post

Isochroma · 15th December 2005, 23:56

Using MKVMerge 1.6.5, muxing DivX 6.11 files I noticed that frame 0 of the avi file is eaten, when muxed in either native mpeg-4 mode or VFW mode. This occured whether or not b-frames were used in the avi file. If b-frames are enabled, the entire video clip loses 3 frames, and frame 0 is eaten.

This is using DirectShowSource() and VirtualDub to check the frame alignment.

Are these two items features, or bugs? Are there any undocumented switches to prevent frame 0 from being eaten? I can understand the b-frame delay, though...

15th December 2005, 23:56	#32 \| Link
Isochroma Registered User Join Date: Mar 2005 Posts: 468	Frame 0 eaten by MKVMerge Using MKVMerge 1.6.5, muxing DivX 6.11 files I noticed that frame 0 of the avi file is eaten, when muxed in either native mpeg-4 mode or VFW mode. This occured whether or not b-frames were used in the avi file. If b-frames are enabled, the entire video clip loses 3 frames, and frame 0 is eaten. This is using DirectShowSource() and VirtualDub to check the frame alignment. Are these two items features, or bugs? Are there any undocumented switches to prevent frame 0 from being eaten? I can understand the b-frame delay, though...