Re: Final Cut Pro getInputImage() returning up-side-down image?
Re: Final Cut Pro getInputImage() returning up-side-down image?
- Subject: Re: Final Cut Pro getInputImage() returning up-side-down image?
- From: Garrick Meeker <email@hidden>
- Date: Tue, 21 Dec 2010 15:13:21 -0800
It was Paul Miller who originally posted this, so I thought he might have filed a bug already. I just filed #8795939 with sample code (based on Options Dialog) to reproduce it. It seems 100% reproducible and consistent in FCP but hopefully that's not dependent on my preferences or something.
It's easy to work around (I just assume kFxImageOrigin_BOTTOM_LEFT regardless of what FCP tells us) but I'll need to update our plugins if this bug gets fixed.
On Dec 21, 2010, at 9:51 AM, Darrin Cardani wrote:
> Garrick,
> I did not file a bug about it, as I don't know all the details. I wanted you to file one with a code snippet as there might be something specific about the way you're calling it that causes this to occur.
> As for its consistency, I don't really know, since I don't know what circumstances cause it to happen.
>
> Darrin
>
> On Dec 16, 2010, at 11:21 AM, Garrick Meeker wrote:
>
>> 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
>>> email@hidden
>>>
>>>
>>> _______________________________________________
>>> Do not post admin requests to the list. They will be ignored.
>>> Pro-apps-dev mailing list (email@hidden)
>>> Help/Unsubscribe/Update your Subscription:
>>>
>>> This email sent to email@hidden
>>
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Pro-apps-dev mailing list (email@hidden)
>> Help/Unsubscribe/Update your Subscription:
>>
>> This email sent to email@hidden
>
> --
> Darrin Cardani
> email@hidden
>
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden