Hi there - I am using NotchLC to deliver final files for an upcoming event, as requested by the venue.
I’m running After Effects 2025.2.2 on an M2 Max Mac Studio (Sonoma 14.1).
It was working without issue for a few weeks, but after a standard restart, After Effects crashes on launch with the following error messages:
(first error):
After Effects warning: The following plugins have failed to load. Please reinstall these plugins:
/Library/Application Support/Adobe/Common/Plug-ins/7.0/ MediaCore/ NotchLCPremierePlugin.bundle
/Library/Application Support/Adobe/Common/Plug-ins/7.0/ MediaCore/ NotchLCAfterEffectsPlugin.bundle
(second error):
After Effects error: Couldn’t find main entry point for NotchLCAfterEffectsPlugin.bundle ( 48 :: 72 )
I’ve tried system restarts, reinstalling the plug-ins, resetting preferences - all to no avail. After Effects runs fine if I uninstall the AE and PR plugins.
Has anyone run into this before? Perhaps a known issue with a fix that I’m missing in the documentation? Otherwise I’ll consider this a bug report.
Let me know any other info I can give that’d be helpful to diagnose.
Thanks in advance.
Experiencing the same issue here. Running a MacBook Pro, 16" M3
Installed and tested NotchLC a few weeks ago and it worked great. Coming back to it now for an event need and getting these exact same errors. Deleting the plugin files from MediaCore and reinstalling does not work, same errors continue to pop up.
Looks like its some kind of an issue moving from AE2025 v22.1 to AE2025 v22.2. My team has rolled back and AE/Notch are back to working. Hopefully there will be an update/response in the near future, but in the meantime, hopefully this helps get you back up and running.
Adobe Creative Cloud 25.2 broke plugin functionality (and they did not inform developers of the changes ahead of time), stopping the NotchLC plugins from working.
The current solution is to downgrade / cross-grade (Adobe CC lets you keep multiple versions of apps installed at the same time). We are working on updating NotchLC but it is not as easy as one would think, due to the underlying changes from Adobe’s side.
Sorry you’re having this experience, I hope the workaround works for you (we’ve had nothing but positive reports that it does), and trust me when I say that we do get a lot of notifications about this and the only reply we can give is the one I gave earlier
