Applying track data from mocha to null object has bad timing

Question

I can work for some time before mocha behaves weirdly, when I apply tracking data as transforms to a null object, the frames are spread far far appart. It's already a pain to navigate through the countless crashes of after effects, the many popups that tells me keylight needs another 120 giga byte of ram to run for 1 frame,... but now that some of the plugins don't even behave the intended way, I start to get really demoralized. Any help is welcome, my project is due in 5 days, and I don't have the time to track everything by hand.

Beat23122173n5jj · Accepted Answer

for anyone who goes through this, it appears it's with the RED .R3D files that could be sliced when recording. Precomposing the part you want to track does the trick

Rick Gerard · Answer

If you want help, we need you to provide project workflow details and a few screenshots of the entire UI with the modified properties of the problem layers showing. Select the problem layer, press 'uu', and take a screenshot. Then drag the screenshot to the reply field on the forum instead of using the Drag & drop here button so you can see it in your post, size it up, and then move on to the other problem layers.

Trying to diagnose a problem when all we know about the project is that the tracking data is nearly impossible. The only guess I have is that the Comp and any nested comps have frame rates that don't match.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded