September 2016 - Pro-apps-dev

Re: Motion Image Depth
by Darrin Cardani 12 Sep '16

12 Sep '16

Starting with Motion 5.0 (I think?) all renders are 32-bit per channel when happening on the CPU or 16-bit per channel half float when rendering on the GPU. You can specifically request a different bit depth when using either the parameter API to retrieve an image from an image well or when using the temporal image API to request frames at different times. Note that if you request an 8-bit render of a 32-bit image, values < 0 or > 1 will be clamped to 0 or 1 (or really 0 or 255 in 8-bit). Darrin > On Sep 12, 2016, at 2:47 AM, Dieter Becker <dieterdavebecker(a)gmail.com> wrote: > > Hi There, > > I have a question about this… > > We’ve created 3 tiff images in Photoshop and stored them separately as 8, 16, 32 bits respectively. > > Dragging any into Motion and logging the inputImage/outputImage bit depth during render or setup all yields 32 bit regardless.. > > > Should it not report 8, 16, 32 respectively. > > Is this a behavior of the FxPlug or Motion ? > > > THanks > > > Dieter > > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/pro-apps-dev/dcardani%40apple.com > > This email sent to dcardani(a)apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: FxHostCapabilities
by Darrin Cardani 12 Sep '16

12 Sep '16

_______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Motion Image Depth
by Dieter Becker 12 Sep '16

12 Sep '16

Hi There, I have a question about this… We’ve created 3 tiff images in Photoshop and stored them separately as 8, 16, 32 bits respectively. Dragging any into Motion and logging the inputImage/outputImage bit depth during render or setup all yields 32 bit regardless.. Should it not report 8, 16, 32 respectively. Is this a behavior of the FxPlug or Motion ? THanks Dieter _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

FxHostCapabilities
by Dieter Becker 11 Sep '16

11 Sep '16

_______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Pro-apps-dev Digest, Vol 13, Issue 8
by Darrin Cardani 09 Sep '16

09 Sep '16

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/Con…> and from the “What’s New” section: <https://developer.apple.com/library/mac/documentation/AppleApplications/Con…> 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/Con…> “ • 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 <dieterdavebecker(a)gmail.com> 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, pro-apps-dev-request(a)lists.apple.com wrote: >> >> Send Pro-apps-dev mailing list submissions to >> pro-apps-dev(a)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(a)lists.apple.com >> >> You can reach the person managing the list at >> pro-apps-dev-owner(a)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(a)gmail.com> >> To: pro-apps-dev(a)lists.apple.com >> Subject: Publishing of Custom Parameters of FCPx Plugs inside Motion >> Message-ID: <7FE2B828-1725-4F21-A882-2F93F2C7CF2F(a)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 >>

1 0

Re: Pro-apps-dev Digest, Vol 13, Issue 8
by Dieter Becker 09 Sep '16

09 Sep '16

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

1 0

Re: Publishing of Custom Parameters of FCPx Plugs inside Motion
by Darrin Cardani 09 Sep '16

09 Sep '16

_______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Publishing of Custom Parameters of FCPx Plugs inside Motion
by Dieter Becker 09 Sep '16

09 Sep '16

_______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0