At 10:52 -0200 01/31/2002, Marcos Trinca wrote:
>I think if I tell you my specific problems, like that one I said above,
>I'll need to write lots of lines, so, so far, I would like to receive
>some information like where can I find articles or books that talking
>about this themes (Memory management and Machine Process with Director).
>
>Any Tips and tricks are welcome too.
Dunno about books specific to this topic, but it's worth a surf at
maricopa.edu, director-online.com and macromedia.com's own tech notes
to see if there are suggestions.
One thing I can definitely tell you about Flash is it's not a hot
plan to have more than one Flash sprite on the screen at a time; they
tend to clash. You can get into trouble with sound and video that way
too.
On Win, at least, there are (potentially) different drivers for the
different media types that are all trying to get to the sound card at
one time if you have video, sound separate and flash going all at
once. This can cause conflicts.
Also my experience has been that if you are playing video in a MIAW,
and close that MIAW *while the video is playing* on Windows, you will
get an IML32.DLL crash. Pausing the video before closing the window
fixes it. I would not be shocked to learn that Flash and plain old
sound files can misbehave in the same way.
Also self-forgetting MIAWs will probably end up causing you grief as well.
Rules of thumb? Let's see:
1. Never have more than one silicon-sucking media type going at a
time. This means video *or* Flash *or* some stand-alone sound file.
Certainly not any of those in combination simultaneously!
2. Never try to do much of *anything* else while either video or
Flash is playing back. This means no sprite animations, transitions,
etc., and certainly don't try to have two or more video or Flash
sprites onscreen at once (this means across MIAWs too; that is, one
Flash sprite in one MIAW + another Flash sprite in another MIAW =
trouble).
3. Always make sure your media processes are stopped (pausing the
process is enough) before you close out that part of your
application, whether you're moving to a different part of the score,
to another movie, or closing one MIAW to open another.
4. Remember that when you set up a MIAW, you've technically opened
the file even if it is not showing up onscreen. So initting your main
movie in such a way that it "preloads" all of its MIAWs at one time
will suck up absolutely frightening amounts of memory. This also
means you will have to set up any media used in those MIAWs in such a
way that it will not begin playing the second the file is opened, but
rather when you direct (!) it to do so.
Hope some of this helped!
--
Warren Ockrassa | http://www.nightwares.com/
Director help | Free files | Sample chapters | Freelance | Consulting
Author | Director 8.5 Shockwave Studio: A Beginner's Guide
Published by Osborne/McGraw-Hill
http://www.osborne.com/indexes/beginners_guides.shtml
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/lingo-l.cgi To post messages to the list, email
[EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for
learning and helping with programming Lingo. Thanks!]
