SOLVED: Composite and Crop unexpected behavior

Not totally certain this is a bug but in the below TOX you can see that the same Crop → Composite signal path behaves differently given two different source images.

The problematic image locked in the TOX was saved from a TOP path in TD that also exhibits the issue.

Is there something I don’t understand about TOPs going on here? Or, more simply, something about the Composite or Crop TOP?

Win 10, TD 33910

Hi @hardworkparty,

that stumped me for a bit until I removed the hsvadjust and changed the composite to difference.
Seems like the locked source image already has the offset in it?

cheers
Markus

Hi Markus-

UGH yes it does … OK this problem is more complicated that I originally thought.

Thanks for looking, sorry to waste your time!

no problem - glad I can help :slight_smile: