Skip to main content
C
chrisr58449048
Participant
October 29, 2019
Question

Boris AE CC y position moving faster than planar surface

  • October 29, 2019
  • 1 reply
  • 511 views

Upon tracking an object and importing track data in to AE, the 5 dots that indicate the planar surface move perfectly and align exactly the part I am tracking.

 

See the attached video. Note the planar surface on the left and the null object and when scrubbing, the null moves far faster, while the planar surface sticks to the escalator step.

 

 

This is more than just drift. The output keyframes aren't matching the actual tracking data.

 

I checked my frame rates and all are matched.

 

I'm lost.

    This topic has been closed for replies.

    1 reply

    M
    Community Expert
    MukaidaCommunity Expert
    Community Expert
    October 30, 2019

    Is the footage variable frame rate (VFR) or constant frame rate (CFR)?
    After Effects supports variable frame rates from CC2018, but Mocha doesn't support it.
    https://helpx.adobe.com/after-effects/using/whats-new-oct-2017.html

     

    If the discrepancy is caused by VFR, you can fix it by converting to CFR using HandBrake and then importing into After Effects.

     

    Alternatively, switch the setting to Smooth Video Motion and try it out.

     

    • Select footage in the Project panel.
    • Select File > Interpret Footage > Main.
    • Click More Options.
    • In the dialog, set Variable Frame Rate Mode to Preserve Audio Sync (default) or Smooth Video Motion.
    C
    chrisr58449048Author
    Participant
    October 30, 2019

    Thank you for your response.

     

    The footage is not variable frame rate. It started at 30fps and I wanted to slow it so I interpreted footage and changed it to 23.976. I also double checked my project settings in Mocha to ensure the FPS matched.

     

    I accomplished my task by using AE's built in motion tracker, which did a fine job in this case, but it should have been a cinch with Mocha.

     

    Still stumped.

    R
    Community Expert
    Rick GerardCommunity Expert
    Community Expert
    October 30, 2019

    If there is a timing problem when you forced a frame rate in file interpretation that might be something new. I'll have to check that out. 

     

    90% of my FX plates are shot at 59.97 or 120 FPS so I can easily adjust the timing and don't have to worry about motion blur as much. The metadata for footage is always 29.97 or 23.976 so if I want real-time playback I have to force the footage to the same frame rate that was used when it was shot. I've never had a Mocha tracking or timing problem doing that with the latest builds of Mocha. Back when Mocha opened up the clip instead of the layer, the frame rate had to match the comp frame rate and it was a lot more complicated to use that kind of workflow.

     

    Another option might be to just pre-compose the footage that is giving you problems and then run Mocha on the nested comp. This will guarantee a frame rate match and any corner pin or tracing data you get should match up perfectly no matter what the frame rate of the source footage is. That might be worth a try. You could not do that in previous versions. I run Mocha AE and Mocha Pro on pre-comps all the time. It works very well.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices