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, pro-apps-dev-request@lists.apple.com wrote:
Send Pro-apps-dev mailing list submissions to pro-apps-dev@lists.apple.com
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 pro-apps-dev-request@lists.apple.com
You can reach the person managing the list at pro-apps-dev-owner@lists.apple.com
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 <dieterdavebecker@gmail.com> To: pro-apps-dev@lists.apple.com Subject: Publishing of Custom Parameters of FCPx Plugs inside Motion Message-ID: <7FE2B828-1725-4F21-A882-2F93F2C7CF2F@gmail.com> 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