Hi,

Question...I've been using MeGUI to convert movies to a format compatible with my iPod Touch. I would have posted in the portable video forums but my question is not specific to the ipod but more of a general question.

I'm new to this video conversion stuff...here's my question/situation.

I'm ripping my own movies to my computer for conversion. The source videos are NTSC dvds. I check the vob file and its listed at 29.97 FPS. Here's what's happening. When I use MeGUI's d2v creator, the resulting .d2v file lists the fps on the video as 23.976 FPS. When I use the avisynth script creator using that d2v that lists the video as 23.976 FPS, and I analyze the video, MeGUI lists the video as being progressive. If I use DGIndex manually to create a d2v file, the resuling d2v file lists the video as 29.97 FPS (like the original vob file.) And when I use MeGUI avisynth script creator with the d2v file made by directly using DGIndex and analyze the video, MeGUI lists the video as being FILM and needing deinterlace using TIVTC. I made test encodes using both the d2v/avisynth combo that listed the FPS as 23.976 and no deinterlace (MeGUI's d2v creator tool generated) and using the d2v/avisynth combo that listed the FPS as 29.97 and needing a TIVTC deinterlace (DGIndex generated d2v file.) and they both end up muxig to 23.976 fps.

So my questions are...
1) Why am I seeing different FPS in the D2V files depending on which tool I use to create the d2v file?
2) Why is the avisynth script creator detecting source video as progressive when using one d2v file and FILM with a needed deinterlace when using the other d2v file?
3) Why is the resulting encoded video when using the D2V that lists the FPS as 29.97 FPS end up being 23.976 FPS?
4) Which way should I be doing these encodes? Using MeGUI's d2v creator with its d2v output or using DGIndex myself and using its d2v file?