- Posts: 49
- Thank you received: 4
3 Post Moderation Rule for New Boarders (25 Jan 2021)
New boarders will have their posts moderated - Don't worry if you cannot see your post immediately.
Third Party Products for FCP
NEAT disabling FCPX functions on older MacBookPro
05 May 2016 08:50 #76410
by Blackburn
NEAT disabling FCPX functions on older MacBookPro was created by Blackburn
Hi guys and gals,
I use a couple of MacBook Pros, an older a newer, doing my video editing.
The older Mac, 2010version/4GRam/OSX10.11.4 is slow of course, but now every time I apply NEATV4 to something then most functions of FCPX become grayed out/nonfunctioning. I have to use 'command Q' to quit and then restart FCPX to get everything working again.
Didn't have this issue to begin with, it started happening occasionally but now occurs every time.
Resetting to default prefs didn't help. I can't recall if the problem got worse after upgrading to El Capitan.
Otherwise, life is great!
I use a couple of MacBook Pros, an older a newer, doing my video editing.
The older Mac, 2010version/4GRam/OSX10.11.4 is slow of course, but now every time I apply NEATV4 to something then most functions of FCPX become grayed out/nonfunctioning. I have to use 'command Q' to quit and then restart FCPX to get everything working again.
Didn't have this issue to begin with, it started happening occasionally but now occurs every time.
Resetting to default prefs didn't help. I can't recall if the problem got worse after upgrading to El Capitan.
Otherwise, life is great!
Please Log in to join the conversation.
07 May 2016 14:31 #76470
by Blackburn
Replied by Blackburn on topic NEAT disabling FCPX functions on older MacBookPro
Funny thing happened yesterday, On the old MBP I tried applying Neat to a few segments and the problem (described above) did not occur. So I continued using Neat on lots of other stuff without any problem at all.
So maybe resetting to default prefs did work, albeit with a delay, because I can't think of anything else that might have fixed things.
So maybe resetting to default prefs did work, albeit with a delay, because I can't think of anything else that might have fixed things.
Please Log in to join the conversation.


