OK, I see. My problem was that I was importing dinamically the images, and they are about 200, so the system easyly runs out of memory. I'll have to change my handlers, because I cannot have 200 images at memory simultaneously.
try using a linked bitmap castmember & setting it's filename property
member().filename = "path-filename1" -- do some stuff member().filename = "path-filename2"
the above performs a switch to 'path-filename1' & then another to 'path-filename2'
The problem is that if I import 20 images of 4 MB in total, the cast is about 27 MB, and I saved and compacted the movie...and still the .dir is about 21 MB.
Director authoring stores a copy of the expanded image for faster bitmap compositing & for Paint Window editing
hth
-Buzz
Thank you very much.
Richard Hebert.
-----Mensaje original----- De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] En nombre de Thomas Higgins Enviado el: viernes, 14 de noviembre de 2003 18:55 Para: '[EMAIL PROTECTED]' Asunto: RE: <lingo-l> Importing Images
Richard,
I've already posted this on another forum. I've noticed that each time you import an image (for example a jpeg of 300KB and 24bits) Director stores it in the cast as a bitmap of 32 bits (OK, you can choose the 24bits option in the importing window, but it is a bitmap!!) that becomes about 7.3 MB!!!
Each image I import, it always becomes about 20 times bigger. Besides that, I import the images dynamically, so I cannot select the colour bits of image...:
newImage = new(#bitmap, castLib "temp") newImage.filename = gPathActual&gListaFotos[i] -- it is the correct path
Really don't know how to solve this... Any idea???
I don't believe there is anything to solve here, just an explanation of what you are seeing. :) When you're looking at the size of your jpg file (300Kb) you're looking at the disk size of the data (thus you're seeing the size of the data when compressed). When you're looking at a cast member's size inside of Director (7.3Mb) you're seeing the memory size of the data (thus you're seeing the size of the image data when decompressed into memory). Check the actual *.cst/*.dir file size change after performing the image import (make sure to save and compact to be sure), I doubt your file size ballooned by 7.3Mb (did it?).
Cheers, Tom Higgins Product Specialist - Director Team Macromedia
...
[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!]
[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!]
[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!]
