View Single Post
Old 2nd January 2012, 07:07   #104  |  Link
amtm
Guest
 
Posts: n/a
Okay, that's what I assumed it was. Yes, if the original input value is ms and you chose to use frames it converts to the next highest positive or negative frame to get a whole frame value since working in fractions of frames doesn't seem to make sense. But since the original code that calculates the target info only works in ms it gets then converted back to ms which means it's now at whatever matches that rounded frame number since it doesn't know that the original value in ms. I can add code to remember the original ms value so that you don't get the extra rounding.

Last edited by amtm; 2nd January 2012 at 07:14.
  Reply With Quote