
Quartz Composer 3D Carousel (and loading images with an iterator)
1 year ago
This is a little sample Quartz Composer composition which loads a bunch of images from a directory, and creates a 3D carousel from it (cos we all love carousels, dont we).
The main purpose of this was to demonstrate how to load multiple images (using the Image Downloader) from within an Iterator patch. You'd think it was quite straightforward, just send a different string (either generated within the iterator or loaded from XML etc.) to the Image Downloader, but alas QC has other plans. It always loads the same image whatever string you send it!
So there is a hack workaround using a recursive JavaScript patch which I read about somewhere in the cloud and cannot find right now. Its quite an important issue I think as there are loads of questions regarding this on forums but with no answers...
Source file and more info at memo.tv/quartz_composer_3d_carousel_and_loading_images_within_an_iterator
The main purpose of this was to demonstrate how to load multiple images (using the Image Downloader) from within an Iterator patch. You'd think it was quite straightforward, just send a different string (either generated within the iterator or loaded from XML etc.) to the Image Downloader, but alas QC has other plans. It always loads the same image whatever string you send it!
So there is a hack workaround using a recursive JavaScript patch which I read about somewhere in the cloud and cannot find right now. Its quite an important issue I think as there are loads of questions regarding this on forums but with no answers...
Source file and more info at memo.tv/quartz_composer_3d_carousel_and_loading_images_within_an_iterator
-
Vimeo: About / Blog / Developers / Jobs / Community Guidelines / Community Forums / Help Center / Site Map / Merchandise
/ Get Vimeo

Previous Week
Btw, you can get around the image loading issue by passing in a structure of image paths, and using the current iteration as the structure index to load the right image.
Best ways to do it I've found are either to store the paths in a text file and use the string components to split it into a structure (requires a plugin to load the text, the kineme file tools one does it nicely), or put all the paths in an xml file which gives you a structure straight off.