Re: Custom parameters with kFxParameterFlag_CUSTOM_UI
Re: Custom parameters with kFxParameterFlag_CUSTOM_UI
- Subject: Re: Custom parameters with kFxParameterFlag_CUSTOM_UI
- From: Eberhard Ammelt <email@hidden>
- Date: Tue, 28 Jun 2011 21:08:19 +0200
Hello Darrin,
can you please tell if custom parameters will be supported in future versions of FCP-X?
Our plugins have many custom parameters, and omitting them all will be a big problem.
Regards, Eberhard
> Currently it is not possible to publish or rig a custom UI parameter. There are some other options, depending on what you're trying to do. Since Onscreen Controls (OSCs) now work in FCPX, you could put the button in the canvas using on OSC. (I'm not saying that's great UI design - just that it could be done.) It may be possible or sensible (or not) to trigger opening your window another way, such as with a popup menu item, too.
>
> You say that your dialog has complex controls and the current frame. This sounds like it could be a good candidate for OSCs. Instead of having a dialog which shows the current frame, can you create a set of directly manipulable controls and overlay them on the footage? I don't mean putting sliders or checkboxes on the canvas, but can your controls be rethought so that they work like the new OSCs we added to many of the built-in filters? If you look at filters like Circle Blur, Droplet, Gradient Blur, etc., you'll see some of what we've done. Things that used to be sliders for widths are now rings or boxes that the user can just directly grab and change.
>
> Or it may just be better to only allow the complex interface to come up in Motion for power users and make several presets (possibly with some rigged/published parameters) for FCPX. In general, we'd like to encourage developers to make Final Cut Effects that accomplish a specific task rather than just publishing dozens of parameters from an FxPlug and exactly duplicating the functionality of the FxPlug in FCPX. Users have told us that they're overwhelmed by dozens of sliders and controls in the inspector and want more tightly focused tools that help them accomplish specific tasks. But obviously, not every plug-in will work this way.
>
> Darrin
>
> On Jun 26, 2011, at 5:05 AM, Vladimir Sergeev wrote:
>
>> Hello Darrin,
>>
>> I develop an effect FXPlug with a custom button among its
>> controls. The button opens a modal dialog with complex GUI
>> containing a set of controls and the current frame. Those
>> controls are used to analyze the frame and to modify several
>> custom parameters (created by addCustomParameterWithName with
>> the kFxParameterFlag_CUSTOM_UI flag enabled). The parameters
>> are visible/editable only in the dialog.
>>
>> This works well in FCP6/7 and in Motion5 (in Motion Projects).
>>
>> To make it work in FCP X, I need to somehow "publish" the custom
>> button to let user open the custom dialog and to adjust those
>> custom parameters based on the current frame from the FCP X project.
>>
>> Is this technically possible in the current version of FCP X?
>> If not, will such custom buttons and custom parameters be added later?
>>
>> What would be the next best way to provide the same functionality
>> directly to FCP X users (opening the FC Effect back in Motion5 will
>> likely not help, since the frame data is not provided)?
>>
>> Thank you,
>> Vladimir
>>
>> _______________________________________________
>> 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
_______________________________________________
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