On 5/22/06, Pierre-Olivier Latour <email@hidden> wrote:
> The processing path of my application is this:
>
> CIImage -> QCRenderer/CIFilter -> CIImage -> Texture -> OpenGL calls
> (morphing, warping) -> CImage -> QCRenderer/CIFilter -> display (GL)
You can simplify this quite a bit: avoid unnecessary CIImage
roundtrips. Just use CVOpenGLBuffers to render GL stuff into and pass
them to QC.
Well I need to offer the use of CIFilters as well, and thus need
CIImage. But I could have different paths whether QCRenderer are used
or CIFilters are used.
> The user should be able to use his own Quartz Composition (or a
> CIFilter), either before my opengl calls or after. So I guess I must
> render QC output into a pixel buffer directly, although it would have
> been easier with all CIImage approach.
