Had to dowload the newest app again

[Enigma]

You might wanna change DirectShow Source to MPeg2source if you are working with DVD footage......

[Scintilla]

DirectShowSource("C:\AJBackup\Jim\Converting folder\Gurren Laggan\VTS_06_1.VOB")
Telecide(order=1,guide=0)
Decimate(cycle=5, mode=2)
FastLineDarken(150,100,4,0)
Tweak(bright=3)

It still says: Script error: there is no function named "FastLineDarken" (gl3.avs, line 4)

Now, this is good since I used to get a flat out error box saying there was no "FastLineDarken". where I would normally preview my video in AvsP is where the error is.

It's called FastLineDarkenMod now (see the code). Fix that and it ought to work.

[Qyot27]

Paste it into Notepad, and when you go to save it, select All Files and append .avsi to the end of the filename instead of .txt. There's no reason why that shouldn't work; just make sure you copy the entire contents of the code box, from the very first # sign to the last }.

Actually there is one reason that should not work: he should also make sure to pick "All the files (*.*)" instead of "Text document (*.txt)" in the save as pulldown menu of notepad's save window. Otherwise, even if he saves as .avs, I think that windows will save the file as .avsi.txt which wouldn't work.

I did say to switch to All Files.

In any case, changing the extension through Windows Explorer would still work if something did go wrong, so long as it's set to show file extensions in the first place. AVS and AVSI are just plain text files anyway (speaking from a mime-type standpoint). The only formatting problem that might arise is if Windows is automatically saving text files in UTF-8 instead of ANSI - AviSynth doesn't support UTF-8. XP doesn't do that, and I don't think Vista does either, but I've not worked with Win7 to know for certain if it does or not.

[OzzieAlThor79]

Worked. Would converting to YV12 possibly mess up any interlacing I have done? Certain clips I made before didn't have interlacing and those same ones, when I run it through VDM and AvsP, see to have an issue.

Also, When I run things through VDM, now I get a slight rewind-skipping of the footage. Like once every few minutes it will jump backwards a few hundred frames just for a second and then hop back to where it's supposed to be. Is this common with this FastLine thing?

Or is it because AvsP seems to be defaulting to DirectShowSource instead of the mpeg2source that I was using on my previous computer?

[Qyot27]

Worked. Would converting to YV12 possibly mess up any interlacing I have done? Certain clips I made before didn't have interlacing and those same ones, when I run it through VDM and AvsP, see to have an issue.

Also, When I run things through VDM, now I get a slight rewind-skipping of the footage. Like once every few minutes it will jump backwards a few hundred frames just for a second and then hop back to where it's supposed to be. Is this common with this FastLine thing?

Or is it because AvsP seems to be defaulting to DirectShowSource instead of the mpeg2source that I was using on my previous computer?

DVD footage is already YV12. You were doing inverse telecine, which removes it, not adds it. The problem may have simply been that Telecide/Decimate has been outdated for several years and the recommendation is to use TFM/TDecimate instead.

The very first step you should take when working with VOB files is to open them in DGIndex and save the index file and script (to output the script you need to set up DGIndex's template function*). Then open that script in VDubMod or AvsP to continue editing.

*To do this, create a script in DGIndex's folder and name it template.avs. Open this script in notepad and paste the following into it exactly as it appears below:

MPEG2Source("__vid__", ipp=true, cpu=4)
deint = TDeint(mode=2, mtnmode=3, blim=100)
TFM(order=-1,mode=5,PP=7,field=-1,slow=2, clip2=deint)
TDecimate(mode=1)
AssumeFPS(24)

(the only absolutely necessary part of that is the MPEG2Source line, but it's easier to put the rest in there too instead of typing all that out or copy/pasting it for every single script you make; if it's wrong, then change it later)

Now, in DGIndex, go to Options->AVS Template. Click 'Change Template File' and select the template.avs you just saved. That's it. Now, whenever you index a VOB with DGIndex, it will automatically create a script in the same directory as the .d2v file that has the IVTC operation and AssumeFPS(24) already there.

[Scintilla]

Careful with that AssumeFPS(24). The only reason this should be in there is if your video editing software doesn't properly support 23.976fps, like Adobe Premiere up to Pro version CS2 or CS3. Otherwise it'll just make things needlessly confusing.

[OzzieAlThor79]

I'll give this a whirl. I'll try with and without the FPS line and see which works better.

[Qyot27]

Careful with that AssumeFPS(24). The only reason this should be in there is if your video editing software doesn't properly support 23.976fps, like Adobe Premiere up to Pro version CS2 or CS3. Otherwise it'll just make things needlessly confusing.

Yeah, I'm still on Premiere 6.5. I don't really find the BeSweet method confusing, though; use the time-corrected one in your editor, and only use the original copy after you've AssumeFPS'ed the exported footage back to 23.976 - which would only be at the end, when preparing final encodes of everything.

So CS4 (and upcoming CS5) do properly support 23.976, and not just claim to? I remember that was a problem with some of the early Pro offerings.

[Scintilla]

Careful with that AssumeFPS(24). The only reason this should be in there is if your video editing software doesn't properly support 23.976fps, like Adobe Premiere up to Pro version CS2 or CS3. Otherwise it'll just make things needlessly confusing.

Yeah, I'm still on Premiere 6.5. I don't really find the BeSweet method confusing, though; use the time-corrected one in your editor, and only use the original copy after you've AssumeFPS'ed the exported footage back to 23.976 - which would only be at the end, when preparing final encodes of everything.

Oh, neither do I -- I'm still on Premiere Pro (1.0), so I've been editing with the time-correction method for six years.
I'm saying it could needlessly confuse someone whose editing program does properly support 23.976, because then if you want to send it to a contest that wants the fractional frame rates, you'd have to do the time-correction part; whereas if you skip the AssumeFPS(24) and just edit at 23.976, you wouldn't need all of that.

So CS4 (and upcoming CS5) do properly support 23.976, and not just claim to? I remember that was a problem with some of the early Pro offerings.

I don't remember encountering any problems the one time Cyanna tried it with Premiere Pro CS4, but someone who's done more editing with those systems recently would be better able to address this.

[LantisEscudo]

PP2 and up correctly handle 23.976. I've worked with it without issues in both PP2 and CS4 (never tried CS3, but I'd assume it works, since the versions before and after both do).