So, are you saying with it on it could be faster?When it is on, we use [ciContext drawImage:], just like you would do in your own code with a fully CI-based render chain. That's why it is fast, the CoreImage framework can do their special optimizations and make it so.
Yes -- it saves some round-trip GL stuff (CIImage -> GL texture -> GL_QUAD) to become (CIImage -> context). Behind the scenes, I imagine it's doing something very similar, but CI has an advantage when it knows exactly how many pixels are visible, how large the destination extent is, what parts are offscreen, etc. with that extra information, it can potentially end up doing less work (fewer pixels to evaluate, for example).
For me, Video Input -> Gaussian Blur -> Billboard is about twice as fast with Native Core Image Rendering enabled. This characteristic is probably different for different video sizes (mine's 640x480) and GPUs (mine's a GMA950).
-- [ christopher wright ] [email protected] http://kineme.net/
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ 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]
