Final Cut won't open because of Waves on Intel...

Question

Level 1

5 points

Final Cut won't open because of Waves on Intel...

Final Cut Express HD 3.5.1 (on 10.4.9) won't open because it tries to load a Waves plug in (which I deleted) and the Waves 5.9 Enabler comes authorization screen comes up. (Odd, since I deleted that too!!!)
I have deleted my waveshells and anything else having to do with Waves, and this still continues to happen.
This is on a 2G Intel Core Duo MacBook with 1.25G of RAM. I also have ProTools M-Powered installed, but not running. (The iLok is not inserted either.)

Anyone know what the deal is here? Is there a way to have Final Cut stop looking for something that isn't there? I am just trying to open the program, I'm not even opening a project - so it's not looking for things because of that...

Macbook (Core Duo), iMac (Core 2 Duo), PowerMac G5, Mac OS X (10.4.9), Pro Audio & Video Production, musician, educator

Posted on Apr 13, 2007 9:11 AM

Reply

Answer 1

eveaudio Author

Level 1

5 points

Apr 13, 2007 9:14 AM in response to eveaudio

I found the answer on the Waves site.... (duh...)

Waves does not support Final Cut Pro.
Go to HD > Library > Audio > Plug-ins > Components, and remove any Waveshell you may find there. This will allow FCP to launch without Waves plug-ins.

Reply

Answer 2

Apr 13, 2007 12:52 PM in response to eveaudio

I was working on a system for a client a few weeks ago that was primarily an audio workstation and had the Waves gold bundle installed. It finally did launch final cut, and in fact I could see and apply the filters, but it took over 45 minutes for FCP to launch, and several of the plugins required me to click OK, so I had to sit there and watch it as it loaded up.

I was reluctant to move the waves shell (the only file you need to move) fom the Library/Audio/Plugins/Components folder since it wasn't my system, but finally decided to do it so I could get some work done.

Also was teaching in a classroom where the waves bundle had been installed on the student computers. Some would launch, but a few could not launch FCP, not sure what the difference could have been, since these were identicla mahcines which are restored from identical images on a regular basis.

Reply