Beaten to it somewhat, but anyway...
To address these individually:
A) Those Deen settings are way too high, especially for stuff produced over the last, decade, almost - and arguably stuff
released over the past decade, barring some rather horrendously botched authoring jobs or discs produced from bad or inadequate masters, something most discs less than ~6 years old don't generally have a problem with... (unless it's Manga Entertainment we're talking about). A radius of 4 is practically never necessary, as 4 on any of the modes is tantamount overkill, putting aside that you'll be getting other posts pretty soon equating Deen use in general with tantamount overkill.
B) While you could do better to reduce the problem by lowering your Deen settings or using a different smoother, it is possible to isolate sections in videos by using Trim(). To use Trim effectively for what you want to do, however, you need to be comfortable using variables in your script. Like so:
Code: Select all
v1 = YourSourceLoaderHere()
Trim(v1,0,199).YourFilteringChoicesA() ++ Trim(v1,200,399).YourFilteringChoicesB() ++ etc.
'v1' is the variable, although the name needn't actually be v1 - you could call it 'fuwafuwatime' for all AviSynth cares, although that would be rather cumbersome of a variable name to be lobbing around. What each instance of Trim is doing is loading 'v1', a.k.a. your source video, cutting out frames 0-199 or 200-399, and then applying some sort of filtering to them - the fact that AviSynth interprets periods between commands the same way it interprets having each command on a new line makes this possible. Also remember that it starts counting frames at 0, not 1, so if you wanted the first 200 frames you need 0,199 like I showed.
Obviously it requires some pre-planning to know what frame ranges you need. The ++ stitches the segments back together after you've applied filtering to them; in actuality, ++ is shorthand for AlignedSplice, which will maintain audio sync between segments. + is shorthand for UnalignedSplice, which doesn't take audio into account (and thus, + might preserve sync, or it might not; it depends on what you're feeding it).