Inspiring

Answered

After Effects Error: zero denominator in ratio multiply. ( 17 :: 17 ) | How to Fix?

Forum|Forum|11 years ago
March 3, 2015
7 replies
87410 views

I changed the fps rate in the Preview panel.

From 29.97fps to 59.94fps.

And I did a preview.

When I went back to 29.97, and did preview, appears this error, when i try make RAM Preview.

It seems that fps with number integer works normal, because I've put in 30 fps, 25, 24, 15, and all work normal, the problem appears only when put in 29.97fps or 59.94fps.

Error or problem

This topic has been closed for replies.

Correct answer christopho57143731

It happens when your using Jpeg sequences.

Right click footage -> INterpret Footage and turn on the preserve RGB

now everything should work

darionLeigh333

Participating Frequently

I solved this issue, although it is not ideal it allowed me to continue working.

So here is your emergency solution if you have to get a project out the door.

1) Go to the bottom of the Project window and change the settings of the project to 8 bpc.

You can change back if you need to before rendering.

2) If that fails go to File > Project Settings > Video Rendering and Effects - Set to Software only (no GPU)

Hope this helps.

sandys81900829

Participant

Tried everything in this thread and still got the error whenever I tried to play/preview my project. I even tried "trial-and-deleting" footage/project media groups at a time to see if it was something in my media (like a broken jpeg sequence as suggested) but I would get all the way down to the last item in my project (the comp) and it would still give me the error.

I finally realized that I had set one of the comps to Cinema 4D instead of classic. Found other pre-comps that were the same. So I set all comps to Classic 3D and the problem disappeared. Worth a try if you're still having this issue!

M

M Umar Riaz

Participant

Appeared Exactly the Same Error, and in mine case it always occurs when we are UPDATING a File (with another application) while we are USING it in Composition. While the Update is Not finished (like Audacity takes times Writing Big MP3 file), and in the Mean time we Switch to After Effect.

K

keshavr55555

Participant

I am working on 25 fps still its showing aftereffects error: zero denominator in ratio multiply (17::17) and i have done that preserve RGB also as its an JPEG sequence. What should I do now? Please suggest..

Thanku

C

christopho57143731Correct answer

Participant

It happens when your using Jpeg sequences.

Right click footage -> INterpret Footage and turn on the preserve RGB

now everything should work

F

Fred van Os

Participating Frequently

Thank you. Will give it a try ....

F

Fred van Os

Participating Frequently

I will give that a try.

chesterb72279385

Participant

I have the same issue.

I want to import a jpeg sequence from a timelapse for stabilisation. I interpret the footage at 24fps and create a new composition to work with.

The issue is that clip is the right size (1:08) but the images in sequence stop at about 4/5 the way through (0:54) and the rest is just black. The clip is not compressed the images from this point on do not register so its missing the last 12 seconds.

The funny thing is this is the exact time that the entire clip would be if it was 30fps. The images in the green bar above are just black and dont render or export. If i try export the clip it just fails at this point also.

If I import and render at 30fps this dosnt happen, only when it is set to 24fps.

Working in AAE 14.0.1.5

Running Windows with 32gb Ram Intel i7 6 core and GTX1080

I have rebooted, reinstalled (multiple times) and reset preferences.

Any help would be massive!!

F

Fred van Os

Participating Frequently

I have this error as wel. When combining a black/white matte through using "Luma Matte" for creating an alpha channel in the composition. In after Effects 2015 this works in the 2017 version, I get After Effects Error: zero denominator in ratio multiply. ( 17 :: 17 ). Reinstalling, Rebooting, nothing works. The 2015 version is on another system, I run the 2017 version now, and this project would not open in 2015 version.