ASK & DISCUSS INDEX

8 years, 6 months ago - Alwyne Kennedy

I run Windows 10. Yesterday I upgraded my motherboard, RAM and my CPU, and it cost a pretty penny. MB Looks, along with almost all the other MB Suite effects, vanished from Premiere during the swap, which was the only issue arising from simply putting the SSD with my old OS and installed apps into my new system. Windows 10 handled the swap otherwise cleanly. I didn't have to do a thing, other than to later install some motherboard drivers.

But then I discovered that most of the MB Suite effects had vanished from Premiere (but not After Effects). Only Denoiser III remained.

Anyway, after a bit of head scratching and MB Suite re-installs, I finally got Looks and its Suite comrades to reappear. But when I compared its rendering speed with my old system's performance, it was actually slightly SLOWER when handling Looks. The whole point of upgrading was to get things working faster, but its slower in this case.

I then noticed that in Premiere, Looks shows as a 32 bit effect, even though the plugin is named _64 in the plugin folder.

Denoiser III, which isn't showing as a 32 bit effect on my system, does show a significant speed increase compared to my old rig.

Could someone look on their own system and see if, in Premiere, Looks shows as a 32 bit effect. Click on the effects tab in the Project panel and navigate to Looks - on the right there will be a 32 icon if its running as a 32 bit effect.

I'm using the very latest version of MB Suite, and the latest Premiere version. However, my first Looks purchase was years back, when it definitely was only 32 bit. I'm wondering if there isn't some weird throwback thing going on on my system, due to some lingering Registry entry? At least that would explain why, after spending over a grand on an upgrade, I have slower Looks performance.