Quote:
tHSAD variable. Is that why v1.04 is needed?
|
Yes.
Main change to prev image script is
Code:
SpotLess(RadT=5,ThSAD=5000,chroma=false,tm=false)
As we now added ThSAD=5000 (defaults 10,000) and ThSAD2 defaults to ThSAD, so thresholds for ALL frames=5000, and so frame at 1560-1 is
mostly ignored (from a different scene) and so dont mess up the numbers [previously, frame 1560-1 got threshold of 10,000, and so not ignored and messed up numbers].
Likewise frame at 1560-2 ignored etc.
2nd orange frame at 1561, also ignores 1561-2 and 1561-3 etc.
Setting only ThSAD2 worked fine for double frame spots, but I really shoulda implemented ThSAD arg too as more flexible thresholds.
The above mentioned v1.04 requirement was only for the un-shown frames 1560 and 1561, the images that are shown are from somewhere else.
Dont really think good idea to handle interlaced with MC by separatefields, pixels jump in and out of one field to the other.
EDIT: As it happens, below from v1.03 would actually have worked too, I just did not try it.
Code:
SpotLess(RadT=5,ThSAD2=5000,chroma=false,tm=false) # ThSAD would be as v1.03 default 10000
EDIT:
OOps, talking total bo??ocks, only the chroma=false, tm=false fixes it for either version, ThSAD=5000 made no difference.
EDIT: I'm still tryin' to figure out how this thing works too
EDIT: Actually
Code:
SpotLess(RadT=2,ThSAD=5000,chroma=false,tm=false)
Gets it mostly right, but some weird behaviour @ 4081, RadT=4 seems to work all ok on quick look.