Using Vegas Pro 17 and tracking some 1920x1080 59.9 fps footage and have a pretty solid track.
I decided that 60fps was higher than I needed and because the VP pipeline is cpu heavy it also slows things down unnecessarily so I converted the clip to 30fps.
Because Mocha doesn’t interpolate tracking data when used with VP, I had to re-track. No big deal, I knew that was coming.
But a few seconds into tracking the world center, the center point and search area jumps to a completely different location from one frame to the next. The track is flawless every time with the original footage and jumps with the converted footage. [see below for an exception]
While Mocha can be sensitive if I don’t include enough variation in detail with the 59 footage, it’s much more sensitive with the 30. I can include the fire hydrant or it and grass and at some point the search area will just jump somewhere else. Sometimes I’ll get a “tracking lost” message but usually just a discontinuous jump.
I’ve upload a sample project with working and non-working tracks if you want to try it on your end.
While I was writing this, I was giving AE a trial and tracking the original 59.9 fps footage and that track failed once. I haven’t been able to repeat that failure yet.