Ratio Denominators error

Hi guys (and girls),
I'm having this error where when I try to add a video clip into an AE composition it gives me an error regarding my piece saying, "Overflow converting ratio denominators (17::18). I know there are a few other posts on this error on the thread but none are ore recent then early 2014 so I don't know how viable the answers still are. The file I am trying to add in is an MP4 file 2.5GB file size 1280x720 @ 30fps. If someone could just let me know how to fix it so I can fit the file in the composition without getting that error it would be greatly appreciated.
Thanks.

GreenMcCabe wrote:
As far as my version of AE I am using AE off of Creative Cloud which has been updating it automatically so it would be the latest version of AE for CC.
Yes, so that would be version 12.2.1.5
But that's not the latest version of After Effects. The latest version of After Effects is 13.2.0.49 (Which is After Effects CC 2014.2) CC and CC 2014 are completely different versions of the program and not a simple update. Also, sometimes the Creative Cloud app doesn't update correctly. We've had a lot of people lately who are on version 13.0.1 who thought they were updated. So, go to Help>About in AE and find out what your full version number is.
GreenMcCabe wrote:
As for transcoding the file into a different format would I be able to use Adobe Media Encoder to do that, and if so what format would you recommend using?
Possibly AME could do it. It might also have a similar error.
QuickTime with the Photo-JPEG codec would be a good intermediate codec.

Similar Messages

After Efects Error: overflow converting ratio denominators.(17 :;18)

Hello, I am experiencing a serious problem with after effects.
It started when I right clicked a clip in my premiere pro timeline and chose "replace with after effects composition." Upon moving the clip into my already open after effects project, the wrong still frame opened up in the comp viewer, followed by this error: After Effects Error: overflow converting ratio denominators.(17 :;18). Clicking OK does nothing, and even after closing after effects and restarting the computer, upon opening my project, I simply get this error which will not go away, and as long as it is open, I can do nothing else with after effects. I cannot just create a new project as several other comps are contained within this specific project, and because of this error I now have no access to them. What can I do to correct this?

Hi there
Well, I have this issue for two days so I was like "OMG!", but then I have found this forum and this post which gave me some clues what should I do or what to try...so: my problem was that when I did try to open my huge project (quantum of clips, pics, effects etc.) I got to that error message and when I clicked "OK" project opens TOTALY EMPTY so I couldn't try out any of your solutions (having CAPS LOCK ON didn't help, cos simply there was absolutely nothing inside the project)...so I began scratching my head saying something like: "Hey, wait a sec - what the...?!?!?!". After some messing with empty projects I was able to import my buggy project via IMPOERT>FILE>*.aep, but as soon as I open the composition inside it crashes with exact the same error message (but at least I was able to see what's inside) + some other errors. So I write them all down to a paper and after some time I noticed there are like 2-3 the same errors that occure most of the time...and those was errors with AF own internal effects of AUTO CONTRAST and LINEAR WIPE (+ one more but that one has no significancy and also I was not sure if that third one is internal effect or not: Classic 3D). Then automaticaly my next thought was: "Hm, OK, I should try disabling those effects and see what will happend..." - well, guess what: IT HELPED!!! I went to C:\Program Files\Adobe\Adobe After Effects CS6\Support FilesPlug-ins\Effects\ and there I changed the *.eax extension of those plugins to *.eax- (or any other "unnown" extension :-D). And after some while I narrow it to one definitive internal effect plugin bug of AUTO CONTRAST! So my guess is that the framerate bug (having not whole number as framerate, like some of you suggested here) is probably NOT AFTER EFFECTS INTERNAL BUG AS WHOLE, but reather bug in some of its internal effects dealing with it (the framerate) - hope it will help to resolve this many years long bug (+ sorry: english is not my native language :-D)
Message was edited by: eriqire9 - sorry, I by mistake write the buggy effect name wrong, it was AUTO CONTRAST, not Auto Focus :-)

After Effects error: overflow converting ratio denominators. (17 :: 18)

I have been working on learning how to use Adobe After Effects CS6 and it has been alot of fun, so I have decided to buy it! Except now... I ran in to an issue when I tried to place an effect on a portion of a layer to see if anything would happen; something horrible happened. There is a really annoying pop-up that will not go away! It reads: "After Effects error: overflow converting ratio denominators. (17 :: 18), and it has a red circular icon with a white exclaimation mark in the middle of it. This would be great if it was actually doing anything other than piss me off! It will not go away when I 'dismiss' it by pressing OK, and I fear that I will lose my footage now. I will be buying a different program 100% if I cannot fix this problem or get it explained, so for the sake of Adobe's consumer record, would anybody be kind enough to assist me? Thanks alot, I will be following up on this ASAP.
Much appreciated,
Riley Lloy
Nova Scotia
[email protected]

