That means one of the dropped frames could actually be a non-duplicate and blending it will produce ghosting.
But it also will reduce jerkyness a bit, if tdecimate is unsure about which frame to choose.
Also, you want the blending only when there are triples? Or blending for all dups?
No.
I had this idea: blend all most different duplicates of one row.
examples of duplicate chains (non-real-world):
n1,n2,n3 -> slight different near/new duplicates
d -> bit identical, or better said: almost identical duplicate of the preceding frame
this x d n1 will blended to: x+n1 OR d+n1
this x d n1 d1 will blended to: x+n1 OR x+d1 OR d+n1 OR d+d1
this x d n1 n2 n3 will blended to: x+n1+n2+n3 OR d+n1+n2+n3
Most duplicates after R24-processing are bit-identical. So a near-duplicate(s) should be detectable...
Of course, this assumtion does not fit for other sources,
as well as for the ST-Yoyager sample I sent to you because I compressed that one, so the duplicates arent identical anymore.
I hope I didn't cause too much confusion.
__________________
Don't forget the 'c'!
Don't PM me for technical support, please.
|