#COLORFINALE KEEPS CRASHING FINALCUTPROX HOW TO#
#COLORFINALE KEEPS CRASHING FINALCUTPROX SKIN#
#COLORFINALE KEEPS CRASHING FINALCUTPROX PRO#
#COLORFINALE KEEPS CRASHING FINALCUTPROX CODE#

So FxPlug 4 will help contain the problem but there's no substitute for developers debugging and supporting their code. 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: /documentation/profes._minor&language=objc

#COLORFINALE KEEPS CRASHING FINALCUTPROX CODE#

However the plugin code will still crash which will be disruptive. 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).

#COLORFINALE KEEPS CRASHING FINALCUTPROX HOW TO#

Apple has provided lots of info and tools about how to do this: /videos/play/wwdc2018/414/ It is the responsibility of the plugin developer to promptly debug and fix problems like this. I've not heard back yet from support but hopefully this is something that can be fixed. 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. But color correction is widely used and saturates your timeline. You can remove it or switch to another product.

#COLORFINALE KEEPS CRASHING FINALCUTPROX SKIN#

The concept of things like Color Finale 2 is good - but only if the performance, reliability and support turnaround is top notch.Ī bug in a narrow, specialized plugin like Imagenomic Portraiture for skin processing isn't that bad. This is one reason why I use as few plugins as possible. In the future this will hopefully be fixed as plugin vendors move their products to FxPlug 4 which can enable out-of-process plugins, thereby preventing a plugin bug from 'deranging' FCPX. Any bug in their code can hang, crash, or cause a memory leak within FCPX. It is absolutely imperative that plugin developers use a robust testing strategy, since their code is running *inside* the FCPX address space. Make sure background render is off, delete all render files and only render manually by selecting timeline clips and doing CTRL+R. Verify you aren't using HEVC material, else transcode it to proxy.

You can first do a few more troubleshooting procedures: Make sure you're not running the Chrome browser or any browser based on Chrome. Many developers have special debugging features built into their product which they can advise you on. If instead of crashing it sometimes causes an FCPX hang, the procedure is using Activity Monitor to take a spin dump. A first step would be looking at the complete crash log. The Color Finale developer needs to fix this. You have already done some useful isolation steps by verifying it happens with no other effects or plugins.

#COLORFINALE KEEPS CRASHING FINALCUTPROX PRO#

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.įinal Cut Pro quit unexpectedly while using the Color Finale Plugin. At this point, I am ready to give up using this altogether If you have any optimization tips you could share that would be great. 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.įinal Cut Pro quit unexpectedly while using the Color Finale PluginĪnd this is all after trashing the preferences PRam resets, SMC resets etc etc.ĭo 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. 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.Īfter 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). Many problems, especially when using the Pro version with masking. I bought the plugin the day it was released (long time CF 1.0 user) and quite frankly, I've been underwhelmed. I thought I'd write over here as I hope that some of you guys will have experience with Color Finale 2.0

Colorfinale keeps crashing finalcutprox