Filter Sorting

[Koepi]

Hi,

sorry if I ask a question that has been asked more often already, but I can't find _where_ that was - so I ask again... :-/

I read on some other thread here that a temporal avisynth filter only gets unfiltered images as "last" and "next" frames.
So it must be a difference weather I first crop and than (temporal) filter or vice versa as for a temporal smoother I work with different sized frames then or at least with different locations within this image...

I'm really confused about this matter now, can someone enlighten me please?

Thanks a million in advance,

best regards,
Koepi

[Guest]

A filter requesting frames (whether the current frame or past or future ones) always gets the frames from its parent, i.e., either the preceding source (e.g., avisource()) or the preceding filter. Therefore, all the frames received by the filter will be the same size and that size will be known by the filter. In your context, unfiltered just means not processed by the temporal filter. So there is no problem, at least not one that I can see. :)

[stickboy]

I was just about to post an odd problem I've been having with TemporalSmoother that seems to be related. (I'm using the one from dividee's version of mpeg2dec (http://users.win.be/dividee/avisynth.html).)

In the following script, the first three frames (corresponding to the radius of TemporalSmoother) are black instead of white:
BlankClip(10, 640, 480, pixel_type="rgb32", color=$000000)
Levels(0, 1.0, 255, 255, 0) # invert; produce a totally white clip
TemporalSmoother(5, 3)
Curiously, if I use yuy2 instead of rgb32, TemporalSmoother does the right thing!

At first I thought that in RGB mode, TemporalSmoother just wasn't initializing its buffer properly, but when I use:
BlankClip(10, 640, 480, pixel_type="rgb32", color=$FFFFFF)
TemporalSmoother(5, 3)then the first three frames are white, as I'd expect.

It appears that in RGB mode, TemporalSmoother always gets frames from the source instead of the previous filter.

I thought about working around the problem by duplicating the first three frames, running TemporalSmoother, and then deleting them, but that doesn't work.
BlankClip(10, 640, 480, pixel_type="rgb32", color=$000000)
Levels(0, 1.0, 255, 255, 0) # invert; produce a totally white clip
DuplicateFrame(0)
DuplicateFrame(0)
DuplicateFrame(0)
TemporalSmoother(5, 3)
DeleteFrame(0)
DeleteFrame(0)
DeleteFrame(0)I'm not sure what's going on that...

[stickboy]

Anybody have any ideas? Is this normal behavior?

[Guest]

Ask dividee. Didn't he write it? Generally, we have enough work to do with our own filters to allow time to debug other people's. :)

[stickboy]

I emailed dividee about it over two weeks ago but never got any response.

Koepi's post suggests that similar behavior may occur with temporal filters in general, and what about the DuplicateFrame/DeleteFrame oddity?