| |||
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
| Have a look at /Developer/Examples/QC/PlugIns 1) You can't specify what input you want, you'll get what's optimal for QC / GPU / etc... 2) Keep directly the input images in your plug-in and use: - (BOOL) didValueForInputKeyChange:(NSString*)key; 3/4) If you want the best performances for data that you must generate on the fly (it's not already around in a buffer), use a QCPlugInOutputImageProvider, not the -[QCPlugInContext outputImageProviderFromBufferWithPixelFormat] On Oct 28, 2007, at 9:41 PM, Sam Kass wrote: I wrote a couple plug-ins for QC 3.0 (detailed on my QC blog: http://www.samkass.com/blog). They're not very efficient, and I was wondering if anyone had started hacking around with the official plug-in interface yet. I included the source to my plug-ins for reference. ________________________________ |
_______________________________________________ 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
| References: | |
| >My First Plug-In (From: Sam Kass <email@hidden>) |
| Home | Archives | FAQ | Terms/Conditions | Contact | RSS | Lists | About |
Visit the Apple Store online or at retail locations.
1-800-MY-APPLE
Contact Apple | Terms of Use | Privacy Policy
Copyright © 2007 Apple Inc. All rights reserved.