Hi, We're updating our plugins to offer native arm64 support in Final Cut Pro X and thus porting our existing code over to the FxPlug4 API. Here's were we're running into issues: Out plugin features a custom parameter (essentially a push button) that opens a configuration window on the UI thread. This window is supposed to display the frame at the current timeline cursor position. Since the FxTemporalImageAPI which we had been using before for that purpose has been deprecated, how could something like that be implemented? We tried adding a hidden int slider parameter that gets incremented once our selector is hit in order to force a re-render and then grab the current frame in renderDestinationImage:... . However, the render pipeline seems to be stalled until our selector has exited so our force render mechanism seems to be ineffective. So how do we relieably filter out and grab the source image at the current time position in FxPlug 4 ? Thanks! Best, Ray

I'd like to react to changes of the activated/deactivated state of my plugin in FCPX/Motion, but I can't seem to find any info on how to achieve that in the FxPlug API.Attaching the debugger I can see that the host calls into parameterChanged: with parmID=1 once I click on the Fx bypass checkbox in FCPX.However, I already have a parameter that's mapped to paramID 1 and I wouldn't be abgle to remap it without breaking compatibility with sessions saved with existing versions of our plugins.I also tried removing the mentioned parameter in order to retieve param 1's state as a BOOL via the FxParameterRetrievalAPI presuming it reflects the desired bypass state...without success, however, since getBoolValue:fromParm:atTime: always returns NO for that parameter.Any hints?Thank you!

I have created a custom parameter via the FxParameterCreationAPI and it shows up and works fine in motion.I'd like to expose that parameter to Final Cut Pro using a motion effect template but, I can't select the "Publish parameter" menu entry like it's the case with standard parameter types. The same also happens for the OptionsDialog example in the FxPlug SDK.Any hints on how I can achieve that?Thanks.Best,Ray