@kwag

I've noticed that the blurred frames on both "sides" of a scene change is clearly visible when watching the encoded movie (encoded with the latset script (June 14, 2003 @17:18GMT)) on a standalone DVD . What's the problem? I didn't noticed this when I was using the script from June 8...

-audioslave

@ audioslave..

I noticed it too, but you don't see them when you are playing them.
However, I can't help but to think that it may have a dragmatic affect
on final encoded "size", (maybe even effect the Q somewhat) when performed through a whole movie w/ lots of scene changes. Some tests
would have to be run.

How about this...

If you want to use the June 8th script, then just re-read the posts that
Kwag and others made, in reference to those changes back then.
Unfortunately, you have to SEARCH through ALL 31+ pages, but you
shouldn't have much dif. locating "June 8th" is you add it in the search

Good luck.
-vhelp

Here's the script from june 8th, you'll have to change the values to what you want though

## DLL Section ##
#
LoadPlugin("C:\Filters25\MPEG2Dec3.dll")
LoadPlugin("C:\Filters25\STMedianFilter.dll")
LoadPlugin("C:\Filters25\asharp.dll")
LoadPlugin("C:\Filters25\undot.dll")
#
####

## Defined Variables and Constants ##
#
MaxTreshold = 1.50
scd_trigger = 25 # Scene change trigger value.
nf = 0 # Current frame.
#
####

## Main section and static filters ###
#
Mpeg2Source("C:\DVD\T2.d2v")
#
undot()
Limiter()
asharp(2, 4)
BicubicResize(352,240,0,0.6,0,0,720,480)
STMedianFilter(8, 32, 0, 0 )
MergeChroma(blur(MaxTreshold))
MergeLuma(blur(0.2))
#
#

## Dynamic Linear Adaptive Filtering and Scene Change Detection ##
#
# ( Portions from AviSynth's manual ) - This will apply temporalsoften to
# very static scenes, and apply variable blur on moving scenes.
# We also assign a variable - and this is why a line break is inserted:

ScriptClip("nf = YDifferenceToNext()"+chr(13)+ "nf > 2.5 ? asharp( -(fmin((nf/30), 1)), 0 ) : \
TemporalSoften(2,7,7,3,2) ")

#
# Scene change detection ( kwag ) - If a scene change is detected, we
# blur heavily. This affects the scene before and the one after the
# scene change, thus providing a softer transition for the encoder instead
# of a sharp "spike".
# If it's not a scene change, then we just blur dynamically, depending on
# the action.

ScriptClip("nf > scd_trigger ? asharp( -2,0) : asharp(0,0) ")

#
#
#

#LetterBox( Your_Values_Here ) # Depends on situation. Use MovieStacker!
AddBorders(0,0,0,0) # Depends on situation. Use MovieStacker!
Limiter()

#
#
## Functions ###

function fmin(float f1, float f2) {
return (f1<f2) ? f1 : f2
}

#
####



David

Hi audioslave,

If the blur is too noticeable for you ( because you have eagle eyes ), change this line:

ScriptClip("nf > scd_trigger ? asharp( -2,0) : asharp(0,0) ")

To read:
ScriptClip("nf > scd_trigger ? asharp( -1,0) : asharp(0,0) ")

That will blur the frames adjacent to scene change much less.

-kwag

Kwag,

How much of an effect on file size do you think the -2 to -1 change in asharp create?


Grantman

Not sure, but it should be maybe around ~1%. I'll stick to using -2, because I can't see any visual changes using -1 or -2. However, I DO notice that if motion estimation is not set to"Motion Estimate" with the new script, and I use "High quality", the blured transitions are somehow "bleeded" to a following frame and I DO notice something in the picture. So I'm definitely sticking to "Motion Estimate(fast)" from now on

-kwag