TThis has been an issue for a long time in ExtendScript. The only work around, as heavy and annoying as it is, has been using a function I built that basically tests compObj.time value against the supposed frame value. The time attribute seams to work properly and lands on the whole frame. Corrects and incorrect float value basically. I then compare the values, if they don't match, I assume the compObj.time is the correct one and use that value instead. It becomes greatly annoying as setting this value forces the timeline cursor to move to that time, so I also saved the previous location so I could return it back as if nothing happened. It's an incredibly inconvenient process, but it does seem to work.
↧