I have always experienced errors in time calculations with the 3.6 versions. If an event is dragged and dropped into the RDAirPlay log machine, times are not recalculated correctly unless I move an event, or the automation advances to the next event. We drag and drop a lot during a typical day. Right now, I am working in RDLogEdit on tomorrow’s log, and when highlighting a 4 hour interval, it shows total time as 5:05:03. If I add the segment lengths as displayed in the log, they total 4:05:59, not 5:05:03.
BTW you can add time on any calculator.
--For 1:30 + 2:43 + :55
--Enter 1030 + 2043 + 55 the colon is essentially represented by a 0
--Result 3128
--Now add 940 this moves one minute of seconds to the minute column and keeps seconds in base 60; result 4068; keep adding 940 until the seconds are less than 60 and restoring the 0 between minutes and seconds.
--Result 5008 or 5:08
I have always experienced errors in time calculations with the 3.6 versions. If an event is dragged and dropped into the RDAirPlay log machine, times are not recalculated correctly unless I move an event, or the automation advances to the next event. We drag and drop a lot during a typical day. Right now, I am working in RDLogEdit on tomorrow’s log, and when highlighting a 4 hour interval, it shows total time as 5:05:03. If I add the segment lengths as displayed in the log, they total 4:05:59, not 5:05:03.
BTW you can add time on any calculator. --For 1:30 + 2:43 + :55 --Enter 1030 + 2043 + 55 the colon is essentially represented by a 0 --Result 3128 --Now add 940 this moves one minute of seconds to the minute column and keeps seconds in base 60; result 4068; keep adding 940 until the seconds are less than 60 and restoring the 0 between minutes and seconds. --Result 5008 or 5:08
--Chuck W.