fbpx
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.

Plugin Disabled

More
24 Feb 2022 21:03 #119183 by noah.leon
Plugin Disabled was created by noah.leon
So I’ve recently been getting a lot of “The plugin X failed to respond and has been disabled.” Some of these are heavy-duty plugins, like Filmconvert Nitrate, or RX8 Denoise, so they sometimes do respond a little more slowly than lightweight plugins, but every time FCP disables a plugin, I have to restart FCP and try again. Is there a way to disable disabling plugins? Even if it means a slower system, I think Apple is much too agressive about disabling unresponsive plugins.

This didn’t used to happen with older versions of FCP so I wonder if they have changed how the program works to avoid hangs and slowdowns due to plugins.

Macbook Air M1, 16GB ram, etc.

Please Log in to join the conversation.

More
02 Mar 2022 10:26 #119225 by Betty Forest
Replied by Betty Forest on topic Plugin Disabled
Have you done an operating system upgrade recently? I'm just reading a post on Reddit and a guy writes that he had this problem after updating his OS and a customer service guy from a plugin company told him to roll back the changes or install a previous version.

Please Log in to join the conversation.

More
31 Mar 2022 17:28 #119734 by noah.leon
Replied by noah.leon on topic Plugin Disabled
I have the same issue.

Initially I thought it was a problem with Filmconvert, but I think I've discovered the real culprit.

When editing, rendering, or exporting certain codecs, h.265 (HEVC) for example causes either Kernel Task or VTDecoderXPCService to go crazy and use upwards of 60GB of swap memory (according to Avtivity Monitor). When this happens, FCP starts to disable your plugins.

The solution for me was to convert everything to Optimized media. This doesn't seem to happen when everything is in ProRes.

As to what happened, I have two theories that may both be true:

1: They put a hard limit on how much memory FCP is allowed to consume before it crashes plugins (and crashes renders)
2: It's a fundamental bug with VTDecoderXPCService which is what decodes certain codecs (especially h.265) and so it is an OS problem, which may or may not get fixed.

Either way, a pain.

Would you please let me know which codecs you are working with in your timeline? I'm very curious.

Please Log in to join the conversation.

More
10 Mar 2023 17:08 #124539 by visioncut
Replied by visioncut on topic Plugin Disabled
I encounter the same problem with an Fx Factory plugin from CrumplePop: AudioDenoise AI gets disconnected and I have to reinitiate FCPX.

For me is important to work in Proxies, because is a Documentary, so very heavy to work everything as optimized.

I reported it to Apple, because Fx Factory told me that is on their end.

If you find a solution, please let me know...

Thanks!

Please Log in to join the conversation.