Re: Setting keyframes in FxPlug
Re: Setting keyframes in FxPlug
- Subject: Re: Setting keyframes in FxPlug
- From: Garrick Meeker <email@hidden>
- Date: Thu, 22 Jul 2010 11:43:02 -0700
Filed radar #8223125.
On Jul 22, 2010, at 10:59 AM, Darrin Cardani wrote:
> Please file a request. We have other requests for it already, but more requests usually equals more weight in management's mind.
>
> Darrin
>
> On Jul 22, 2010, at 10:54 AM, Garrick Meeker wrote:
>
>> Then should I file a feature request for an API to modify keyframes, or is this already under consideration?
>>
>> On Jul 22, 2010, at 10:42 AM, Darrin Cardani wrote:
>>
>>> In my opinion, Motion's doing the correct thing, and FCP is not. The parameter setting API is not intended to set keyframes.
>>>
>>> Darrin
>>>
>>> On Jul 22, 2010, at 10:36 AM, Garrick Meeker wrote:
>>>
>>>> Another note about keyframes. In FCP, we can have the user set keyframes on some parameters and then calling the set parameter value methods will create new keyframes (current only the current frame due to the bug below). In Motion, these methods don't create new keyframes. We'd have to require the user to manually create keyframes for every frames. Is this a bug? Should Motion behave like FCP? Or do we just need a new interface in the FxPlug API? A new interface would let us skip the step of the user creating the initial keyframes but that's secondary to our issue with Motion.
>>>>
>>>> On Dec 6, 2009, at 2:43 PM, Paul Schneider wrote:
>>>>
>>>>>
>>>>> Hi Garrick,
>>>>>
>>>>> This looks like a bug in FCP. Unfortunately, it's still there in version 7. I've filed radar #7447967 to track fixing it. Sorry about that...
>>>>>
>>>>> - Paul
>>>>>
>>>>>
>>>>> On Dec 5, 2009, at 11:41 PM, Garrick Meeker wrote:
>>>>>
>>>>>> I know that FxPlug doesn't have an interface for manipulating keyframes, and that the set parameter value methods won't set a keyframe until the user has keyframed that parameter. I can't even get these methods to have any effect for times other than the current one (atTime != currentTime). I'm calling this from the action on a custom parameter, and yes, I'm calling startAction first.
>>>>>>
>>>>>> I've only tried this in FCP6 as I don't have access to FCP7 yet. Has anyone else tried this?
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>>>
>>
>
> --
> 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