Problem with AVISynth/DVD2AVI

[AbsoluteDestiny]

I don't know why version 1.86 fixes things... but given that lots of people seem to have this problem I may put 1.86 in the next release of the amvapp.

[SpPANDA]

what about deinterlacing?

is there a simple code for that?

my source seems to like being being interlaced regaurdless of what i do to it.

[the Black Monarch]

You know, I had this EXACT same problem, but upgrading DVD2AVI to version 1.86 and re-writing the project file didn't fix jack squat!

*cries*

[WilLoW :--)]

Mmm, currently having the same problem...

OS : Win XP
DVD2AVI & AviSynth : the ones from AMVApp (Dvd2Avi 1.76)
Proc : Duron 700

I'll try to download Dvd2avi 1.86 and see...

[WilLoW :--)]

yep, it worked with DVD2Avi 1.86 for me.

[sleet01]

I have:
2 x P3 500, Premiere 6.5

I had the same problem listed above; with an upgrade to AviSynth 2.5
_and_ installation of the Source Forge plug-in pack, plus the newest ver.
of MPEG2DEC3.dll and DVD2AVI, I was in business. Of course, I also re-ripped and rebuilt my .d2v files, just to be sure, but it works great...

...but now I'm having a new problem.

I ripped a couple of discs of Trigun, and they seem to work fine; I'm using ErMaC's fast-avi editing system, and _that_ works fine... except with my most recent rip. When I switched out the .avi files as a test of the technique, I found that all my clips transferred well, except for the rip of disk #3, in which I removed all the ops and eds during ripping. Now, the .avi file was made from the .avs of this .d2v file, so they should be identical. But, in fact, the clips from disk #3, when switched from the AVI to the .avs file, are slightly (~10-30 seconds) off. It's as if the .avi file is faster than the .avs file. I'm recreating the .d2v and .avi files now, but I'm wondering if it's common for files to be incompletely or incorrectly coded. Has anybody else had this problem?

[klinky]

The usual cause of the two being out of synch is one was IVTC'd and the other wasn't. So you have a 23.976 file and a 29.97 file :\

Take the AVI into VirtualDub and goto File|File Information, check the frame rate and frame count. Then do the same for the AVS. See if they differ at all.

Other then that there really isn't much reason for them to be different.

[sleet01]

I checked everything; what makes it so puzzling is that the timestamp, framerate, and number of frames all match, but the files themselves are considerably different.
I went through the .avi file nearly frame-by-frame this morning, and it turns out that the .avi file actually contains two copies of a ten-minute stretch of the .avs version. The second copy was appended to the end of the shortened copy of the original:

|<----~53 minutes of footage from 1:03 of .avs--->|<10 min of extra>|

It's as if the .avs script is doing the IVTC twice, dropping too many frames and trying to compensate for the file length disparity; the possible explanation I can come up with is that, because I didn't copy the ops and eds when I first ripped the .vob files, there's some irregularity in the .d2v or .vob file that AviSynth can't handle while actively frameserving. The really _really_ wierd thing is that when I preview the .avs file in VirtualDub or Premiere, it's choppy (of course) but A-okay. Is this an AviSynth deal, or is it VirtualDub, or what? The .avs file is identical to my previous rips, except for the file name; the .d2v has been rebuilt twice, as has the .avi file. If nobody has any ideas, I'll have to re-rip and re-code everything from scratch; help me, please!

Martin