Avisynth: I can see the blur on scene changes!
 

On my last encode I used 1/2 DVD resolution for the first time to fit 180 minutes of dvd material on 2CDs at a CQ of around 72.

On some actually most scene changes I can see the whole frame shift and blur. Peoples faces and other objects seem to tear to the left. It doesn't happen so much in close ups, but more on scenes of medium to long distance. Why can I see this? and how do we get rid of it. Beside that the movie looks fantastic.

I don't think my higher res movies with the MA script do it, because I didn't notice it until now, but I could be wrong.

I take that back. I can see it on closeup scenes also. It doesn't matter how far away the center of attention of the scene is.

Try a Diff Dvd compliant resolution like 528x480
I hope u r using the kvcd x 3 templates :D

I'm using ToK so it has the templates built in. Somehow I don't think it is the resolution, but something in the MA script bluring slightly early because I see it right before the scene changes.

Hi audi2honda...

I see the exact thing you're describing on my latest encode... :cry:
I really feel that it's aSharp blurring that is causing this (chroma shifting), and although it is not as noticable as before, I can still see that on scene changes just as you described. :roll:
I wonder if aSharp is a good filter for blurring... I already PM'd kwag, but he's very busy at the moment, so I'm gonna try some things out myself.
:D

You can try clamping down the maximum value of asharp. Try the following change:
ScriptClip("nf = YDifferenceToNext()"+chr(13)+ "nf > 2.5 ? asharp( -(fmin((nf/30), 0.8)), 0 ) : \
TemporalSoften(2,7,7,3,2) ")

-kwag

Is this still the recommended script modification for tighter scene change detection?

You've got an invalid statement. nf starts with the value of 0. Can't divide zero by anything.

NO :!: This is an old thread :)
The current (and latest!) script is always updated here: http://www.kvcd.net/forum/viewtopic.php?t=3483

-kwag

FYI, you can divide zero by whatever you want. It'll give 0.
It's the opposite that is forbiden.

Yeah, you're right, divide by 0 isn't possible. Should realize when I'm too tired to think. :o

Have you successfully run this modified code? I'm seeing an error from AviSynth:

Script error: invalid arguments to function "fmin"
([ScriptClip],line 3)

There are no errors on the current script. You're probably using an older script :!:

-kwag

If anyone is following this thread, the code snip kwag posted a posts prior to this is outdated. Consider this thread dead. I'm chasing a solution but that post ain't it.