-
HELP! I think this expression is crashing CS4
I’ve had a major problem with a big project of ours since we moved over to CS4 from AE7. I am getting the ‘overflow converting ratio denominators 17::18’ error message constantly when scrubbing timeline, changing bit depth, actually pretty much anything in a certain part of the project. In AE7 I got the error every so often, but in CS4 when it comes up it just doesn’t go away! I have to force quit AE. It’s not the usual thing of footage being wrong frame rate for comp it’s in, etc – I’ve tried all that…
So, anyway – I think I found the culprit and stripped the project down to a couple of comps that are basically just text layers with counter expressions applied and precomped up a bit.
The following code is applied to ‘source text’ on text layers (the ‘initial’ field is the only difference on the diff text layers): –
——————-
(See code in Expressions code box)
——————-Can anyone see anything in this code (Dan Ebberts maybe?) that doesn’t look right or that could be changed to do exactly the same job?
I’ve been hounding Adobe for months now and they are being less than useless.
If anyone could help I would be eternally grateful!
Cheers, Jim.
CODE—>>>>
initial = 89//minutes
mins = Math.floor(time/60)//seconds
secs = Math.floor(time - (mins * 60))
secsCount = timeif ((mins < 180) & (secsCount < 2000000)) {
if (secs < 10){
secsT = "0" + secs
} else {
secsT = secs
}text.sourceText = (initial + mins) + ":" + secsT
} else {
text.sourceText = "22:00"
}Production Premium CS4 – Mocha v1.5 – FCP 5.1.4
MacPro Quad 3GHz / ATI 1900XT / 8GB RAM / OSX 10.4.11
30″ ACD / Decklink SP / SONY PVM-20M4E/ Wacom Intuos 3 A4 / XServe / United Digital RAID
———————————
Production Premium CS2 – Combustion 3 – Mocha v1.0.1
Win XP Pro 32 / Dell Precision T3400 Q6600 / 4GB RAM / NVidia Quadro570 / DeckLink Pro / Roland DS-5s / Sony BVM-20G1E / 2 x Dell 2007FP / Wacom Intuos 3 A4 -
2 Replies
-
I don’t see anything in your expression that cause AE to crash, and it seems to work fine in my version of CS4. Wouldn’t this do the same thing though?
initial = 89;
secs = Math.floor(time%60);
mins = Math.floor(time/60)
“” + (initial + mins) + “:” + (secs < 10? "0" : "") + secs Dan -
The only thing is you are using the bitwise AND operator ‘&’ instead of logical AND operator ‘&&’, but in effect it should be the same given the way you use it.
Xinlai Ni
Software Engineer, Google Inc.
Reply to this Discussion! Login or Sign Up