Trouble with VirtualDubMod

[zeromaster]

Hey all, the name's zero, been a part of the .org for a while but I never really joined into the community aspect, but now I need your help.

So, I ripped some Gurren Lagann footage a while ago using DVD Decryptor and made into an AVS script using DGIndex as I always do. A few months ago I made it into an AVI using VirtualDubMod and it came out great. Now recently I went to use the same script in VDM and i found that now the footage is rittled with random interlaced lines of various colors and green bars appear at random on the footage. And it's not just this, footage I ripped and used in this same method today had the same problem. Is there a way I can fix this?

Here's the script that I used:
mpeg2source("J:\GURREN_LAGANN_VOL1\VIDEO_TS\GLep1.d2v")
Telecide(order=1,guide=1)
Decimate(cycle=5, mode=2)

Also all the programs are from the most recent version of the AMVApp

[Mister Hatt]

You can start by realising this is the 21st century. Ditch neuron2shit for TIVTC, delete VDM, and install the latest version of VirtualDub. If that doesn't fix your problem, I would be surprised.

[mirkosp]

I'm actually pretty sure the most recent AMVApp comes with VirtualDub and not VirtualDubMod anyway, albeit an outdated version of VirtualDub anyway.

[zeromaster]

You can start by realising this is the 21st century. Ditch neuron2shit for TIVTC, delete VDM, and install the latest version of VirtualDub. If that doesn't fix your problem, I would be surprised.

Ignoring the blaint ignorance of your first sentence, you suggest the latest version of virtual dub, I was gunna try that but I wasn't sure of the differences between VDM and VD, i'll check it out though. As for TIVTC, i'm not 100% sure what your talking about here, I've only been using VDM because that's what the AMVApp came with and all the tuts I found were for it.

Regardless I'll try VD and see what happens, I'll mod my post with the results.

[zeromaster]

You can start by realising this is the 21st century. Ditch neuron2shit for TIVTC, delete VDM, and install the latest version of VirtualDub. If that doesn't fix your problem, I would be surprised.

Ignoring the blaint ignorance of your first sentence, you suggest the latest version of virtual dub, I was gunna try that but I wasn't sure of the differences between VDM and VD, i'll check it out though. As for TIVTC, i'm not 100% sure what your talking about here, I've only been using VDM because that's what the AMVApp came with and all the tuts I found were for it.

Regardless I'll try VD and see what happens, I'll mod my post with the results.

It seems you can't edit your posts on this forum, either that or I missed it, but anyways tried it in VD 1.9.9 from the developer site and the same problem occurs, not only that I can't import the .VOB files I ripped because of an MPEG-2 error. I don't understand why all the sudden my .AVS is being stupid, maybe i'll try making a new script.

Just tested a new script seems it's the code i'm using that's messing it up. I makes me wonder if the code is out of date or I've just got it wrong, but I've been using the same code for everything and this is the first time I've had an issue like this.

[Qyot27]

Let me put it this way:

Telecide(order=1,guide=1)
Decimate(cycle=5, mode=2)

Is far more likely to fail than it is to remove all telecine correctly, and that was true even when Telecide was the go-to field matching filter (Decimate still has some use for quick-and-dirty framerate halving, but otherwise you're better off with TFM and TDecimate, which are part of the TIVTC package). The only source I've encountered that the above Telecide/Decimate lines worked correctly on was the American domestic release of one of the Inuyasha movies. Nothing else I've seen IVTCs that cleanly with the above. TFM/TDecimate have a substantially higher success rate.


VDub 1.9.9 (well, 1.8.? and above, can't remember the exact minor version) supports input plugins - you can use these to enable MPEG-2, WMV, FLV, DirectShow, whatever input support. Create a folder named Plugins32 in VDub's directory and plop the .vdplugin files in there. When you load up VDub, they should be active. The plugins themselves can be found on the VirtualDub forums (the DirectShow plugin, toward the bottom of the page), or fcchandler's website (MPEG-2, WMV, AC3). fcchandler was the one responsible for the VirtualDub-MPEG2 codebase that VDubMod's MPEG-2 support came from, and the current MPEG-2 input plugin is newer than the input support in either VDubMod or VDub-MPEG2.

[zeromaster]

Let me put it this way:

Telecide(order=1,guide=1)
Decimate(cycle=5, mode=2)

Is far more likely to fail than it is to remove all telecine correctly, and that was true even when Telecide was the go-to field matching filter (Decimate still has some use for quick-and-dirty framerate halving, but otherwise you're better off with TFM and TDecimate, which are part of the TIVTC package). The only source I've encountered that the above Telecide/Decimate lines worked correctly on was the American domestic release of one of the Inuyasha movies. Nothing else I've seen IVTCs that cleanly with the above. TFM/TDecimate have a substantially higher success rate.


VDub 1.9.9 (well, 1.8.? and above, can't remember the exact minor version) supports input plugins - you can use these to enable MPEG-2, WMV, FLV, DirectShow, whatever input support. Create a folder named Plugins32 in VDub's directory and plop the .vdplugin files in there. When you load up VDub, they should be active. The plugins themselves can be found on the VirtualDub forums (the DirectShow plugin, toward the bottom of the page), or fcchandler's website (MPEG-2, WMV, AC3). fcchandler was the one responsible for the VirtualDub-MPEG2 codebase that VDubMod's MPEG-2 support came from, and the current MPEG-2 input plugin is newer than the input support in either VDubMod or VDub-MPEG2.

Alright, thanks, i've been fooling around with VDub but unfortunately I can't get the output to look as good as my one from a few months ago, it's give me either edge bumps or color smears when I try to de-interlace where as my old clip from Feb is flawless, no bumpy edges, no video glitches, no interlacing, no frame blending and it looks spectacular. I just don't understand why all of the sudden it changed when it worked forever until recently

[Mister Hatt]

AMVApp no longer uses those crusty ancient things anyway. Just upgrade regardless. Posting either a screenshot or transcription of the actual MPEG-2 error message that you mentioned might be a good idea too.

[Brakus]

It turns out I'm having the same problem this guy was having. My scripts used to open up without any problem, but now I'm getting that green bar at the bottom of the screen and the weird off-color picture. It looks something like this:



and up until recently, my AVS script looked like this:

mpeg2source("F:\DBKaiOP-ED\DBKai_OP1.d2v", cpu=6).Telecide(1).Decimate(5)
Crop(8,0,-8,-0)
Spline36Resize(640,480)

It seemed to work properly with other footage I've used before, but now I get this crappy image. How do I make it look like it's supposed to again?

[mirkosp]

Does it do this on everything or just this one? Chances are it's just a bad VOB, maybe a ripping error.
I don't think telecide would fuck up that badly...