| Peter, You are correct that custom UI continues to work just fine in Motion. In fact, we've greatly improved it, allowing you to keyframe your custom parameters now! Zero is not now, nor has it ever been, a valid parameter ID. We have a bug on it, but I don't think it's a very high priority, as most developers seem fine starting at parameter 1. (And I'd bet those porting plug-ins from other hosts probably start at parameter 2 since other hosts define parameter 1 as the input image.) You can use a custom window in a variety of ways. For example, in conjunction with custom UI in Motion, or via an OSC button in either Motion or FCPX. I believe some companies also have plug-ins that do analysis when their plug-in is first applied to a clip, so they may wish to display a custom window with a progress bar at that time. (And you can now get notified when your plug-in has been applied, before the first render - see -finishInitialSetup in the FxBaseEffect protocol.)
Darrin On Jul 18, 2011, at 7:59 AM, Peter T wrote: Following up on the publishing custom parameters to FCP X...
I was playing around with the Simple Matte sample and discovered that the custom UI does appear in Motion, but still can't be published naturally to FCP X.
I went back to one of my plugins with custom parameters and was able to see the UI in motion, but only when the parameter ID was changed to not be 0 (zero) - I had been using 0 for all my custom parameters. Once I set it to 1 say, it popped-up in Motion's inspector view! Couldn't publish again, but does show some custom support still under the hood?
Also, regarding the FxWindowAPI, have I missed any tricks to get around the lack of custom parameter support? I don't see how or when you might want to show a window? Any one have any sample uses?
On 1 July 2011 16:46, Pauli Ojala <email@hidden> wrote:
Darrin,
could you elaborate on the behavior of custom parameters in FCP X?
I have a custom parameter UI that's basically just a button that opens a window. Since this can't be published into FCP X, I've tried to replace it with a checkbox as you advised, and then publish that checkbox from Motion.
This works as far as opening the window within FCP X. From there on, it's not quite what I expected. There are two issues:
1) The FCP viewer doesn't update in response to actions in the window. The plug-in uses the FxCustomParameterActionAPI to store its data in the custom parameter. Changing this value has previously worked for triggering a re-render. I've tried using the new FxRenderNotificationAPI, but it doesn't seem to have any more of an effect.
When I drag the playhead on the FCP timeline, the updated custom param value is reflected correctly. So FCP does see the update eventually -- it just fails to re-render the current frame when the FxPlug APIs are called.
2) Although FCP maintains the modified custom parameter value correctly during a session, it doesn't seem to get saved. Next time I open FCP, the modifications are gone, and the custom param has been reset to its default value.
I could live with the lack of instant viewer updates, but the broken saving is a serious problem and will prevent me from using this method. (Customers wouldn't be happy to have their modifications silently reverted.)
Is there any way to tell FCP X that it should save a custom parameter persistently?
--
Pauli Ojala
Lacquer oy/ltd
email@hidden
On 29.6.2011, at 19.29, Darrin Cardani wrote:
> Yes, if you want features added or bugs fixed, you absolutely must report them officially using bugreport.apple.com, or whatever other bug reporting mechanisms you usually use.
>
> I should say that many of us did advocate for custom controls in Final Cut Pro X. There were, of course, time and resource constraints to deal with. But there was also a lot of resistance from management because of the way that custom controls and custom windows tend to be used. When they looked at plug-ins with custom controls, a lot of what stood out to them was gaudy logos in the inspectors, and frankly it really turned them off. Obviously, there are good and bad ways to use custom controls, but we had a hard time convincing management how important they are to usability because of the downsides.
>
> Darrin
>
> On Jun 29, 2011, at 2:07 AM, Peter T wrote:
>
>> Can I add a request to put back custom UI support in to a future version of FCP X too? Why are the custom protocols in FxPlug 2? Any plugin that creates a custom parameter doesn't complain at all, you just see nothing; not good.
>>
>> Should we be officially reporting these problems, questions and requests?
>>
>> I have to say this is a real step backwards for plugins - not even a push button parameter to allow us to spring a custom UI window, right now I'm using a 1-item popup and the newer FxWindowHost and FxWindowAPI protocols.. it's not pretty.
>>
>> -Peter
>>
>> On 28 June 2011 20:49, Darrin Cardani <email@hidden> wrote:
>> As always, we cannot speak about future developments publicly. Sorry.
>>
>> Darrin
>>
>> On Jun 28, 2011, at 12:08 PM, Eberhard Ammelt wrote:
>>
>> > 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
>> >
>>
>> --
>> 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
>>
>
> --
> 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
|