[RESOLVED] Red Giant Magic Bullet Looks ceased to work after updating PP to 2014.1 !!!!

[Steve Brame]

I had also found out that FilmImpact plugins were preventing some Red Giant plugins from loading, and even narrowed it down to which specific FilmImpact plugins were causing it. I sent a support request to FilmImpact with the information, and they attempted to test with free versions of MBLooks and Colorista, but showed no incompatibility, and having heard of no one else having the issue, wrote it off as a machine specific problem. Clearing the plugin cache on startup had never solved the problem, only re-installing PPro hen all plugins would get me working again, but the issue would eventually reappear, sometimes a month or two afterward.

At any rate, it does seem to be an incompatibility between the two sets of plugins – now which one is to blame is something for those vendors to hash out, but neither seems interested.

Asus P6X58D Premium * Core i7 950 * 24GB RAM * nVidia GeForce GTX 770 * Windows 7 Premium 64bit * System Drive – WD Caviar Black 500GB * 2nd Drive(Pagefile, Previews) – WD Velociraptor 10K drive 600GB * Media Drive – 2TB RAID0 (4 – WD Caviar Black 500GB drive) * Matrox MX02 Mini * Adobe CC * QuickTime 7.7.5
——————————————-
“98% of all computer issues can be solved by simply pressing ‘F1’.”
Steve Brame
creative illusions Productions

[Morten Telling]

Have you tried uninstalling Filmimpact plugins and reinstalling the latest versions? It helped me…and now its working. I agree it is very frustrating to experience all these issues everytime Asobe comes with one of their frequent updates for Premiere. Everytime Magic Bullet plugins and others have issues – crashes Premiere Pro or goes black or something. It seems like these folks do not speak to each other at all…and try to solve issues BEFORE they ship a new update.

/Morten

[Steve Brame]

Yes, actually that had worked for me once. Then the problem crept back in at some point.

It was a little disconcerting when the folks at FilmImpact told me that they had downloaded a trial of Red Giant’s Color Suite to run their test with. This indicates that they had never tested compatibility with those plugins before they had released theirs. I guess there could be all sorts of cases explaining why a plugin vendor can’t be expected to determine compatibility, and of course there’s also the inevitable that they could simply blame the problem on another plugin – not theirs.

But in the end, we’re the ones to suffer.

Asus P6X58D Premium * Core i7 950 * 24GB RAM * nVidia GeForce GTX 770 * Windows 7 Premium 64bit * System Drive – WD Caviar Black 500GB * 2nd Drive(Pagefile, Previews) – WD Velociraptor 10K drive 600GB * Media Drive – 2TB RAID0 (4 – WD Caviar Black 500GB drive) * Matrox MX02 Mini * Adobe CC * QuickTime 7.7.5
——————————————-
“98% of all computer issues can be solved by simply pressing ‘F1’.”
Steve Brame
creative illusions Productions

[Jaap Boerhof]

Hi Folks,

This seems to solve the issue:

1. Open the Registry Editor (RegEdit.exe)
2. Find the “HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US” (‘en_US’ indicates your language, could be different for you)
3. Locate the problematic plugin in the list.
This plugin will likely have this attribute “Ignore”=dword:00000001”
4. Set it to “Ignore”=dword:00000000”
5. Restart Premiere.

I’ve noticed the issue may come back when either a new version of Premiere comes out or you reset the Plugin Loading Cache by holding Shift when launching Premiere Pro. So if the problem comes back on a frequent basis, you may want to setup a .Reg file (eg. “fix_it_for_me.reg”) that contains lines like this:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\Looks3_64.aex]

“Ignore”=dword:00000000

[HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US\Colorista_II_x64.aex]

“Ignore”=dword:00000000

The lines above will fix MB Looks and Colorista II. Of course you can add any plugin to this that is causing an issue not to be recognized.
To apply the fix just right click the file and select: “Merge”
It will set all the “Ignore” lines to values you want them to be and will definitely speed up the procedure.

This worked for me. I hope it works for you!

[Tom Edwards]

Jaap Boerhof’s fix worked for me.

[Donald Tong]

EASY SOLUTION

Just have to go Program file > Adobe > Common > Plug – ins > CS6 > MediaCore > and just copy any software to CC plug-in folder.

It works for me, tell me whether if this works for you as well.

[Michael Weinman]

Where did you place the the folder that you copied from your old Mac to your new Mac?
I’m trying to figure out where the misfire plugins live on my new install as red giant install didn’t create the same plugins folder in my library.
I put the folder there hoping it would read it but didn’t. So wondering where you place to get AE to read?

Thanks!

[Gene Weglarz]

Exported the “HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\8.0\PluginCache.64\en_US” branch. Opened the file and highlighted the Red Giant keys that weren’t showing up and replaced “Ignore”=dword:00000001 with “Ignore”=dword:00000000 for the selected text. Did this for all Red Giant plugins; Looks, Cosmo, Universe, etc. Then imported file back into registry and now they all show up.

G. Weglarz

MSI Intel I7 5960X 16 Core @ 4.4GHz; 32GB Ram;
NVidia GTX 780ti; 60TB storage; Four Asus 27\” monitors

Adobe CC 2015
Cinema 4D R16

[Oscar Obians]

Thank you so much. It worked. Had the same issue with magic bullet looks in premiere pro 2015.4 update.

[Ersagun Demirel]

This solution never gets older. You can always try when you have new version of program or plug-in