caching of image importer vs image downloader

• Subject: caching of image importer vs image downloader
• From: "Roger Bolton" <email@hidden>
• Date: Fri, 27 Jan 2006 15:15:17 +1100
• Delivered-to: email@hidden
• Delivered-to: email@hidden

is there a significent different in the way an image is cached by Quartz Composer when
using image importer vs image downloader?

I am trying to create compositions that animate cycling quickly through all the images in a 
folder. I change the image url to a series of image downloaders as it progresses.

using "folder images" and image importer it renders very unevenly, it can't keep an even 
framerate and pauses for a long time on some images.  this is true even though the images 
have already been loaded once and are all on the local harddisk.

if I drag in all the images using image importers and cycle them through a multiplexer it will 
render smoothly.

problem is how to have it automatically load images from folders while still having good 
performance?

thanks for any info

Roger
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/email@hidden

This email sent to email@hidden

• Follow-Ups:
  • Re: caching of image importer vs image downloader
    • From: Pierre-Olivier Latour <email@hidden>

• Prev by Date: Re: qc3dloader...
• Next by Date: Re: caching of image importer vs image downloader
• Previous by thread: Quartz Composer Tutorial on Replicate in Time
• Next by thread: Re: caching of image importer vs image downloader
• Index(es):
  • Date
  • Thread