site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com In the meantime, you can see if you are running inside FCPX by checking [[NSBundle mainBundle] bundleIdentifier]. On Nov 30, 2011, at 1:34 PM, Darrin Cardani wrote:
Paul, This seems familiar to me. I think this is something I worked on recently, and I believe will be fixed in a future release. If you could send me a sample plugin – it can just print to the console, doesn't need to do much of anything – I can figure out if it's been fixed, or if we need to do additional work on it.
Thanks, Darrin
On Nov 30, 2011, at 10:50 AM, Paul Young wrote:
I'm trying to make sense of an apparent upside-down buffer issue in an FxPlug2 plugin I'm developing.
I'm of course still looking for things I may be doing wrong on my end, but here's what I think I'm seeing:
In Motion 5 (5.0.1), when my renderOutput: method is called, the inputImage & outputImage return 0 (kFxImageOrigin_BOTTOM_LEFT) for origin and the first row of pixels, upon inspection, is indeed the bottom row of the image.
In FCPX (10.0.2), using a .moef for the same plugin, when my renderOutput: method is called, the inputImage & outputImage return 0 (kFxImageOrigin_BOTTOM_LEFT) for origin but the first row of pixels, upon inspection, is the TOP row of the image.
(The same is true for FxImageInfo.origin in the various places I've checked it.)
In both cases, FxHostCapabilities indicates that Motion is the host. (I guess this almost makes sense in this .moef model... but it's a bit of a head scratcher... might rather have "Motion-Inside-FCPX")
This is software-only rendering (32-bit float bitmaps). I've confirmed that I can create new bitmaps stamped as kFxImageOrigin_TOP_LEFT.
There's plenty of mention in the docs about FCP buffers being top down, but perhaps they're getting stamped incorrectly on their way through the Motion rendering engine?
Has anyone else seen this? Any ideas on how to work around it? (Including a reliable way to detect that FCPX is the host? Not ideal but workable in the short term.)
Many thanks,
paul _______________________________________________ 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/dcardani%40apple.com
This email sent to 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/pschneider%40apple.com
This email sent to pschneider@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... This email sent to site_archiver@lists.apple.com