documentation/profes._minor&language=objc 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. 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
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |