Mocha Tracking Export Better Out of Render Queue than Media Encoder -- Why?

Forum|Forum|5 years ago
January 15, 2021
1 reply
469 views

Hi there,

I was working on a project last night and I noticed that a precomp that I'd tracked onto some footage using Mocha AE looked good in After Effects, but when I exported it the layer I'd tracked onto the footage seemed to be slipping all over the place. I read somewhere that rendering out of the Render Queue instead of Media Encoder solves this issue. Indeed, when I rendered out of the render queue instead the layer and footage were tracking appropriately together.

Can anyone explain to me why the difference in results? (It didn't seem to be a codec difference as I exported to Pro Res both from the Render Queue and AME and only the one out of AME seemed to have the issue.) Just curious what AME is doing that makes this kind of thing not work, where out of the render queue it does.

-Ryan

Import and export

This topic has been closed for replies.

Mylenium

Legend

Without any exact info about your comp, your footage, your render settings and whatnot we can't really tell you much. Chances are you simply messed up the framerates somewhere, which could happen as easily as picking a wrong output preset in AME that overrides the project's native frame rate. Anything beyond that will require much more info. I would also recommend reading the help, as you seem to be unaware of some of these basics.

Mylenium

R

RyanScammellAuthor

Inspiring

Anyways. Here's some samples if you're able to view:

https://www.dropbox.com/sh/bkhvgy1k5ardpr3/AACSbi9r9H4xBwRIBOcfwD92a?dl=0

The first is via media encoder as Pro Res 422 at 2997. The second is via Render Queue as Pro Res 422. As you can see, there's more wiggle in the one rendered out of media encoder.

To your point, the original source footage was shot on an iphone. I was doing this quick as little birthday present for a friend, so I just dropped the footage to make a new comp which isn't how I normally would do it. That set the comp frame rate to the footage frame rate of 29.973.

In media encoder there's not an option for 29.973, so when set to "match source" it defaults to 29.97. In render queue, it doesn't give me the option of setting an output frame rate. I assume it just draws the frame rate exactly from the comp. So I guess it's possible (and maybe this is what you're saying) that the .003 frame in some way messes with the keyframing on export via media encoder because media encoder can't encode to 29.973, where render queue can? Though, when I look at the properties of the individual files post export both are listed at 29.97 (though it could be that the properties feature within windows can't be more explicit down to the .000 level).

Some of the reason maybe I haven't run into this in the past is that I usual set my comps to a normal frame rate to start. This was something I was just throwing together last night, so maybe it was in creating an unusual frame rate comp that caused that issue further down the line when trying to export via the in some ways less flexible AME.

-Ryan

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