you will find an answer and workaround here: http://myleniumerrors.com/category/by-number/11-20/

What causes "After Effects error: zero denominator converting ratio denominators. (17 :: 18)" ?

I have the latest update 11.0.2. (Saw same issue with version 11.0.0)
Got the error yesterday from my render computers. Had to render on one machine.
The next day I was able to use the render farm without any issues at all.
But then the next time I rendered, same day, merely changing colors on a layer, I get the error message again.
Same project file each time. Why does it work sometimes but not other times???
How can this be remedied?
I have not seen this error in all my years of using AE. I have not made any changes to my computers except regular Windows updates. Last version we couldn't network at all, now there are errors while trying to network render.

I think I found "my" problem. I don't know if other will solve this issue the same.
It turns out that a certain .AVI file rendered from Cineform Studio will not work in a network render, onl yin the stand alone AE software.
I rendered that .AVI out from AE as a .AVI and now I don't get the error. So apparently, the Cineform format won't work on a network render.
By the way, that might be a really good feature request!

17 :: 19 After Effects Error: zero denominator converting ratio denominators

Hi,
I've been getting this error after I installed AE on a fresh installation of Windows. Google has a collection of complicated explanations.
Mylenium has a nice blog about error messages, but it also has a big explanation.
So I stated thinking: Fresh install... codecs! What am I using?
I disabled all mp4 layers and the error went away.
So if you're getting 17 :: 19, you might want to check for something simple like Advanced Video Codec footage without Quictime, FFDshow or Core installed.

I think I found "my" problem. I don't know if other will solve this issue the same.
It turns out that a certain .AVI file rendered from Cineform Studio will not work in a network render, onl yin the stand alone AE software.
I rendered that .AVI out from AE as a .AVI and now I don't get the error. So apparently, the Cineform format won't work on a network render.
By the way, that might be a really good feature request!

Error 17::18 overflow converting ratio denominators fix

i try doing that thing were u interpret the footage but it puts it down to 9 minutes it is making me very mad. any help would be very apreaiated

Whatever your tool says, it probably isn't recording at the framerate it claims. AE is drawing that info from the embedded streamflags of your H.264 and this is usually pretty correct. Tend to agree with Dave. This probably is the sole source of your issue. You really should consider mangling your clips through an ffmpeg encoder like Handbrake or MPEG streamclip to conform it to something usable and fix those inconsistencies.
Mylenium

AE CS5 Crashing with Zero Denominator & Strange Situation errors

Good afternoon!
In AE CS5 for OSX, we've started observing a strange behavior:
- I have an AE project w/ footage loaded, including a Quicktime movie rendered out of another app (e.g., a 3D app)
- I need a change to the movie, so I re-render it from the 3D app, replacing the existing movie.
- In AE, I get impatient and click Reload Footage while the movie is still being re-rendered.
In past versions of AE, I got an error (unrecognized file type) but AE continued to operate. With CS5, I get a series of errors:
"may be an unsupported format" (expected)
"zero denominator in ratio addition"
"zero denominator comparing ratios"
"zero denominator converting ratio denominators"
"After Effects Error: Strange Situation"
Even after the movie finishes rendering, I keep getting the errors and clicking OK keeps presenting errors. Have to force-quit AE to get on with my day.
Is this a bug? New in CS5? I understand that I'm trying to do something "wrong" by loading a piece of footage that's invalid, but shouldn't I just get a polite "that piece of footage is no good", the ol' test-pattern, and be able to keep working and come back to it when it's ready?
Anyone else run into this?
--Rob

but shouldn't I just get a polite "that piece of footage is no good", the ol' test-pattern, and be able to keep working and come back to it when it's ready?
In theory yes, but as I just explained in another thread, 64bit AE vs. ye olde QT is full of workarounds and limitations due to Apple not seeming to care at all. That and the differences in 64bit file access on a more general level may lead AE to wrong conclusions. I'm sure it's a bug of sorts plus perhaps your 3D app (Cinema 4D?) could also do better by closing and re-opening the file from time to time so at least some parts are accessible instead of keeping it permanently open. For the time being, simply use image sequences...
Mylenium

After Effects error: (17::18)

Every time I try to drag a video to after effects(cs4), I get the following error: After Effects error: overflow converting ratio denominators. ( 17 :: 18 ).
In the beginning I thought that maybe changing the avi files to mpg would solve this problem, because I have two videos that are mpg-s and they work fine, so I downloaded one program, changed the file, but
it didn't work.
Then I searched help from Google and what I found was that I had to right click on the video , then interpret footage and then main. Below the frame rate was two options. 1) Use frame rate from file:(23, 970)
2)Conform to frame rate: 23,97 frames per second.
According to help I found from Google I had to select the option number two. The video worked fine, but...the video became shorter, half of the video was just gone.
So, what should I do? Is there a way to get a video to it's original length, or is there some other way to get off this error so I don't have to use that way, what I found from Google.
P.S. Sorry, if my English is bad
Thank you,
Kristjan

