Re: Pro-apps-dev Digest, Vol 13, Issue 8
Re: Pro-apps-dev Digest, Vol 13, Issue 8
- Subject: Re: Pro-apps-dev Digest, Vol 13, Issue 8
- From: Darrin Cardani <email@hidden>
- Date: Fri, 09 Sep 2016 13:23:23 -0700
Dieter,
It’s not obvious at all. If you look in the headers, you’ll see that many of the APIs have a note saying which version of the FxPlug SDK introduced that version of the API. It’s then another leap from which version of the FxPlug SDK was released with which version of Motion or Final Cut Pro. We don’t have a chart anywhere, unfortunately.
There is a version history in the FxPlug documentation, though. You can see it here:
<https://developer.apple.com/library/mac/documentation/AppleApplications/Conceptual/FXPlug_overview/FxPlugVersionHistory/FxPlugVersionHistory.html>
and from the “What’s New” section:
<https://developer.apple.com/library/mac/documentation/AppleApplications/Conceptual/FXPlug_overview/WhatsNewinFxPlug3.1/WhatsNewinFxPlug3.1.html#//apple_ref/doc/uid/TP40002180-CH240-SW1>
For example:
FxPlug 2.4 shipped with Motion 5.0.5 and FCPX 10.0.5
FxPlug 3.1 shipped with Motion 5.2.2 and FCPX 10.2.2
At this point you should be targeting FxPlug 3.0 or higher, most likely.
You can also check at runtime if a given API is implemented by asking the _apiManager object for it. If it returns nil then that API is not implemented in the host you’re currently running in. Otherwise, it is and you’ll get a valid API object back.
Looking at the “What’s New” for FxPlug 3.0, that appears to be when we started supporting publishing of custom parameters:
<https://developer.apple.com/library/mac/documentation/AppleApplications/Conceptual/FXPlug_overview/WhatsNewinFxPlug3.0/WhatsNewinFxPlug3.0.html#//apple_ref/doc/uid/TP40002180-CH239-SW1>
“ • Custom UI support for Final Cut Pro Effects containing FxPlug 3–based plug-ins.”
I’m sorry it’s not easier to find all this information in one place. If you have suggestions for how to improve things, then by all means file a bug requesting what you need and we’ll look into it:
<http://bugreport.apple.com/>
Darrin
> On Sep 9, 2016, at 12:46 PM, Dieter Becker <email@hidden> wrote:
>
> Hi Darrin,
>
> thanks a lot for your answer… This might be a full-on dumb Q but here goes..
>
> We downloaded the latest version of FxPlug and built upon one of the examples.
> We are not targeting anything specific aside from using latest version of FCPX and Motion.
>
> Where do we ‘Target’ the Versions of FCPx and Motion ? Checked build-settings in Xcode and wasn’t able to find anything on the go…
>
> Are we missing something very very obvious ? Are the examples Old ?
> At least the Example of the Current version of FxPlug (Options Dialog) is NOT publishable when opened in Xcode and just built.
>
> So where do we go about targeting the Versions of FCPx and Motion ?
>
>
> Thank you very much for your time, Darrin
>
>
> — Dieter
>> On 9 Sep 2016, at 21:00, email@hidden wrote:
>>
>> Send Pro-apps-dev mailing list submissions to
>> email@hidden
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> https://lists.apple.com/mailman/listinfo/pro-apps-dev
>> or, via email, send a message with subject or body 'help' to
>> email@hidden
>>
>> You can reach the person managing the list at
>> email@hidden
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of Pro-apps-dev digest..."
>>
>>
>> Today's Topics:
>>
>> 1. Publishing of Custom Parameters of FCPx Plugs inside Motion
>> (Dieter Becker)
>> 2. Re: Publishing of Custom Parameters of FCPx Plugs inside
>> Motion (Darrin Cardani)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Fri, 09 Sep 2016 16:29:25 +0200
>> From: Dieter Becker <email@hidden>
>> To: email@hidden
>> Subject: Publishing of Custom Parameters of FCPx Plugs inside Motion
>> Message-ID: <email@hidden>
>> Content-Type: text/plain; charset="utf-8"
>>
>> Hi There,
>>
>> 1) we have successfully created custom sliders etc. inside our plug-in.
>> 2) The plug-in is unusable to any user if the sliders are row-bases. As in Slider 1 new line slider 2 new line etc… They need to be adjacent not below/above one another.
>> 3) The FxPlug built-in sliders are not able to to provide the ‘feel’ and fitness that our users want so we have no choice than to provide out own slider functionality. Which we have done in Premiere Pro, Photoshop, After Effects etc… It Works wonderfully inside of Motion.
>>
>> Here some the HUGE However…. Why are we not able to publish this slider as all the Built-In sliders for use on FCPx ?
>> Are we missing something very very very obvious ? Or is it impossible to publish custom sliders to Final Cut Pro X from a template.
>>
>> If so, then what is the point of all this ‘Custom’ in FxPlug? Why add a custom slider to FxPlug if one cannot use it in FCPX :D - Since that would make zero sense, we are arriving at the conclusion that we are being the idiots missing something everyone else it not…
>>
>> Any advice would be fantastic so that we can move on.
>>
>>
>> Thanks a lot
>>
>> Dieter
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: <https://lists.apple.com/mailman/private/pro-apps-dev/attachments/20160909/fa60b951/attachment.html>
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Fri, 09 Sep 2016 08:46:10 -0700
>> From: Darrin Cardani <email@hidden>
>> To: Dieter Becker <email@hidden>
>> Cc: email@hidden
>> Subject: Re: Publishing of Custom Parameters of FCPx Plugs inside
>> Motion
>> Message-ID: <email@hidden>
>> Content-Type: text/plain; charset="utf-8"
>>
>> Dieter,
>>
>> What versions of Motion and FCPX are you targeting? There was a time when custom controls could not be published, but that is no longer the case. If you’re working with an older version, that might be the issue. If you’re working with the current release (or really any recent release from the last year or two), you can simply right click in the area below the parameter name and you should get a popup which allows you to publish the parameter. Please let me know if you have any questions.
>>
>> Darrin
>>
>>> On Sep 9, 2016, at 7:29 AM, Dieter Becker <email@hidden> wrote:
>>>
>>> Hi There,
>>>
>>> 1) we have successfully created custom sliders etc. inside our plug-in.
>>> 2) The plug-in is unusable to any user if the sliders are row-bases. As in Slider 1 new line slider 2 new line etc… They need to be adjacent not below/above one another.
>>> 3) The FxPlug built-in sliders are not able to to provide the ‘feel’ and fitness that our users want so we have no choice than to provide out own slider functionality. Which we have done in Premiere Pro, Photoshop, After Effects etc… It Works wonderfully inside of Motion.
>>>
>>> Here some the HUGE However…. Why are we not able to publish this slider as all the Built-In sliders for use on FCPx ?
>>> Are we missing something very very very obvious ? Or is it impossible to publish custom sliders to Final Cut Pro X from a template.
>>>
>>> If so, then what is the point of all this ‘Custom’ in FxPlug? Why add a custom slider to FxPlug if one cannot use it in FCPX :D - Since that would make zero sense, we are arriving at the conclusion that we are being the idiots missing something everyone else it not…
>>>
>>> Any advice would be fantastic so that we can move on.
>>>
>>>
>>> Thanks a lot
>>>
>>> Dieter
>>> _______________________________________________
>>> 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
>>
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: <https://lists.apple.com/mailman/private/pro-apps-dev/attachments/20160909/1898637c/attachment.html>
>>
>> ------------------------------
>>
>> _______________________________________________
>> Pro-apps-dev mailing list
>> email@hidden
>> https://lists.apple.com/mailman/listinfo/pro-apps-dev
>>
>> End of Pro-apps-dev Digest, Vol 13, Issue 8
>> *******************************************
>
>
> _______________________________________________
> 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