Ableton Forum

I cannot launch ableton live, every time i do i get a message that reads - "
maxplug:live 5.03 . unable to locate component-
this application has failed to start because commonvcph.dll was not found.reinstalling the application may fix this problem" or
"maxplug:live 5.03 . unable to locate component
this application has failed to start because commonnsp.dll was not found.reinstalling the application may fix this problem" . And it continues giving these type of messages as it scans for different vst's.
This all started yesterday when i was using ableton live i tried to select custom vst's in the preference view, and when live started to scan my vst folder it started giving me the above error messages.I then closed live and tried to reopen it later but every time the program launches it starts to scan for vst's and then gives me the error messages. I then uninstalled Ableton live and reinstalled it but still got the same results. I then installed the upgrade version 5.03 of Ableton live and still get the same error messages when i try to launch the program.Everytime i uninstall and reinstall the program it still remembers my previous settings and begans scanning for vst's when i launch it, i press ok to every message that comes up and then they stop but the program does'nt launch.

I have Windows xp, pentium 4, 2ghz processor, 512megabytes ram.
M- audio delta 66 soundcard

Try moving the problematic vsti / vsti out of the folder live is scanning. If you are not sure which one it is move them all out, then drop them back in one by one to isolate the problem.

Best of luck.

Thank You, your a genius! your reply led to the solution. I had several folders within my steinberg folder and when ableton live scanned for vst's, it not only scanned my vst folder but also the wavelab demo folder, the wavelab demo folder contained dll's that where'nt vst plugins but things that pertained to the functioning of wavelab, and these strange dll's caused live not to launch. Your a time and stress saver, Thanks!

No prob. Glad that worked for you.

welcome to the forums by the way.

Glad to be here and welcomed! And i see it pays to come!

sounddesigner wrote:Glad to be here and welcomed! And i see it pays to come!

that's what all the girls say!

smutek wrote:Try moving the problematic vsti / vsti out of the folder live is scanning. If you are not sure which one it is move them all out, then drop them back in one by one to isolate the problem.

Best of luck.

Yes ... Wavelab's plugs don't like running inside applications other than Wavelab (except for a few such as NaturalVerb which will run in Cubase SX).

It's kind of like the "plugins" inbuilt into Live (it would be nice to be able to run these outside of Ableton ... particularly Operator).

Sometimes Wavelab has issuses with other people's VSTi's. It seems Wavelab doesn't like scanning certain VSTi's on start up.

For this reason on my system I do not let Wavelab share my "VST plugins Global" folder on my system. Rather I create a separate "VST plugins Wavelab Compatible" folder and place plugins I know are Wavelab safe.

Cheers

jasefos