Start here:
http://blogs.adobe.com/toddkopriva/2010/01/getting-started-with-after-eff.html

Error Code ( 17 :: 18 )

I am getting an error code, ( 17 :: 18 ) reading After Effects error: zero denominator converting ratio denominators when I try to load a QuickTime asset into the composition panel. Any ideas as to how to work around it or, better yet, fix it?

Not without lots more info. Exact, down to the decimals, version of After Effects. OS version. Computer specs. What version of QuickTime you have installed. What codec this QuickTime asset is. Etc. FAQ: What information should I provide?
Initial thought: troubleshooting QuickTime errors with After Effects

Copy and paste from premiere

hey guys,
copy and paste into after effects worked like a charm with CS5.5, but now when i copy and paste to CS6 is gives me a After Effects Error 17::18: zero denominator converting ratio denominators
the're m4v files, but that's never been a problem before...
any ideas?

the're m4v files, but that's never been a problem before...
Well, so many things never have been a problem before, but then CS6 came around the corner and reared its ugly head... Not realyl an idea, but you might wanan follow some of the advise I just posted yesterday: http://myleniumblog.com/2012/05/15/make-cs6-work-for-you/ Perhaps one setting or a combination of things will avoid the issues.
Mylenium

No Adobe support response for 1 month!? Anyone there?

