Hi Chris,
Thanks for your answer.
I just replace my pix_image object with pix_film and it works. I also send it a RGB colorspace message at loading time, this way PNGs are showing fine. Without the RGB message, JPGs are showing fine but not PNGs. Do you have any ideas why it works with JPGs and not PNGs? I did not need to re-trigger the first frame, when I load a new picture, it just show up and it's great like that. The idea of putting all the images in one sequence is not enough flexible for my project, but I did use this kind of trick in an old Hypercard project and it was really fast!
Etienne
On 04-10-28, at 01:03, chris clepper wrote:
Hi
We will look into those problems. Thanks for the report.
For another approach, try loading images with pix_movie/film and just re-trigger the first frame over and over. Also, consider making the multiple image sequences into a single moving using QTPro or similar application and stepping through the frames. This method is probably the fastest way to get images to the screen and also will allow for mixing images and movies using the various pix_ objects.
cgc
On Oct 27, 2004, at 9:50 PM, Etienne Desautels wrote:
Hi all,
I did for an interactive video installation a pd-GEM patch, a kind of video sequencer. I'm on mac os 10.3.5 with pd 0.37 and GEM 0.90. I use pix_image to load images on a rectangle and I have 2 problems with it.
First, pix_image have a system to keep each loaded image in the computer memory for using it later if you reload the _exact_ same image. But if you load a lot, say hundreds, of images, that will use a lot of memory. I'd like to know if there's a way to avoid this, a way to release this memory ?
Secondly, I think there's a bug in pix_image (and pix_multiimage also). It's suppose to use the data image in the cache if you reload the _exact_ same image, but it doesn't seem to work. That make my first problem even worst because each time you reload the same image, gem will put it another time in memory, so the memory will grow indefinitely. I did the test with pix_image and pix_multiimage and on 2 different computers (powerbook 667 with an ATI and a dual G4 1GHz with an nVidia). Each time I reload the same image, I can see the memory usage of pd growing. The only way to release the memory is to quit pd. It's not an acceptable solution for me because my installation is running all day long and at some point PD hang because there's no more memory and swap.
You could try it by using the help patch of pix_image and keep reloading the same image and watching the memory usage of pd in top.
Thank you for your help.
Etienne
GEM-dev mailing list GEM-dev@iem.at http://iem.at/cgi-bin/mailman/listinfo/gem-dev
-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support.