>Since it seems that QT releases the memory once the video starts >playing again, maybe the memory could be freed up by doing > >sprite(x).movieRate=0 >sprite(x).movieRate=1 >go frame x > >Would this work, or would it actually have to play a frame to free >up the memory?
You can do all of that, and come back to the frame where the movie exists, and still the memory hasn't been freed. Playing the movie again will then free the memory. Carol, you probably shouldn't be worrying about it, unless you've seen a case where there was a problem. The way QuickTime works allows it to play video smoothly off devices that are only a small amount faster than the data rate of the movie. With QuickTime 1.0 you would typically have to make your movies at 90KB/S in order to be sure that it would play off a 150KB/S CD-ROM drive. With QuickTime 2.0, and later, QuickTime pre-streams the video, so that it's in memory ready to be played. The transfer off the CD happens as quickly as the drive can deliver it, which would let you get much closer to the theoretical limit of 150KB/S (this is for a single speed Cd-ROM drive). A side effect of how it does it is that frames are in memory before you need them, and also may be kept in memory in case you are going to go back to them. The memory is purgable though. If another program needs the memory, the memory should be freed up. That should mean that if Director needs a bit of memory to load some cast members, the QuickTime frames would be cleared. I'm not saying that this happens perfectly, it may not, but you should test to see if the memory being used by the QuickTime movie is actually causing you any problems. -- [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!]
