Recently, Hugh Senior wrote:
> Playing sound or movies in QT from a CDROM can cause playback 'stuttering',
> as if the system has to wait for the CDROM to catch up.
Playing any multimedia from a CD can be problematic (burn speed has nothing
to do with it since this simply refers to the rate at which your writer can
add data to the CD). Keep in mind that if any portion of your stack/s has
to hit the CD for data while media is playing, the head needs to jump back
and forth between the media and your stack, potentially causing stutter.
This may not be what is happening in your case but it is a good possibility.
As far as I can tell, there is no reliable way around a disc access problem.
Theoretically, if the entire contents of your stack can be read into memory,
then playback should be stutter free since the disc player only needs access
media from the disc. Fortunately, (my understanding is) Metacard's
architecture inherently loads entire stacks into memory so any disc hits for
stack data should be minimal (Scott Raney, correct me if I'm wrong).
I ran into a problem similar to the above with a mixed mode disc (Red Book
audio and data). I built an MC stack that was supposed to show a looping
slideshow while acting as a player for the audio. Problem was, the
slideshow was a multi-megabyte QuickTime movie stored on disc, and the CD
player couldn't play audio and read QT data fast enough to prevent the audio
from stuttering (or stopping completely). The solution was to dumb down the
slideshow (no transitions) and place the slide images into the MC stack, so
that all the data in the presentation would load into RAM, thus freeing the
CD player to read the audio portion of the disc only.
Hope this is somewhat useful.
Regards,
Scott
__________________________________________________________________
Scott Rossi Tactile Media - Multimedia & Design
Creative Director Email: [EMAIL PROTECTED]
Web: www.tactilemedia.com
Archives: http://www.mail-archive.com/[email protected]/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
