This content has been marked as final. Show 2 replies
Take a look at the sound object. Go to the LiveDocs, then click on:
Director Scripting Reference
Director Core Objects
You will see methods such as queue() and play(). Quote: "Once a sound has been queued, it can be played immediately with the play() method. This is because Director preloads a certain amount of each sound that is queued, preventing any delay between the play() method and the start of playback."
Thank you very much for the response. By the way, I'm not a Director user yet. I'm exploring the application's features to see if it is the program I need to do what I want to do.
This is good news about the queue function. I'd like to ask a more in depth question for you to consider if you have the time. Let's say I have a collection of 100 sound files (of various sizes) and when any given one is playing there is the possibility of one of two other ones to play seamlessly, immediately after it: call them "Option A" and "Option B" (both of which would be different for every sound file). Option A would play if the user did nothing during the course of the sound file playing, and Option B would play if the user clicked something during the playing of the sound file.
Could director handle that many sound files - given that at any point in time only two would have to be queued?
Also, I understand from your response that the queued file will be preloaded and play immediately, but is the point at which the current sound file ends and the queued one begins a sample-accurate transition? Anything less than that could be heard as a glitch.
Thanks very much for your help. I'm an audio editor and I'm swimming in unfamiliar waters.