Re: FCP X and parameterChanged
Re: FCP X and parameterChanged
- Subject: Re: FCP X and parameterChanged
- From: Garrick Meeker <email@hidden>
- Date: Fri, 01 Jul 2011 15:42:00 -0700
Reported as Bug ID# 9714238.
Hmm, the last render time seems fragile with all the timeline rendering happening. Maybe get the time from an on-screen control?
Any thoughts about checking out images from on-screen controls or parameterChanged? Should I file this as a bug or an enhancement request? Is there anything I can do now other than cache images from render calls?
FxHostCapabilities always reports Motion now, right? Do I need to look at the id of the application bundle to figure out if these workaround are necessary?
On Jul 1, 2011, at 9:53 AM, Darrin Cardani wrote:
> Garrick,
> This appears to be a bug that we aren't propagating the current time in some cases. Please file a bug.
>
> As for workarounds, one option would be to use whatever was the last render time if currentTime comes back as 0. It's fragile, but may be better than nothing.
>
> Darrin
>
> On Jun 30, 2011, at 10:17 PM, Garrick Meeker wrote:
>
>> I'm seeing some issues here that could seriously affect our products. First, we get the current time in the parameterChanged method with:
>>
>> id <FxCustomParameterActionAPI> actionAPI = [_apiManager apiForProtocol:@protocol(FxCustomParameterActionAPI)];
>> double t = [actionAPI currentTime];
>>
>> That works in Motion 5 and has always worked before, but in FCP X it seems to always be 0.
>>
>> And we also need access to images outside of renderOutput, specifically in parameterChanged and from on-screen controls (or custom UI in FxPlug 1). I realize this isn't guaranteed by the API but it works in Motion 4 and 5. FCP X seems to return a solid color. I've only tried the bitmap calls here. Stuffing the current OpenGL context into an FxRenderInfo to get a texture seems problematic. Trying to cache a frame from the render calls seems difficult too because of FCP's timeline rendering.
>>
>> I can file a bug but I'm really hoping there are workarounds for this release.
>>
>> _______________________________________________
>> 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