-
Floating point trouble
I have a variable called “workDur”, which is assigned the result of calculating floating point values (from different layer.inPoints/outPoints & prop.keyTime().
The workDur value is then assign to activeComp.workAreaDuration. But it ends up being a slightly higher number.
Any thoughts on why and how to solve?
// ..
alert(workDur); // Result: 1.2
activeComp.workAreaDuration = workDur;
alert(activeComp.workAreaDuration); // Result: 1.20000004768372
/Terje
-
4 Replies
-
I’m not sure why the comp has this slightly longer duration. Maybe due to framerate or something, they can not exactly divide it. But i don’t know why this 40 nanoseconds trouble you 😀
Andrei
-
It renders an extra frame. Quite annoying when the purpose is to create seamless loops.
/Terje
-
Maybe you should differently declare the workDur. figure out the number of frames you wish to have(i named it framesNumber) and try something like
workDur = framesNumber*app.project.activeItem.frameDurationAndrei
-
Assuming a 25 fps comp (CC2014), even hard-coding 122 frames (122*myComp.frameDuration = 4.88 seconds) gives an unexpected result:
app.project.item(1).workAreaStart = 4.88;
alert(app.project.item(1).workAreaStart);
// Result: 4.88000011444092
Reply to this Discussion! Login or Sign Up