Help With Scripting (Pics Included)

[Kariudo]

doing deinterlacing or IVTC may screw up your sync, but progressive is so much better than interlaced that I think it would be worth it to deinterlace (at the very least) and check to see if you need to re-sync. (Your sync will be better working with progressive footage)

resizing may screw up your AE work

shifting the smoothers and sharpeneners in your script won't affect anything besides the video quality (which you may notice a slight difference, or end up with a more compressible video)

limitedsharpen/faster doesn't mess with frame order, so it won't screw up any editing/effects

[Vivaldi]

I'll beta it if you want.

If you're really worried about something messing up sync, you could just make clips.

[TwilightChrono]

Well, I'm not too good at the making of clips in the AMVApp yet. Still very noobish in that area. The program I mainly use for all of my editing, is Sony Vegas, which I somehow found easier to use than the AMVApp.

As progressive, I'm not too sure how to get it in progressive other than selecting it in the field order option while rendering. If there is another way,let me know. Also, would it be wise to convert to MP4? Or would that screw up the AE in my video as well?

As for resizing, El Hazard is full-screen and I need to put it to widescreen for the final version, but I don't know how to do that without cropping every single cut I have already made to the video.

[Scintilla]

As progressive, I'm not too sure how to get it in progressive other than selecting it in the field order option while rendering.

That may make all your effects render progressive, but it won't change the fact that you have interlacing <i>in your source footage</i> -- After Effects and Vegas won't remove that.

You need to deinterlace or IVTC the source first (see upthread for suggestions), then set your project to progressive (no fields) and set to export the same way. That way the footage is progressive coming in and stays progressive the whole way through.

[TwilightChrono]

I see. But, that would entail, I re-edit the whole AMV. And as I said, I am still really noobish when it comes editing clips and saving them through the AMVApp. As I know that, that makes the editing process easier in case something like that does happen. But, the AMV has already been created and this thread was just to get some advice and help o n what I should do quality wise. I am really appreciative of all the help.

I just don't feel like going back and picking through all the scenes over again, because of this damn quality problem that I am having. It's frustrating.

What was the premiere date of my last AMV? Does anyone here remember? I started working on this one shortly after that one was uploaded here. Hence that should give you an amount of time I have put into this AMV. Alas, I digress.

Is there any other way to fix this problem without having to re-edit all the clips in my entire AMV?

So, no de0interlacing will get rid of this problem without going back? Hmmm.....I can see what I can do with it I suppose. But, more than likely, I will just go with it the way it is. I mean, of course I will script, and fix the grain and all the other quality problems in it, before release.

Also, what filters and scripts are there that can make my AMV's quality go how do you say, above and beyond good quality, but not look over-filtered?

Here are some pics from my afore mentioned script:







As, you can see, the grain is gone and the picture is a lot clearer. However, does it look a little blurry to anyone? It does a little bit to me, but it could just be my eyes. What is everyone else's take on these new pics? If you need to, compare them to the pics on the first page.

Just for reference, the script that was used, to clear up the video I took these stills from was:

FastLineDarken()
Tweak(sat=1.2, cont=1.1, bright=-2)
Awarpsharp(12)
Deen("a2d",4,5,9)
crop(32,6,-32,-6)
lanczosresize(640,480)

I hope this helps, somewhat. What is everyone else's take on this filtered footage? Does it seem blurry to you or no. And if it does, what else can be done in the script?

[Kariudo]

it does look a bit blurry, but part of that might just be the age of the source.
The other part is probably a mixture of deen and awarpsharp

Here's a script I would start off with (and then tweak to your heart's content)

deblock() (or if you're using mpeg2source() put cpu=6 in the mpeg2source call)
removegrain(mode=5)
deen("a3d",2,3,3)
fastlinedarken()
limitedsharpenfaster(edgemode=1, wide=true, strength=50)

[TwilightChrono]

mpeg2source()?

I'm not familiar with that one. Of course, my footage is in Original MPEG2.

So, your saying I should use MPEG2source() in place of deblock()?

Or are you saying I should put cpu=6 in the () of deblock?

Ex: deblock(cpu=6)

or are you saying I should:

Ex: mpeg2source(cpu=6) in place of the delock()?

I'm just trying to make sure I have everything straight, before I attempt the script.

So, I take it I can't get rid of the little bit of blurriness that is there?

[Scintilla]

mpeg2source()?

I'm not familiar with that one. Of course, my footage is in Original MPEG2.

How are you loading MPEG-2 footage into your AVISynth script if you're *not* using <b>MPEG2Source</b> already?

[Vivaldi]

mpeg2source()?

I'm not familiar with that one. Of course, my footage is in Original MPEG2.

So, your saying I should use MPEG2source() in place of deblock()?

Or are you saying I should put cpu=6 in the () of deblock?

Ex: deblock(cpu=6)

or are you saying I should:

Ex: mpeg2source(cpu=6) in place of the delock()?

I'm just trying to make sure I have everything straight, before I attempt the script.

So, I take it I can't get rid of the little bit of blurriness that is there?

Mpeg2source isn't a filter, it's used to load the footage, (ex:MPEG2source("C:\Documents and Settings\Vivaldi\My Documents\My clips\Noein VOBs\DGIndex\VTS_02_4.d2v", cpu=4) )

[Vivaldi]

Also, cpu=6 can cause some blurriness, try using cpu=4 instead.