I'm trying to get the X-axis Only feature of the autotracker to work to track an edge. However, the detected points still seem to wander off the x-axis when the feature is enabled, even going outside the search area sometimes (see attached screenshot).
I'm using tracker version 6.2 on Mac OS 12.7.5. I checked that the Java version is the bundled one.
Any ideas what might be going wrong or how to resolve this?
A small update. I dug a bit into the OSP/Tracker source code on GitHub to see if I could find a cause for the behavior.
My current hypothesis is that it could have to do with the sub-pixel refinement step in the template matcher (media/core/TemplateMatcher.java). This optimization step seems to assume that the correlation peak is two-dimensional, while this is not the case for an edge (the direction parallel to the edge won't have a well defined (sub-pixel) peak location).
If this suspicion is correct (and this is indeed unintended behavior) a fix might be to make getMatchLocation() aware of the line (x-axis) along which the search is performed and project the (dx,dy) correction on this line.
To fix this, you can try checking the axis settings again, narrowing the search area to limit discrepancies, or saving and restarting the project to ensure the correct settings are applied. If the problem persists, there is a high possibility that this is a bug with this version. You may need to report it or try another version to see if the feature works more stably. Regard,
