A few other general tips, in addition to the great ones that have been previously mentioned:
-Disable render patches if they aren't visible at the moment (eg., they are located at "offscreen position", or "covered up" by other renders. -Manage pixel h/w wisely. You can many times "downsample" the height and width of an image before processing it with Core Image filters, using Image Resize, Lanczos Scale, or even by placing a scene in a Render In Image and halving or quartering the quality, using the pixel input parameters. If one is using a particularly overt filter, the visual result can be acceptable, and will run much quicker. -When rendering to a Billboard, go into Settings and see if Native Core Image Rendering makes your composition run faster, or slower (this can go either way). -When using the Render In Image, and the Video patch, see if turning off color correction gains you any fps. -When using the Render In Image, disabling the depth buffer can gain fps (it can also effect the visual output, so use cautiously). -If the objective is to make a final image larger than the source, try to use the final render to enlarge the source by manipulating the height and width of that render (a sprite for example), instead of enlarging it after the source, and doing all CI processing on a source with large pixel h/w. -Similarly, using the actual render (sprite, etc.) for transforms and rotations tends to be more efficient than using CI/Image Processing patches to achieve similar looks. -Hooking image sources to any consumer patch, even ones that do not render, such as a 3D transform, or any macro environment that has a render inside, will make that source evaluate. When using things like movie players, or other image inputs, this will cause the source to evaluate, even if it's not going on to a final rendering destination at the moment. Best regards, George Toledo On Wed, Feb 17, 2010 at 8:34 AM, Christopher Wright <[email protected]>wrote: > Does anyone have any good links or advice on how to optimize QCs >> performance? I have a composition that's fairly simple, but spins the >> disk and locks up my UI occasionally. Any help on performance in >> general would be appreciated. >> > > > Shark and Instruments can help, if you're accustomed to software > development profiling. > > Otherwise, hold option and open the preferences. Under (Editor) there's a > disableVBLSyncing option -- enable it, quit QC and restart it. (changing > that option requires a QC restart) [be sure to reenable it when you're > done -- it can lead to tearing] > > That will uncap your framerate so you can time different things more > accurately. > > Start by disabling all the renderers, and then enable them one by one (or > one at a time) -- note the performance. > > Debug mode will help spot which patches are actually executing, which can > be good to know. > > Activity Monitor can help spot memory leaks (endlessly increasing memory > usage) -- this will lead to performance degradation over time, and might be > the cause of your UI stalls and disk activity. If you uncover a bug, > please file a radar at http://bugreporter.apple.com > > As for general tips: do as little image processing and loading as > possible, and don't do loading or processing in iterators if you can do it > otherwise. > > -- > [ christopher wright ] > [email protected] > http://kineme.net/ > > > _______________________________________________ > 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/gtoledo3%40gmail.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]
