QuadraQ
1st November 2005, 07:21
I've been trying to track down some issues I ran into using MeGUI (See the MPEG-4 and Co. > MPEG-4 AVC forum) and I finally tracked down the issue, but I'm not sure what the history of it is.
Basically when I create a d2v project through DGIndex 1.4.5 directly as opposed to creating it through MeGUI, there is only one difference:
DGIndex 1.4.5:
Field_Operation=1
MeGUI 0.2.2.8:
Field_Operation=1 (0:None 1:ForcedFILM 2:RawFrames)
The extra " (0:None 1:ForcedFILM 2:RawFrames)" is causing issues in MeGUI that result in a 0.0 fps framerate being sent to x264.exe which gets stuck in an infinite loop.
The question is this: Is that extra code obsolete in DGMPGDec, and if so in which version did the change occur?
Basically when I create a d2v project through DGIndex 1.4.5 directly as opposed to creating it through MeGUI, there is only one difference:
DGIndex 1.4.5:
Field_Operation=1
MeGUI 0.2.2.8:
Field_Operation=1 (0:None 1:ForcedFILM 2:RawFrames)
The extra " (0:None 1:ForcedFILM 2:RawFrames)" is causing issues in MeGUI that result in a 0.0 fps framerate being sent to x264.exe which gets stuck in an infinite loop.
The question is this: Is that extra code obsolete in DGMPGDec, and if so in which version did the change occur?