Page 1 of 1

flicker, tool should not look at "tails"

PostPosted: Thu Apr 19, 2018 10:59 pm
by waltervolpatto
Wr need the de- flicker when we are doing restoration, if you scan a final piece, you will use the cut detect to cut the piece therefore the "tail" is the previous/ next cut.

That make both the temporal Denise and the deflicker really unusable because the the tool will look beyond first and last frame: basically looking at "tails" that are completely different shots.

So, there should be a checkbox to tell the temporal tools to limit the action to "visible frames" or "use the tail" (normal behaviours).

Re: flicker, tool should not look at "tails"

PostPosted: Thu Apr 19, 2018 11:44 pm
by Andrew Kolakowski
It's poor design. Any decent or even semi decent restoration tool should detect cut (perform actual cut detection on the fly) and don't take "wrong" info into account. This is quite fundamental feature for temporal based filters.
Resolve has cut detection option, so this should be built-in into all filters which do need to be aware of scene changes. You should not need to have scenes to be already pre-cut.

Re: flicker, tool should not look at "tails"

PostPosted: Fri Apr 20, 2018 3:45 am
by waltervolpatto
I'm ok with cutting, just tell the tool to work with visible cranes only

Re: flicker, tool should not look at "tails"

PostPosted: Fri Apr 20, 2018 8:41 am
by Sam Steti
Yep Walter, I agree... I had the same issue with the denoiser; I also remember I had this issue with old Apple stabilizer which was not able to restrict its search area to the cut clip, it looks the same here, unfortunately...

Re: flicker, tool should not look at "tails"

PostPosted: Fri Apr 20, 2018 1:58 pm
by Rohit Gupta
waltervolpatto wrote:Wr need the de- flicker when we are doing restoration, if you scan a final piece, you will use the cut detect to cut the piece therefore the "tail" is the previous/ next cut.

That make both the temporal Denise and the deflicker really unusable because the the tool will look beyond first and last frame: basically looking at "tails" that are completely different shots.

So, there should be a checkbox to tell the temporal tools to limit the action to "visible frames" or "use the tail" (normal behaviours).


Are you using the pre-conform workflow? In that mode, we don’t use the handles. Else if it’s from the same media pool clip, we use the handles.

Re: flicker, tool should not look at "tails"

PostPosted: Sat Apr 21, 2018 12:17 pm
by Johan Fleetwood
waltervolpatto wrote:...That make both the temporal Denise and the deflicker really unusable because the the tool will look beyond first and last frame: basically looking at "tails" that are completely different shots.
Rohit Gupta wrote:Are you using the pre-conform workflow? In that mode, we don’t use the handles. Else if it’s from the same media pool clip, we use the handles.

That doesn't make sense to me.

When there's a cut, either from an edl, scene cut detection or added manually - the method shouldn't matter.

Motion blur, temporal denoise etc are as Walter points out often pretty useless if we can't choose to use handles or not, so please make this an option checkbox.