Skip to main content
Inspiring
March 26, 2025

After Effects Error: zero denominator converting ration denominators

  • March 26, 2025
  • 3 replies
  • 278 views

I can see that this has popped up often in the past, but specifically in my case, it's related to importing Premiere Pro timelines into AE when there are keyframes on media: 

In the past couple of weeks, I have seen it caused by keyframes in Premiere on:
Time-remapping
Opacity
Transform

I have a hard time reproducing it at will, so there is something about either (1) the number of keyframes. (2) The location in the media of the keyframes. In particular, Time-remapping keyframes near the beginning of end of media might be a trigger. (3) Possibly a MacOS to Windows thing? Editors are on Macs, After Effects artists are on Windows boxes.

In this current job that I am working, any media time-remapped by the Editor will trigger the error, but sometimes it's something else like Opacity keyframing. 

Windows 11 - AE 25.1

3 replies

Zack Einhorn
Community Manager
Community Manager
April 14, 2025

I think you're right about the time reversed out of range keyframes. Can you send me a Premiere project that has time warped footage that casues this error in AE?

Inspiring
April 11, 2025

Hi Zack! (I am responding from my actual account and not the random work account I initially posted with). I have been trying to reproduce this for you, but it's odd. The error goes away when I replace time-warped footage with another clip (nonclient footage replacing client footage). I can't come up with a good way to send you something. Does it have to do with the amount of handles in a reduced/transcoded Premiere project?

I am imagining an editor time-remapping a clip with keyframes far off outside of a "handle" range--like 3 seconds to heads or 5 seconds to the tails. Then, when they transcode/reduce the project with 24 frame handles, the collected project has clips in it where there are keyframes outside of the bounds of the transcoded clips from the reduced project. This is not a problem for Premiere but an issue when imported into AE. Could that be it?

Zack Einhorn
Community Manager
Community Manager
March 26, 2025

Hi @defaulti1o0r0fybisq! Thanks for reporting this issue. When you have steps to reproduce it or a project that reproduces the issue, could you send it here or in a DM to me?