Ive had that happen if I use a render in image or a GLSL patch with
Quartz Composer and DO NOT use a 'clear' patch. In fact, I quite
like the effect, so I purposefully do it. You sound like you dont :
( Im not rendering to a CIImage, but just passing input and output
keys serially from one composition to another using the opaque
QCPortImage type. Not sure if that makes a difference or if this
usage scenario matches yours in any way, but it might be worth
looking into.
On Mar 12, 2008, at 1:04 AM, Neil Clayton wrote:
Hi,
I'm trying to get a CIImage from a QCRenderer object. I've basing
my code on QuartzComposerOffline but then saw weirdness in the
images being returned. I reverted to the original
QuartzComposerOffline project but I find the same thing.
I'm seeing odd artifacts from the display buffer making their way
into the images being generated by the code. The essentials of
the Quartz Composer files are rendered to separate images OK (the
qtz file plays OK in the composer itself and in quick look), but it
as if there is rubbish being pulled from some context in the
background of every image. It's almost as if the background isn't
cleared before each frame is rendered...
Am I running into a well known bugette here? (Im targeting 10.4,
and building using XCode 2.5 (running on 10.5.2))
--
Regards,
Neil Clayton, http://shinywhitebox.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartz-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartz-dev/email@hidden
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartz-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartz-dev/tkoelling
%40apple.com
This email sent to email@hidden