I have had an ongoing support ticket going with Adobe about a very problematic error (the overflow converting ratio denominators one! - I've tried the usual workarounds/fixes) that has completely halted one of our projects since moving over to CS4 and I've basically been ignored for the past month about it.
Are there any Adobe support guys on here that might be able to shed some light on the progress of the case?
Cheers,
Jim.

I think I might cry! My master collection came only monday and I cant get it to install! I have done everything I think that needs doing to get it working. I have also contacted customer services 5 times but I don't understand them and they don't understand me! I have left 3 messages on my 'support portal' all consisting of the same problem- jst so I can make my point! I've even threatened I will take further action but nothing- I don't think anyone actually reads them!
I don't know what to do!

Zero denominator loop

Hi, I'm seeing "zero denominator converting ratio denominators. (17 :: 18)" when dealing specifically with looped image sequences. This has started recently with AE CC. If I set the loop to something really high, like 9999 - if I try to add an effect to the footage it throws this error. I've tried it on PNG and TIFF and it seems consistent. Interpret the footage to loop 99 times and the affects are applied just fine. Bug?

Yes, I checked the frame rates - everything is running at exactly 24 fps. Setting loops at 9999 seems to consistently trigger the error, 999 appears ok (Ive tried it with a couple different PNG sequences, between 100 and 500 frames). It's not a big deal, as 9999 is overkill - but I used to always throw 9999 in the loop settings and never experienced this error. But I was banging my head against this for a while so wanted to share my findings in case anyone else runs into this.

Urgent : Executing a batch file in a JSP file

Hi;
I need help in executing a batch file within a jsp page, ive the following codes but it doesnt seem to work...
These are the codes :
<%@ page import="java.util.*,java.io.*,java.net.*" %>
<%@ page import="java.sql.*" %>
<%
Process p = Runtime.getRuntime().exec("Ratio.bat");
p.waitFor();
int i = p.exitValue();
%>
The following is the error :
ype Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
java.io.IOException: CreateProcess: Ratio.bat error=2
java.lang.Win32Process.create(Native Method)
java.lang.Win32Process.<init>(Win32Process.java:63)
java.lang.Runtime.execInternal(Native Method)
java.lang.Runtime.exec(Runtime.java:550)
java.lang.Runtime.exec(Runtime.java:416)
java.lang.Runtime.exec(Runtime.java:358)
java.lang.Runtime.exec(Runtime.java:322)
org.apache.jsp.invRatio_jsp._jspService(invRatio_jsp.java:52)
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
Anyone can tell me why it doesnt work ?... Thanks

Aside from removing the "start" or adding the title ...
Does your batfile really say "SET PATH=%PATH%;%JAVA_HMOE%\bin"? If so, I rather expect you meant to say "JAVA_HOME" and not "JAVA_HMOE".
Also, I'd be cautious about those relative paths that you're passing in to the Java program. Of course I don't know what you're doing with those in the program, but if you try to just pass those paths to a File or InputStream constructor, they're going to be relative to the current directory. And if you execute a batfile using cmd from an exec that's within a JSP ... I'm not sure what your current directory would be when the bat runs. Maybe you've checked this out and it's the right place, but if not, perhaps you have a misconception there.

Z68A-GD80(G3) Beta BIOS Versions For Ivy CPU's

E7672IMS.J10 ==> E7672IMS.J21
01.Fix vdroop offset control function can't work normally issue and
modify code to avoid chip bug issue.
   02.Add Gigadevice 25Q64BSIG" SPI ROM support.
   03.Fix Adjusted DRAM Frequency and XMP info incorrect issue when use
XMP 3000 memory and if XMP 3000 profile is enabled then force run 2800.
04.Fix Adjusted DRAM Frequency incorrect issue when XMP is enabled and
set different DRAM frequency.
05.Fix DRAM frequency incorrect issue when use Patriot PV316G213C1K memory
and XMP is enabled.
   06.Fix system hang on 0x55 issue when use Team Team-Elite-1866 memory.
07.Fix system hang on 0x55 issue when use SPD 800MHz memory and
Sandy Bridge CPU.
   08.improve memory performance.
   09.Add M-Flash support ME FW update solution.
   10.Modify ME shouldn¡¦t be updated if the USB is removed before reboot to BIOS.
   11.support amp function.
   12.Finetune G.Skill memory command rate timing.
   13.Fix some memory cause bios hang 0x3b or 0x4f when overclock cpu ratio to 42.
   14.Fix the issue that setting item "Command Rate" to 1t causes
an unnecessary cold reset when bios was postting.
   15.Fix some PCIE card can¡¯t detect issue.
   16.Fixed MSI keyboard ES300MU can't detect.
   17.Set SMLink1 Thermal Reporting Select default to ture.
   18.Fix use usb card reader error issue when update usb 022 module.
19.Fix OC Genie setting not set to item after OC Genie function enable.
   20.Fix item "Internel PLL Overvoltage" always Enable when over clock cpu ratio.
21.Set item "Intel C-State" to enabled when use some special cpus (such as i5¨C3475s
     which oc ability are limited) to over clock cpu ratio to the ratio higher than
     the ratio 4 cores can reach at the same time.
22.Fix item "Adjust CPU Ratio" show error when adjust cpu ratio.
   23.Fixed PLL function enable caused set tRTL timing hang issue.
   24.Add OC Retry Counter Item.
   25.Fix system hang on 0x55 issue when use single side dual rank memory.
Please note that flashing this release occurs entirely at your own risk!
For BIOS Update >>Use the MSI HQ Forum USB flasher<< => Mode 1: Point to archive file!
*NOTE: Make sure you unplug your PSU from A/C power and properly >>Clear CMOS Guide<< after flashing.

E7672IMS.J22====>E7672IMS.J20 OFFICIAL
- Enhanced PCI-E display card performance.
- Improved memory compatibility.
This is the full release bios for this board with additional archive for flashing the ME extension.
>>Use the MSI HQ Forum USB flasher<<
Download the compressed archive to your desktop but do not decompress.
Select option 1 of the forum flash tool and point the tool an the compressed archive then follow the direction. This will flash your bios and ME extension.
Once complete you will need to download and re-install the latest version of the Intel Management Engine Drivers.
<<Intel Downloads / Management Engine>>
Please note that flashing this release occurs entirely at your own risk!

Is there a practical size limit on JPEG format image files?

I have noticed when working with Photoshop v7.0 on Windows XP that, when creating a JPEG format image file from a very large scanned image (more than 800 Mb, maybe), the .jpg file will usually be saved on disk at any of the possible compression ratios available, without any reported error, yet when the saved file is re-opened, an error is reported - something along the lines of "missing or corrupted end of file marker" - and the image cannot be loaded.
If before saving the original image is substantially reduced in size, e.g. by reducing the resolution of the image, a viable JPEG format file can be created, which will subsequently load successfully, though technically with data loss.
This appears to happen only with JPEG format files - PDF format files can be saved from the original image at similar JPEG compression ratios, without error on reloading.
I do not know if this also occurs with any other Photoshop versions. I am working with Adobe Photoshop v7.0 on Windows XP, although we are preparing to upgrade to CS (which version I don't know) in the near future, for different reasons to those which are detailed above.
Does anyone know if there is a technical explanation for this behaviour? Is there a file size limit for writing viable JPEG files (which Photoshop does not report as an error when exceeded)?
Thanks

Chris Cox wrote:
Where did you get the idea that we weren't doing something about it?
that's what I gathered from "JPEG cannot [...] in Photoshop (code difficult to replace)".
But if you say this is in the works right now, that's good news indeed.
Chris Cox wrote:
And where did you get the idea that posts get deleted? (other than SPAM)
Are you sure you're reading the same forum as the rest of us?
That's what happened:
The content you posted below was reported for abuse and removed by our
moderators:
Subject: Re: Is there a practical size limit on JPEG format image files?
Posted: 4/29/11 9:11 AM
Anyway, you gave an honest answer on this technical issue, Chris, and that's what counts.

Ratio Denominators error

Similar Messages

Maybe you are looking for