Re: FCPX current playhead and identifying a clip in FxPlug
Re: FCPX current playhead and identifying a clip in FxPlug
- Subject: Re: FCPX current playhead and identifying a clip in FxPlug
- From: Darrin Cardani <email@hidden>
- Date: Wed, 31 May 2017 16:55:05 -0700
Daniel,
Regarding the issue of getting multiple parameters to show the full keyframe editor - I don’t think this is possible. There is a limitation of only a single parameter being able to show that view. I had thought we lifted that restriction a while ago, but apparently I was mistaken. There can be only 1.
If a parameter is rigged then keyframes won’t work because they conflict with the rig, so that makes some sense.
Given that and the issues you’re having with Rigged parameters, your best bet in this scenario is to write your own keyframe editor to display keyframes and let the user modify them. I wish I had better news.
Darrin
> On May 31, 2017, at 2:27 PM, Daniel Walz <email@hidden> wrote:
>
> Hi Darrin,
>
> using Rigs brings another problem:
> The FxKeyframeAPI keyframeCount: forParam: andIndex: returns always 0.
>
> When publishing the parameter directly, I can access the keyframes,
> even though I still can't access their value.
> I always get the value from the motion template instead of the actual
> clips automation.
> But the keyframes' positions I can get correctly.
>
> So priority is to read the keyframe values, and then it would be
> awesome to get the parameters displayed as curves.
>
> Any clues?
>
> Thanks,
> Daniel
>
>
> On Thu, May 25, 2017 at 10:32 PM, Daniel Walz <email@hidden> wrote:
>> Hi Darrin,
>>
>>
>>> On Thu, May 25, 2017 at 6:16 PM, Darrin Cardani <email@hidden> wrote:
>>> [...]
>>>> For #4, it seems that in order for a parameter to allow vertical editing in
>>>> the curve editor in FCPX, it needs to be rigged and the rig’s slider needs
>>>> to go from 0 to 100. Otherwise, it will just allow you to edit the time of
>>>> the keyframes. So you can do the following in your Motion Template:
>>>>
>>>> 1) Open the inspector for your plug-in
>>>> 2) Click on the pop-up menu for the parameter you want the user to be able
>>>> to edit using the curve editor in FCPX
>>>> 3) Click “Add to Rig” and select “Create New Rig” and then “Add to New
>>>> Slider”
>>>> 4) This will create a new Rig in your Motion Template named “Slider” which
>>>> by default goes from 0 to 100
>>>> 5) You can rename the Rig by Double-clicking on the name “Slider” in the
>>>> layer list and entering a new name
>>>>
>>>> Now when you add the generator to the timeline in FCPX and bring up the
>>>> curve editor, you can select the Rigged Slider as the parameter to show and
>>>> you’ll see the disclosure triangle on the right side. Click it and it should
>>>> expand to allow editing both the value and time of the parameter.
>>
>> Ok, that kinda works. But only for the first parameter. I have four
>> parameters to publish.
>> What is strange, it always works for the first to publish. When I add
>> more than one,
>> the first one still shows the expand button when I select it.
>> But the others show only the point in time, but no curve.
>>
>> All four parameters are identical, value 0..100.
>>
>> It makes no difference, if I add them to the same Rig or if I create a
>> new Rig for each slider.
>>
>> Can you or the Developers please check if you can add more than one
>> sliders as curves?
>>
>> Otherwise I should probably file a bug for that.
>>
>> Small extra question, is there a way to reorder the parameters? They appear in
>> opposite order of creation in motion, but they end up in random order
>> in the HUD
>> in FCPX.
>>
>> Thanks for checking,
>> Daniel
>>
>> --
>> Daniel Walz | Software Developer
>>
>> Filmstro | Music that Moves.
>>
>> www.filmstro.com | twitter/filmstro | vimeo/filmstro
>
>
>
> --
> Daniel Walz | Software Developer
>
> Filmstro | Music that Moves.
>
> Sussex Innovation Centre | Science Park Square | Brighton, BN1 9SB
>
> email@hidden | Personal mobile: +44 7491 836 008
>
> www.filmstro.com | twitter/filmstro | vimeo/filmstro
_______________________________________________
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