Hi ,
I have just upgraded to the new / Latest version of FCPX (10.6.6) and I am told that my plugins are NOT supported and that i must upgrade.
I am running the latest versions, can you help please ?
Rory
Hi Rory,
Thanks for reaching out to us about this. There are a few of things to be aware of with regard to Continuum and FCPX 10.6.6.
(1) In the latest version of FCPX (10.6.6) Apple dropped support for the Apple FxPlug 1 architecture
(2) The legacy BCC filters were built using Apple FxPlug 1 and will not run in FCPX 10.6.6 because Apple dropped support for that older API
(3) The newer BCC+ filters were built using Apple FxPlug 4 architecture and operate as expected in FCPX 10.6.6
So the takeaways are that the legacy BCC filters and transitions are not supported by Apple in FCPX 10.6.6 but all of the new BCC+ filters and transitions are indeed supported in FCPX 10.6.6.
I hope this helps explain the status of Continuum and FCPX 10.6.6.
Thanks,
Peter.
Hi Peter,
I’ve recently tried out the new Mocha Param Tracker with some of the BCC+ filters (eg BCC +Prism or BCC +Transform), but it won’t track or move at all. The tracker works fine inside the Mocha window, but fails to apply in the FCP timeline.
I am currently running macOS 13.4.1, FCP 10.6.6 and Continuum Version 2023.5 - 16.5.0.851.
Let me know if you need any additional information.
Thanks and best
Sam
Hi Sam,
Thank you for reaching out to me about this issue.
I’m currently using FCP 10.6.6 with Continuum 2023.5 (so the same as your setup) but on 13.1 Mac OS (so a couple of points behind your OS setup). With my setup, I’m unable to reproduce the problem that you’ve encountered so If possible, I’d like you to please try something for me.
Can you edit in a new HD clip into a new FCP project and then apply the BCC+ Lens Flare, then use the mocha parameter tracker to track the flare position across time. I’d like to know if you have any success with this before we dig deeper into the problem on your system.
Thanks,
Peter.
Peter,
I’ve tested this again in a new project and while the tracker seems fine, the flare will stay at its original position and won’t move/stay in position at all.
It’s a standard 1080p, 24fps project with a ProRes LT clip.
Let me know what else I can share to see what’s going on.
Thanks
Sam
Hi Sam,
Well I’m sure that must be a bit frustrating - thank you for your patience while we work through this.
I have an idea if you’re open to giving it a shot. I’ll import a clip, then use the parameter tracker in the Lens Flare to track the light source into the shot. I’ll send you the mocha file and the source shot. You’ll need to import and add the clip to the start of a new FCP project, then apply the BCC+ Lens Flare filter, open Mocha parameter tracker, select file>merge to import the Mocha data, scrub the mocha timeline to ensure that it’s tracking as expected, then apply back to the host and scrub to see if it’s still tracking correctly. Might you be open to trying that?
Thanks,
P.
Sure thing, let’s give this a try.
Thanks
Sam
Fantastic - thank you!
Here’s a link to the files : ParameterTrackerTesting.zip - Google Drive
Fingers crossed (and toes!).
Thanks,
P.
Unfortunately after I do the merge, the Position moves to a different location, but is not tracked and stays in a fixed position. The lens flare stays in its starting position within FCP as well.
Thanks for trying that, Sam. What strikes me as odd is that in the screenshot of the Mocha UI that you provided, the timeline after the merge is red but it should be blue so this indicates to me that there might be something off with the merge.
And you used this (screenshot below) to merge the data, right?
And if in Mocha you switch from the Essentials to the Classic mode, and click on the DopeSheet tab you should see all of the keyframes that are from the merge (screenshot below)
Thanks for having another look. Yes I’ve used the “merge project…” command from the toolbar. Looking at the DopeSheet it won’t show any keyframes.
Try twirling open the Effect Trackers group and then clicking on Position - this should reveal the keyframes, if they actually came through.
Hi Sam,
Hmmm … ok, well would you mind trying something else for me please? I’d like you to see if we can produce the correct result on your system using Resolve.
So, if you are ok with this, let’s import the shot into a Resolve timeline, then in the Color tab apply the BCC+ Lens Flare and merge in the tracking data. The result in Resolve should look like my screenshot. If this works then we know the problem is isolated to the FCP host, which will help us diagnose the problem.
If it also fails in Resolve then I think we will find that it’s a problem with the Mocha config.
Thanks,
P.
Peter,
it does work in Resolve, both in the Edit and Color page. So it seems isolated to FCP.
Best
Sam
Hi Sam,
I’m consulting with some of my colleagues on this mystery - hopefully they’ll have some suggestions for us to try.
And if you’re up for it, I can make available to you one of our internal builds of the BCC FxPlug (2023.5.1) software which has an update to the Apple SDK, which might resolve this for us. Would you be interested in trying this suggestion? It won’t cause any additional issues on your system and we can always downgrade to the current retail version if you need to.
Cheers,
P.
Sure, always happy to test and see if we can get to the bottom of this.
Cool … thanks for being open to that, Sam.
Thanks,
Peter.