|
 |
sacredblack wrote:
> Ger <No.### [at] Thank You> wrote:
>> Hi Steve,
>>
>> A trick that I personally have used before is to average frames.
>> Either use a linear average so every frame contribute the same amount to
>> the resulting frame, or use a sin-based average.
>>
>> Linear:
>>
>> (Frame 1 + Frame 2 + Frame 3) / 3 = new frame
>>
>> Sin based:
>>
>> (sin(45) *Frame 1 + sin(90) * Frame 2 + sin(45)*Frame 3) / 2.41 = new
>> frame
>>
>> --
>> Ger
>
> Interesting. Though this looks something like averaging the actual image
> generated ?? Possibly to fix flicker caused by fast moving objects. Not
> sure.
>
Exactly. Assuming you have the whole animation done, as in all frames
rendered, you can average frames 1, 2 and 3 to create a "new" frame 2.
For example, assume pixel (3,3) is "1" in frame 1 and "0" in frame 2, and
"1" again in frame 3, averaging it will make it a bit more the "0" in frame
2 and less then "1" in the other frames.
Averaging also lets you work on tiny bits of the frame, like just section
(10,10) through (20,50) and it lets you decide how much weight you give the
"other" frames. ie. use 20% frame 1, 100% frame 2 , 20%frame 3 to make the
new frame 2. Or the extreme other way. 100% frame 1, 0% frame 2 and 100%
frame 3 to make the new frame 2.
Also, you can "fade in - fade out" the averaging so it would only be applied
to the frames 10 through 20 and not the rest.
> The problem I have (which isn't really clear on my first post) is a
> problem with POVRay rendering detail at only 1 pixel size which changes
> every frame making detailed areas that are small (due to location from
> camera) appear to flicker (there's probably a better word to describe this
> problem these days).
>
> Though I will give your suggestion a go.
>
> Steve.
--
Ger
Post a reply to this message
|
|
