This may be a Nuke/OFX bug as well.
A new instance of Mocha Pro OFX replacing a previously used Mocha node remembers the input duration of the previous clip even if that is no longer valid.
- Launch Nuke, import mov clip, add retime node to force start frame of mov to 1001, set globals appropriately.
- Launch Mocha, do some tracking, save the project export the tracker, do work.
- Save Nuke project as a new project, different name. Delete old source mov and replace with a new different duration clip. set globals appropiately.
- Delete old Mocha node add new one and launch.
Result: Mocha sees and indicates the duration of the previous clip.
Nuke 12.0v5, Mac OS Sierra, MacPro 2013 64Gb Ram 2 x D700 8 Core Xeon E5.
Addendum: Just confirmed this does not happen after relaunch but I would have expected Mocha to parse the input stream and determine min/max frange at least each “new” instance if not each launch.