Problem with DGIndex

[Foo2Bar]

I have Teen Titan Go! DVD9's, Ripped them to HDD using DVDFab and extracted all episodes with PGCDemux (Video, Audio and Subtitles in separate file). So now i have 26 .m2v for each Episode, I used MeGUI's FileIndex Tool to create .d2v project. There are too many file so i decided to use batch script for it instead of doing it for individual files.

So the Problem is with MeGUI FileIndex i get Video FPS to be 23.976 (Progressive) and with the batch Script i get 29.9 (Interlaced). MeGUI also uses DGIndex. But why there is difference when done from command line and when indexed from MeGUI ? Can someone please explain what i am missing ?

My Batch Script

@echo off

set dgindex="F:\MeGUI_2418_x86\tools\dgindex\DGIndex.exe"
setlocal EnableDelayedExpansion

REM filelist.txt contains list of all .m2v to be Indexed

FOR /F "tokens=*" %%f IN (filelist.txt) DO (
SET ftmp=%%f
SET outfile=!ftmp:~0,-4!
%dgindex% -i "%%f" -o "!outfile!" -fo 0 -om 0 -hide -exit
)

MeGUI Command Line taken from log

"F:\MeGUI_2418_x86\tools\dgindex\dgindex.exe" -SD=< -AIF=<F:\Files\TTG1\Episode 2\VideoFile.m2v< -OF=<F:\Files\TTG1\Episode 2\VideoFile< -FO=0 -exit -hide -OM=0

If you want sample for m2v ask for it, I will provide it.
MediaInfo

General
Complete name                            : F:\Files\TTG1\Episode 2\VideoFile.m2v
Format                                   : MPEG Video
Format version                           : Version 2
File size                                : 399 MiB
Duration                                 : 11mn 9s
Overall bit rate mode                    : Variable
Overall bit rate                         : 5 000 Kbps

Video
Format                                   : MPEG Video
Format version                           : Version 2
Format profile                           : Main@Main
Format settings, BVOP                    : Yes
Format settings, Matrix                  : Custom
Format settings, GOP                     : Variable
Duration                                 : 11mn 9s
Bit rate mode                            : Variable
Bit rate                                 : 5 000 Kbps
Maximum bit rate                         : 7 500 Kbps
Width                                    : 720 pixels
Height                                   : 480 pixels
Display aspect ratio                     : 16:9
Frame rate                               : 23.976 fps
Standard                                 : NTSC
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Progressive
Scan order                               : 2:3 Pulldown
Compression mode                         : Lossy
Bits/(Pixel*Frame)                       : 0.603
Time code of first frame                 : 00:59:58;00
Stream size                              : 399 MiB (100%)

[manono]

So the Problem is with MeGUI FileIndex i get Video FPS to be 23.976 (Progressive) and with the batch Script i get 29.9 (Interlaced). MeGUI also uses DGIndex. But why there is difference when done from command line and when indexed from MeGUI ? Can someone please explain what i am missing ?

One was done with Video->Field Operation set for Forced Film (23.976fps) and the other for Honor Pulldown Flags (29.97fps).

[Foo2Bar]

One was done with Video->Field Operation set for Forced Film (23.976fps) and the other for Honor Pulldown Flags (29.97fps).

But the command line parameter used by MeGUI (-FO=0) and by my batch script (-fo 0 ) are same.

{Field Operation -fo 0=Honor Pulldown Flags, 1=Force Film, 2=Ignore Pulldown Flags }

[manono]

Sorry, I know nothing about command lines or batch operations. I only know about DGindex (and not the MeGUI version). Perhaps someone else can help.

[ndjamena]

Your title is wrong, -fo 0 will 'Honor Pulldown Flags' and give a frame-rate of 29.976, which DGIndex is doing perfectly, this is a problem with MeGUI.

[_Al_]

try this:

%dgindex% -IF=[%%f] -OF=[!outfile!]  -fo 0 -OM=2 -IA=5 -HIDE -EXIT

[_Al_]

double post

[ndjamena]

If no one can think of anything better, try switching the '-i' option in your batch script with '-ai' and see what happens...

[hello_hello]

I don't really understand how "force film" is applied by MeGUI but it has an option in it's settings to enable/disable it. I assume it's enabled. The commandline used for indexing doesn't seem to change according to whether it's enabled or not, but when it is and force film is applied, MeGUI tells you about it in the log file.

-[Information] Log for job1 (idx, test.m2v -> test.d2v)
--[Information] [01/05/14 9:58:19 PM] Started handling job
--[Information] [01/05/14 9:58:19 PM] Preprocessing
--[Information] [01/05/14 9:58:19 PM] Job commandline:
"C:\Program Files\MeGUI\tools\dgindex\dgindex.exe" -SD=< -AIF=<E:\test.m2v< -OF=<D:\test< -FO=0 -exit -hide -OM=2
--[Information] [01/05/14 9:58:19 PM] Process started
--[Information] [01/05/14 9:58:19 PM] Standard output stream
--[Information] [01/05/14 9:58:19 PM] Standard error stream
--[Information] [01/05/14 9:58:19 PM] Running auto force film
---[Information] [01/05/14 9:58:19 PM] Film percentage: 100
---[Information] [01/05/14 9:58:19 PM] Applied force film
--[Information] [01/05/14 9:58:19 PM] Postprocessing
--[Information] [01/05/14 9:58:19 PM] Job completed

You can also open the d2v file with Notepad to see whether "field operation" and "frame rate" have been changed.

DGIndexProjectFile16
1
E:\test.m2v

Stream_Type=0
MPEG_Type=2
iDCT_Algorithm=6
YUVRGB_Scale=1
Luminance_Filter=0,0
Clipping=0,0,0,0
Aspect_Ratio=4:3
Picture_Size=720x480
Field_Operation=1
Frame_Rate=23976 (24000/1001)
Location=0,0,0,aa4

If I had to guess.... I'd guess MeGUI gets dgindex to create the d2v file while honouring the pulldown flags, then changes the d2v file to apply force film if the percentage of video which is "film" equals or exceeds the percentage set in MeGUI's options. That makes sense..... but I'm not sure how it does it.
I'm fairly sure the "fix" (or to at least end up with the same result each time) would be to disable "force film" in MeGUI's Options/Settings/External Program Configuration.