Examining patches, just meant "double clicking and entering that macro level", but I see it is related to moving patches on the Editor as well.
I did have the Inspector open, but it's odd... if I'm in that macro level and simply open the inspector/parameters, there is actually no performance hit at all. However, if I move a patch on the Editor, then all hell brakes loose. -George Toledo On Mon, May 3, 2010 at 4:22 PM, Christopher Wright < [email protected]> wrote: > > If you have the inspector open and you have LFOs driving the patch you > have selected, the UI redraw will cause slow downs, because QC shares > drawing in the main thread, afaik. > > Correct, they render on the same thread. A variation of this is enabling > debugging mode, where patches inside iterators will flash [Iteration] times, > which is much slower than flashing just once. > > That said, I couldn't reproduce the behavior noted here, so perhaps there's > a step or two missing? (It's not clear what the scope of "examining the > patches inside of the iterator" is). > > If you've got an inspector open, it'll draw the widgets each time a value > changes, which might be the cause? If so, please let us know :) > > -- > Christopher Wright > [email protected] > > > >
_______________________________________________ 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]
