Hiya,
I'm currently working on a video effect that creates a
field of Cube primitives, and colours them according
to samples taken from an input image. I'm just
wondering if anyone can perhaps suggest any
optimisation I could do to the effect, as it seems to
run quite slowly. I know it's creating and controlling
a lot of the cubes (100 at the default 10 rows x 10
columns settings), but I though simple 3D shapes were
relatively easy for the GPU to produce...
I'm wondering if it's the colour-sampling part of the
code inside the Iterator thats burning the cycles, or
perhaps just the fact there's an image input to the
Iterator. I can't think of another way to get the
relevant colour values from the input, however.
Anyone any thoughts on how I might knock this thing
into a sleeker, more efficient shape?
Cheers,
alx
http://www.toneburst.nethttp://machinesdontcare.wordpress.com
__________________________________________________________
Sent from Yahoo! - the World's favourite mail http://uk.mail.yahoo.com
_______________________________________________
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
