site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com On Jul 31, 2008, at 11:07 AM, David Yamnitsky wrote: y = height - y; Darrin -- Darrin Cardani dcardani@apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.ap... I've been trying to render out Quartz Composer compositions into FxPlug using a QCRenderer, and have had a lot of success by first rendering the composition to an FBO, and then drawing the output to the actual destination. To avoid this unnecessary step, I've been hoping to draw using the QCRenderer directly, and have gotten it working properly in Motion, but in FCP it's been more difficult. First of all, the coordinate system is flipped, so all rendering is flipped (except drawing of the input image (for an FxFilter)). This can usually be dealt with by either setting your transformation matrix correctly, or if you're operating directly on the pixels yourself, you can use something along the lines of: With my FBO implementation, rendering scale, pixel aspect ratio, and half height fields were all handled because I could control the context of the FBO. How would I handle all those directly? I've done several tests and found that the "Rendering Destination Dimensions" in QC do not reflect those considerations. See the example plugin called Scrolling Rich Text. It describes how to deal with all of these things in your code. This email sent to site_archiver@lists.apple.com