site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com I think I just ran into this in FCP. In Motion 4 it seems to work correctly. I was just caching the image from the last render call but I'd like to avoid hogging this memory. Did you file a bug about this? Is there any workaround in FCP, or is it reliable enough that we can assume an upside down image (until a future version of FCP fixes this)? On Oct 19, 2010, at 12:40 PM, Darrin Cardani wrote:

On Oct 19, 2010, at 11:57 AM, Paul Miller wrote:

...

On 10/19/2010 1:55 PM, Paul Miller wrote:

...

In response to a button (custom UIButton view) press I'm calling getInputImage() to fetch the full-frame (progressive) image for the current frame. The returned image has an orientation of top-left, but it's actually up-side-down in memory. What did I do wrong?

Oops - sorry for the C-style function format. I'm referring to the getInputBitmap method of the FxTemoralImageAPI.

Hmm.... it doesn't sound like you've done anything wrong. I can't imagine a situation where we would send you an upside down image and it would be correct. Could you file a bug about this?

Thanks, 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/garrick%40digitalanarchy...

This email sent to garrick@digitalanarchy.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