Ask a Question related to Macromedia Director Lingo, Design and Development.
-
BorisS #1
sound(n).currentTime values aren't accurate
There is a bug in Windows version of Director MX (and also in previous
versions):
values reproted by sound(n).currentTime values aren't accurate. They updated
by the steps approx. 250 ms. So on 8 fps sound(n).currentTime values changes
not every frame but every two frames. As a results if there are cuepoints in
the sound file, cuePassed events can be passed at incorrect time. This makes
impossible fine syncronisation of sound and animation. On Mac version of
Director MX such problem isn't exist.
There are a lot of posts about this in this forum. And none of them was
answered by Macromedia Team.
Can somebody from Macromedia Team answer on this?
--
--BorisS
BorisS Guest
-
Getting an accurate Tax percentage
Hi Guys Wonder if you can help with my problem that seemed simple enough at first, but now appears to be a real pain. Basically I have created... -
'set the currenttime of sound' so long ...
On 27 Oct 2003, "nicolas" <n.tasky@preferences.fr> wrote: Yea, not good, eh? There have been methods discussed here that use the queue()... -
using currentTime to trigger events on the stage
Here's a frame script that I've been working on to trigger events on the stage that synch with a quicktime video. This code sort of works but the... -
sound/currentTime
try = member("tolifepic1") etc "moobycalf" <webforumsuser@macromedia.com> wrote in message news:bgu1a6$50k$1@forums.macromedia.com... audio clip. ... -
One field, two values based on status(currenttime)
Originally posted by John M Canino Portland, OR -- Posted via http://dbforums.com
Reply With QuoteSimilar Questions and Discussions
Posting Permissions
- You may not post new threads
- You may post replies
- You may not post attachments
- You may not edit your posts
