Thanks for your responses, Achim and Michael. I've poked around with it some more and I figured a few things: it's not generating any large images—i'm shrinking down a large image (1024x1024) to 32x32 using the image resize patch and sending it into a pair of nested iterators (one to handle x and one for y) where the Image Pixel patch gauges the brightness of each pixel and uses it to assign a z Position for each 'node.' No further images are generated. Constraining images dimensions & iterators to orders of 2 didn't change things, either.
I figured out that the size of the original picture has something to do with it—i switched it to use a picture that started out as 32x32 and resized that to be 33x33, 64x64, etc with performance hits that were closer to what I was originally expecting (nothing gets seriously choppy until I go up to 130x130 or so). I think maybe the image resize patch was executing constantly and not showing it, or that the image pixel patch was malfunctioning somehow; i noticed that sometimes I got massive performance hits by putting nonexistent coordinates into it. I'm still not sure what's wrong with my composition, but I think I'll just work around it for now. ————————————— Andrew Ohlmann
_______________________________________________ Do not post admin requests to the list. They will be ignored. Quartzcomposer-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com This email sent to [email protected]
