I thought I'd write over here as I hope that some of you guys will have experience with Color Finale 2.0
I bought the plugin the day it was released (long time CF 1.0 user) and quite frankly, I've been underwhelmed. Many problems, especially when using the Pro version with masking.
I was patiently waiting for the updates (so I had to stop using the feature I actually paid more money for: masks), and now am running 2.1.144 on Catalina and FCPX 10.4.8.
After starting using it on some of my projects FCPX started becoming laggy, crashing and render times take a very long time without having any other plugins on the project (no tracking or heavy animated titles etc).
I was wondering what could be wrong and really didn't want to point fingers (as I know troubleshooting is needed before doing this) but lately, when I am rendering a project, FCPX just crashes in the middle of the render and it clearly blames Color Finale.
Final Cut Pro quit unexpectedly while using the Color Finale Plugin
And this is all after trashing the preferences PRam resets, SMC resets etc etc.
Do you guys have any experiences to share? Any workarounds? There's definitely something wrong with CF2.0 from the set go, it doesn't play nicely even on a 16'' 2019 MacBook Pro with dedicated GPU.
If you have any optimization tips you could share that would be great. At this point, I am ready to give up using this altogether
Domscillator wrote: ...After starting using it on some of my projects FCPX started becoming laggy, crashing and render times take a very long time without having any other plugins on the project...when I am rendering a project, FCPX just crashes in the middle of the render and it clearly blames Color Finale.
Final Cut Pro quit unexpectedly while using the Color Finale Plugin...
You have already done some useful isolation steps by verifying it happens with no other effects or plugins. The Color Finale developer needs to fix this. A first step would be looking at the complete crash log. If instead of crashing it sometimes causes an FCPX hang, the procedure is using Activity Monitor to take a spin dump. Many developers have special debugging features built into their product which they can advise you on.
You can first do a few more troubleshooting procedures: Make sure you're not running the Chrome browser or any browser based on Chrome. Verify you aren't using HEVC material, else transcode it to proxy. Make sure background render is off, delete all render files and only render manually by selecting timeline clips and doing CTRL+R.
It is absolutely imperative that plugin developers use a robust testing strategy, since their code is running *inside* the FCPX address space. Any bug in their code can hang, crash, or cause a memory leak within FCPX.
This is one reason why I use as few plugins as possible. The concept of things like Color Finale 2 is good -- but only if the performance, reliability and support turnaround is top notch.
A bug in a narrow, specialized plugin like Imagenomic Portraiture for skin processing isn't that bad. You can remove it or switch to another product. But color correction is widely used and saturates your timeline. After making a commitment to a color grading plugin, if a serious bug is later found you are effectively shut down util you rework the entire timeline.
I just wanted to add that I'm getting this issue as well whenever I attempt to use Color FInale 2 with FCPX 10.4.8 on a iMac Pro. It hangs and I must force quit in order to continue working. I basically have to delete the plugin from any clip it's applied to in order to use FCPX. The developer told me this only happened on Mojave but when I upgraded to Catalina the problem continues.
truelife2 wrote: .. The developer told me this only happened on Mojave but when I upgraded to Catalina the problem continues.
Developers have the ability to debug this. They can examine crash logs, or send you a custom instrumented version of the product with additional debug code. They must take responsibility for their own code and aggressively pursue it.
I was getting a lot of crashes with CF 2 and some very strange thing happening randomly with masking. I do like the app but haven't the time to work out the bugs so switched grading to resolve. many less mouse clicks and very few crashes. Would still like to use CF for jobs but not a good idea for tight turn around work right now for me.
PO wrote: I was getting a lot of crashes with CF 2 and some very strange thing happening randomly with masking. I do like the app but haven't the time to work out the bugs so switched grading to resolve. many less mouse clicks and very few crashes. Would still like to use CF for jobs but not a good idea for tight turn around work right now for me.
Same here: lots of crashes with masking. I do like the plugin too but there's too much risk involved if you're tight with deadlines. And if you spend the money that this plugin costs, there are high chances you're a professional and don't have time to deal with crashes and various quirks. Unfortunately, for now, CF2 is not transparent enough neither when it comes to workflow nor stability. I hope this changes soon but I am also switching to DaVinci for now.
I'm a bit late going the conversation but just wanted to weigh-in quickly. I've been tearing my hair out for a month with FCPX crashing... Tried everything and finally got ride of CF2 and all is well. Very strange. I've not heard back yet from support but hopefully this is something that can be fixed.
Ultimately when plugin developers move their code to the FxPlug 4 framework, it will optionally enable running that in a separate "sandboxed" address space, and should not crash the host app (FCPX in this case). However the plugin code will still crash which will be disruptive. IOW the plugin functionality will probably freeze or malfunction but FCPX will stay up and you can do an orderly re-launch without risking data loss:
So FxPlug 4 will help contain the problem but there's no substitute for developers debugging and supporting their code. Ideally customers could provide a small, reproducible scenario, but if not possible there are plenty of ways for a developer to debug and fix things like this.
When plugin developers do not expeditiously investigate and fix their problems it taints the entire plugin ecosystem with a reputation for poor reliability and poor support. This makes customers less likely to purchase plugins -- from any vendor.
I will add that the developer did send me a beta of an upcoming release and that seems to have temporarily solved my crashes. It was constant prior to that, now FCPX still crashes, but due to graphics card issues and Catalina confusion.