couple of buyers had same error on my last two projects in CS6. What’s the same in the projects is that they both have null object with custom controls (position, rotation, scale for element 3D object).
This is the error:
After Effect error:zoro denominator in ratio addition (17::16) After Effects error :Shadow/HighLight (4358) (25::16)
They have up to date AE CS6 but they cannot solve the problem…
Any ideas? Did anyone had similar problems. One guy gave me 1 star for this not working, and he didn’t even contact me. And I cannot even help them, it’s some kind of bug inside AE.
I’ve had this problem in the past with a freelance job I did not long ago. I turned of Multi-Processing and Disabled Layer Caching under “Secret” in the Preferences window. I also turned off the Cache Indicators in the timeline.
To Disable Layer Caching
Hold on to the SHIFT key and go to Preferences -> click on “General” and you will find a new option called “Secret” at the bottom. Now check the “Disable Layer Cache” checkbox.
To Disable Show Cache Indicators
In the timeline of your composition click the drop-down menu in the right-top corner of the timeline window. Now uncheck “Show Cache Indicators”.
When I did all of the above, I never received the error again.
Can’t remember having seen this one, but the zero denominator ratio rings a bell. It’s a divide by zero error, essentially.
Are you using any layer space transform expressions, like toWorld() ? I think if you try some of those transforms on layers that have a scale of 0, you get those kind of problems.
I control element’s 3d scale, rotation, position, groups from it, on 2 null layers… I went inside of buyers computer now via teamviewer, it wont open the project at all. I tried importing it, but then I cannot open the comp. Various errors… p.s. @motionvids, didn’t work.
It could be an issue related to the file format of your footage, I remember having similar issue with a .mov video. Converting to footage to a JPEG sequence solved The problem forma me. Hope it can solve yours too!
Layer source is null? How does that work? I couldn’t make a null layer source if I tried. If you delete the source in Ae the layer disappears, if you delete it in the OS, it gets replaced with a placeholder. I wonder if the customer’s Element 3D plug-in is at fault here.
I think you should get the customer to email you the file and see if you can open it and have a play on your computer. It could be a 3D Element bug. You should also try and submit it to Adobe.
Can’t remember having seen this one, but the zero denominator ratio rings a bell. It’s a divide by zero error, essentially.
Are you using any layer space transform expressions, like toWorld() ? I think if you try some of those transforms on layers that have a scale of 0, you get those kind of problems.
Yes, there is toWorld expression (coming from element)…
Can’t remember having seen this one, but the zero denominator ratio rings a bell. It’s a divide by zero error, essentially.
Are you using any layer space transform expressions, like toWorld() ? I think if you try some of those transforms on layers that have a scale of 0, you get those kind of problems.
Yes, there is toWorld expression (coming from element)…
Might be worth double checking that the layer that the toWorld refers to never gets to a scale of 0. I used to have this problem, but I can’t remember the exact nature of it…whether it gave an expression error or an After Effects error, whether it was toWorld or toWorldVec, but it somehow seems very familiar, even though I think the problem no longer exists in CC.
I certainly have a few templates out there that use something along the lines of…
//quick'n'dirty fix on the scale prop in question
x = value[0] == 0 ? 0.00001 : value[0];
y = value[1] == 0 ? 0.00001 : value[1];
z = value[2] == 0 ? 0.00001 : value[2];
[x,y,z];
found a problem. I tried deleting color presets and it worked, I opened the template at this guys computer it works. I will copy paste the expression in next post.
so I had 20 adjustment layers with different effects used like color preset and one main null layer with slider control. here’s the expression on each adjustment layer opacity:
n = thisComp.layer(“Color Preset”).effect(“ChoosePreset”)(“Slider”);
o=transform.opacity;
if (n==1) {
o=100
} else if (n==2) {
o=0
} else if (n==3) {
o=0
} else if (n==4) {
o=0
} else if (n==5) {
o=0
} else if (n==6) {
o=0
} else if (n==7) {
o=0
} else if (n==8) {
o=0
} else if (n==9) {
o=0
} else if (n==10) {
o=0
} else if (n==11) {
o=0
} else if (n==12) {
o=0
} else if (n==13) {
o=0
} else if (n==14) {
o=0
} else if (n==15) {
o=0
} else if (n==16) {
o=0
} else if (n==17) {
o=0
} else if (n==18) {
o=0
} else if (n==19) {
o=0
} else if (n==20) {
o=0
} else {
0
}
but maybe it’s not about expression… maybe it’s because of some effects on adjustment layers, and as the error title says, I do have shadow/highlight on some layers. Maybe it’s some kind of compatibility issues on CS5.5 VS CS6
As far as I could see, problems happened only to CS6 users.
so I had 20 adjustment layers with different effects used like color preset and one main null layer with slider control. here’s the expression on each adjustment layer opacity:
n = thisComp.layer(“Color Preset”).effect(“ChoosePreset”)(“Slider”);
o=transform.opacity;
if (n==1) {
o=100
} else if (n==2) {
o=0
} else if (n==3) {
o=0
} else if (n==4) {
o=0
} else if (n==5) {
o=0
} else if (n==6) {
o=0
} else if (n==7) {
o=0
} else if (n==8) {
o=0
} else if (n==9) {
o=0
} else if (n==10) {
o=0
} else if (n==11) {
o=0
} else if (n==12) {
o=0
} else if (n==13) {
o=0
} else if (n==14) {
o=0
} else if (n==15) {
o=0
} else if (n==16) {
o=0
} else if (n==17) {
o=0
} else if (n==18) {
o=0
} else if (n==19) {
o=0
} else if (n==20) {
o=0
} else {
0
}
n = thisComp.layer("Color Preset").effect("ChoosePreset")("Slider").value;
myLyrID = 1; //change here
if(n == myLyrID) 100; else 0;
haha, of course there is a shorter way felt, but you must understand I’m a n00b, and when I do expressions I do it the harder way
Would you be interested in an expressions starter tutorial? Couple of basic principles and stuff? I’ve been thinking about it for a while how to approach a subject like that.
Bear in mind, it’s always good to find a shorter way to write an expression because it will execute much quicker. Your expression could take up to 20 times longer to execute than it needs to. 20 “if’s” to test instead of 1.
