Re: FxPlug 2 Answers, etc.
Re: FxPlug 2 Answers, etc.
- Subject: Re: FxPlug 2 Answers, etc.
- From: Darrin Cardani <email@hidden>
- Date: Fri, 24 Jun 2011 10:14:54 -0700
Pete,
1) As I mentioned to Pierre, fields aren't labeled properly in FCPX. Everything ends up getting labeled as progressive. Yeah, I know. It was found in testing, but too late to fix. I'm pushing to get the fix in the soonest possible update. FWIW, it works properly in Motion.
2) I'm not aware of any problems accessing parameters over time. Were there problems before? If you have some specific use-cases, I could check them, if they're not too complicated.
3) I'm not sure what you mean by "properly supported." But yes, fields are sent to the plug-ins separately. They are full-height. I will have to check to see whether they are line doubled or interpolated.
4) A quick test shows everything coming in at the same scale. When you have the canvas at 50%, temporal images and image well images appear to be at 50% also.
5) I'm not aware of any problems getting images in different formats. You will never again receive images in YUV format, though.
6) Yes, checkboxes and popups are animated. They use step interpolation.
Hope that helps!
Darrin
On Jun 23, 2011, at 7:58 PM, Peter Litwinowicz wrote:
> Just because API support is there doesn't mean all features work (as we
> have seen before, right? :-) ).
> Any known problems with working with FCP/Motion and plugins. Specifically:
> 1) Accessing images over time
> 2) accessing other params over time
> 3) input source or output images with interlacing properly supported? If
> so are images at half height or full height? And, if at full height, are
> the inbetween scanlines doubled or interpolated?
> 4) images all at same size for checkout? (previously, in FCP, if you
> checked out an image when working at 50% resolution, the main input would
> be at 50% resolution and all other clipwell inputs were at 100%)
> 5) problems with getting images in formats: RGBA? YUVA?
> 6) checkboxes, menus are now animated? (that's a UI question not an API
> question). If so, do animated params of these types keep their previous
> values before seeing a new keyframe? (that is, these types are animted as
> step curves and not as linearly interpolated floating values)?
>
> Of course we have a vested interest in the answers to these questions...
> Pete
>
>
> On 6/23/11 9:23 AM, "Darrin Cardani" <email@hidden> wrote:
>
>> Hey all,
>> I'm back in the office today. I'm going to take some time and read over
>> all your questions and get you some answers today and hopefully help
>> everyone find solutions that will work for you, your customers, and us.
>> It's going to take me some time to get caught up, so please be patient
>> with me (and everyone else who's helping me answer questions).
>>
>> 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