Perhaps, because it's a new and very fast machine, so that the check about the 250 msecs is done, before the mov is completely loaded? Tiemo
-----Ursprüngliche Nachricht----- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Dave Cragg Gesendet: Donnerstag, 7. Juni 2007 10:02 An: How to use Revolution Betreff: Re: Curious QT playback problem On 7 Jun 2007, at 03:59, J. Landman Gay wrote: > the script gets the currentTime, checks every 250 milliseconds, and > when the currentTime remains unchanged, assumes the playback is > done. Then it moves on to the next file. From what you describe, it sounds like either the currentTime isn't reported correctly, or there is some kind of delay at the start of play so the currenttime doesn't change (stuck at 0) in the first 250 milliseconds. Do you reset the timer at the start of each clip? I could imagine some over-enthuiastic virus-checker causing a delay as you switch files in the Player, and possibly when QuickTime tries to start playing the file. Or a very full hard drive. Off the top of my head, set the currentTime to 0 for each clip, then check that the currentTime hasn't changed AND that it is not 0. (Using the playStopped message would be easier. :-)) Dave _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution