Good call, that's definitely an aspect of this as well, and will also fix performance.
I almost *never* use that (and edit directly in a patches input ports), but in this case, I did have the Inspector open. -George Toledo On Mon, May 3, 2010 at 4:19 PM, vade <[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. > > I've definitely seen this sort of behaviour. Deselecting restores previous > FPS, right? > > > On May 3, 2010, at 4:16 PM, George Toledo wrote: > > > Using this composition, with a Viewer area of 530x375 (or similar), when > I am running the composition, with the Editor open, I get a framerate of > around 30fps in most instances. However, when I am examining the patches > inside of the Iterator environment when using the Editor, my performance > slows to 6~7fps. > > > > It seems extremely odd that the Iterator should be doing any kind of > extra evaluation because of what level is selected inside of the Editor app. > Do others have similar results? > > > > Thanks, > > George Toledo > > <Motion Links GLSL.qtz> _______________________________________________ > > 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/doktorp%40mac.com > > > > This email sent to [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]
