azs last edited by
I have a student who wants to display 2000+ photos. He is using an arduino connected to 3 potentiometers that control the speed at which the images change, the number of images on the screen and the pixelation of the images. In his project, there is one scene that displays one image, one scene that displays 4 images, and one scene that displays 16 images. In each scene images change at the rate of every .25 sec to every 10 seconds, depending on the potentiometers. He is using the limit resolution actor in order to pixelate the images. I am wondering how to optimize this project for speed.In the screen with sixteen images, he could limit the resolution of each image so the total pixels will never exceed 1920 x 1080 or less. But is this going to help, if Isadora has to load each 1920 x 1080 image before it reaches the limit resolution object? What else could he do?
mark last edited by
Dear Azs,Well, the essential thing here is that the images are stored as 1920x1080\. That's the size that Isadora will load; the Limit Resolution actor is "downstream" of this, so it will not affect the load time.The only other thing I can suggest is to play some different codecs -- the bottleneck here is probably going to be the hard drive. So compressing the images so there's not such a large amount of data to load would be helpful. Still, each image needs to be decompressed, and this takes time as well. trying a few possibilities to see how it affects the load speed would be a good idea. I'd start with JPEG and PNG, and go from there. (TIFF can be compressed, but only with LZW which is going to decompress fast but not save you too much in terms of image size.)Hope that helps,Mark
arronlee last edited by
So you must need a fine Image SDK which allows you to do batch processing work for you, right? What's your choice?