Field order corrected on merged m2v files

[Mr_Odwin]

I often create two 23.976fps m2v files and then merge them to create a single m2v using the copy /b command. I run dgpulldown on them to make them NTSC dvd compliant and then author using Muxman.

I obtain the following in a message box when I run DGIndex over the vob files that Muxman creates:

Field order corrected. The original version was saved with the extension ".bad".

Is this something to worry about? Will it cause jerky playback or anything similar?

[neuron2]

You probably mixed TFF with BFF. The corrected file will be OK except that you might get a combed frame at the transition.

[Mr_Odwin]

I have a further question.

I use the following avisynth script:

blankclip(length=2400)
ConvertToYV12()
ChangeFPS(24000,1001)
BicubicResize(720,480)

I encode a progressive stream using HC settings (basically one-pass with a max bitrate):

*CQ_MAXBITRATE 10
*MAXBITRATE 8000
*PROFILE FAST
*DC_PREC 8
*MATRIX MPEG
*ASPECT 16:9
*GOP 12 2
*NOSCD
*WAIT 0

If I run DGIndex on it then a regular d2v file is produced.
If I run DGPulldown (23.976->29.97, creating a new file) and then run DGIndex a regular d2v file is produced.
However, if I run DGPulldown (23.976->29.97, modifying file in place) then DGIndex produces a d2v.bad file.

Here are resulting files for you to check:
http://homepages.nildram.co.uk/~pike/InPlace.m2v
http://homepages.nildram.co.uk/~pike/NewFile.m2v

After writing the above I'm not sure if this is a DGIndex or a DGPulldown issue.

[neuron2]

That's a bug in DGPulldown's in-place mode. Thanks for pointing it out. I will fix it and release a new version ASAP.

[neuron2]

I have fixed the bug. Please see here:

http://forum.doom9.org/showthread.php?t=120769