PDA

View Full Version : Video becomes shorter


loekverhees
15th February 2008, 19:48
Hello,

I've made an AviSynth script with the DirectShowSource-filter. The script loads a MPEG-file. The length of this videofile is 1h57m. But when I open this .avs-file in VirtualDub or in CCE, the length has become shorter, they say the length is 1h12m. How is this possible and how can I solve this?

thetoof
15th February 2008, 21:55
What's the origin of the mpeg file?

If it's a DVD and isn't loaded as a d2v in avisynth, there's a good chance the pulldown flags will be ignored (and therefore some frames will be dropped).

To correct that, use DGIndex with "honor pulldown flags" option turned on and load the d2v with mpeg2source("yourfilepathhere.d2v")

If that's not the source of your problem, please give me more details about your source.

I also recommend reading DGIndex and DGdecode manuals to ensure that you are ripping your files correctly.

loekverhees
15th February 2008, 22:45
The source is a PAL DVD, 720x576 aspectratio: 4:3, progressive. I've extracted the *.mpg with VobEdit. That's all I've done.

Adub
15th February 2008, 22:52
Yeah, you will want to use DGindex whenever you work with vob's, mpegs, and so on.

Load the main movie into DGindex, create an index file, and then load the resulting d2v into avisynth. You shouldn't have any problems.

loekverhees
16th February 2008, 10:06
Thnx, it works! After creating the index-file with DGindex, DGindix said the field order was wrong and that I should run the field order fix tool. Does DGindex make the video interlaced?

neuron2
16th February 2008, 16:01
Does DGindex make the video interlaced? No. Is there something that makes you ask that question?

loekverhees
16th February 2008, 17:36
The window that pops up while creating the index-file says (when it's finished), the frametype is interlaced. But I checked it with MeGUI Interlace Analyser and that program said it was progressive. So the video is still progressive.

That thing with the field order transition, should I fix that?

foxyshadis
16th February 2008, 23:26
The window that pops up while creating the index-file says (when it's finished), the frametype is interlaced.
How the video was encoded.
But I checked it with MeGUI Interlace Analyser and that program said it was progressive. So the video is still progressive.
What the real content is. If it's true progressive, you can just ignore the fact that it was encoded interlaced.

That thing with the field order transition, should I fix that?

The latest versions of dgindex should automatically.

loekverhees
17th February 2008, 09:16
I thought 1.4.9 was the latest version? Where should I get the latest version?

Adub
17th February 2008, 09:40
1.4.9 should do it. 1.5.0 is in testing, but you can download it if you want. It's in it's own sub forum. Just scroll up on the main page a little bit and you will see it.

loekverhees
17th February 2008, 12:42
Ok, thanx. When I open the re-encoded video (with CCE) in MediaPlayer Classic, it says the length is 59 minutes, but when I open it in VirtualDub Mod, it gives the proper length of 1h57m, how is this possible? It seems like MPC plays the video on a higher framerate or something.

neuron2
17th February 2008, 16:44
When I open the re-encoded video (with CCE) in MediaPlayer Classic, it says the length is 59 minutes, but when I open it in VirtualDub Mod, it gives the proper length of 1h57m, how is this possible? VirtualDubMod scans the file and counts the frames to determine the length. MPC uses a heuristic based on the timestamps at the beginning and end of the file. If they are wrong...