There appears to be a bug in QCRenderer which affects compositions where two or more custom QCPlugIn instances access a single published image input.
The general procedure to trigger this is: 1. Install any custom QCPlugIn which calls -lockBufferRepresentationWithPixelFormat: colorSpace: forBounds: 2. Install any custom QCPlugIn which calls -lockTextureRepresentationWithColorSpace: forBounds: 3. Construct a QC composition which publishes an image input, and splits that input to instances of the two custom QCPlugIns. Ensure the lockTexture... plugin executes first, for instance by connecting its output to a lower-layered consumer. 4. In an application configure a QCRenderer to load your QC composition. 5. call -setValue: forInputKey: on the QCRenderer to attach a valid CIImage to the published image input. 6. call -renderAtTime: arguments: on the QCRenderer at which point an exception is raised and the message "[QCImageTextureBuffer bytesPerRow]: unrecognized selector sent to instance ..." is logged to the console. I have filed this as #9053249 with sample code to reproduce. If anyone thinks this might affect them I can forward the code. There appear to be some situations in which this isn't triggered... if anyone has encountered and worked around it, I'd be very glad to hear. Cheers, Tom
_______________________________________________ Do not post admin requests to the list. They will be ignored. Quartzcomposer-dev mailing list (Quartzcomposer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
