Hi
My application uses the QCRenderer API to input and output images in the opaque QCImage format and send them through a chain of published input and output images in QCCompositions/Renderers I control.
Ive noticed in 10.11, performance seems worse. Looking into it, I’m noticing that *certain* configurations of Core Image filters and custom QC Plugins / output images vended as QCImages cause read back to occur on the CPU. I would attach an image, however I know that that requires moderation for external links, so il post in a comment below.
Ive tried to account for various different causes - like pixel format issues, color space issues, etc, but I cannot get rid of the CPU read back, which I am 99.999% positive didn’t happen in older Quartz Composer framework/API versions as older hardware got better frame rates - likely keeping things on the GPU where they belong™.
Has anyone else seen regressions in performance with QC and Core Image?
Any hints as to why there might be rendering path changes in QC or Core Image?
Thank you.
