Post
by SparkOut » Sun Aug 16, 2009 10:49 am
Audioclips are imported files, and become part of the stack content. They are different to audio files that are referenced by a player object.
RunRev can only play an audioclip of a very limited range of file types (to my certain knowledge the file has to be an uncompressed AIFF file or an uncompressed WAV file. There may be some other file types that can be an audioclip, but I don't know, and I somehow doubt it).
When you start a player object, the audio file is external to RunRev and will by default use Quicktime as the engine to play it (unless you set the dontUseQT to true before letting Quicktime be loaded), in which case you will be able to play files of the types that Quicktime (or Windows MCI) supports (although there are some quirks and issues, particularly with Windows based video playing I think) but only by having them read the audio file from a referenced location - a player object cannot play an audioclip that's embedded in the stack.
In other words, audioclips are only really suitable for beep and zap and bloop noises of short duration because they cannot be played simultaneously, and the file formats mean that they would be very large and make the stack size much bigger. Unfortunately you cannot import a file of mp3 type and play it as an audioclip, so your image above shows a definite non-starter.