It can be very frustrating, when a program fails to launch. First, one cannot work in the program, but then it’s also difficult to troubleshoot, because you cannot get it to run. There can be various causes of failure to launch, but one culprit can be a plug-in getting in the way of the launching.
One type of "plug-in" that causes a crash/hang when loading is the VST. These are often from audio-editing programs, and appear as .dll's in most cases. When the Adobe program encounters the VST's that it finds on the system, it attempts to load them, even if they did not install with PrE. There is a very quick and tiny line of text on the Splash Screen, indicating which are being loaded. One has to watch very closely to see this text, and as it goes by quickly on a fast computer, can be tough to read. One idea is to set up your video camera and record the loading process, focused on the Splash Screen. Then, when the launch fails, just rewind that tape and shuttle through it, until the Splash Screen disappears. Go back one Frame and pause. What is the very last line in that text? It is likely that that is the problem - that, or maybe the next one - the one we have yet to see...
There are three things that happen with the VST's:
1.) The Adobe program loads them successfully and can use them.
2.) The Adobe program loads them successfully, but cannot use them. In PrPro, the user gets a one-time warning message to that effect. One only sees this message once.
3.) The Adobe program cannot load, nor can it use, the particular VST(s).
With PrPro, the program writes a "blacklist" of the ones that cause the crash. If one has many of these # 3 VST's, the blacklist grows, on every attempted launch, until all are on the blacklist. Then, the program can launch. It will take one launch attempt for each of the offending VST's. On a DAW with tons of VST's (especially the "instruments" VST's), this might mean 20-30 aborted launches, before all are blacklisted. I mention PrPro here, because I have no idea whether PrE does the same thing. Possibly, but I just do not know. I did not realize that PrPro did the automatic blacklist until recently. Most people would only try to launch a couple of times, and then give up.
If one knows which VST's are getting in the way, they could address those. Hence, reading that little text line might be very useful.
Here is a response from Adobe engineering, on how PrElements handles VST's:
1. How do we load it?
After the patch, we look into the folder where we install plug-ins and load all VST plug-ins that are found. Before the patch, we used to load VST plug-ins from the common plug-ins location as well.
2. How do we use it once loaded?
Once a plug-in is loaded, it is saved in the list of loaded plug-ins. We refer to this list to locate the module for all the plug-ins.
3. Can we ignore loading it?
Yes, If you open ~/Library/Preferences/, you will find the plist file for PRE 9. You can change the ‘Ignore’ to ‘1’ for any specific plug-in and it will be ignored from next time. You will need a plist editor for mac for this. On Windows as well you can modify “Ignore” field for any specific plugin from the registry.
4. Do we ignore it if they’re present in a different folder/drive?
We don’t ignore based on the location. We just load those plug-ins that are in our plug-ins folder. Before the patch, we used to load VST plug-ins from the common plug-ins location as well.
5. Do we keep an entry that we have loaded it?
The plist file in ~/Library/Preferences/ keeps the entry for all plug-ins that we have loaded at least once.
6. Is the VST handling same after Windows patch as well?
Yes, VST handling is same in windows after the patch (we ignore common plug-ins). The plist is replaced by the registry (PluginCache) in the registry
Hope that this helps,
Hi Bill, I did what you say, but in the number 3, you said to change the "Ignore" to "1, and all the plugins that I have in the plist have Ignore to 1 already, and Premiere Pro cs4 continues loading.
Do you know what's the problem?
That set of instructions came from Adobe Engineering, specifically for Premiere Elements, and PrPro CS 4 is a different program.
Are you on a PC, or on a Mac?
On a PC, many users have Moved their VST's (the ones that they do not want PrPro to load) to the Windows Desktop folder, as PrPro will not look there. Then, all they need to do is point say CubeBase to the Desktop folder. I have no idea how one might do that on a Mac, but others probably do.
I'm on a Mac. That's the problem.
I run PPro cs4 and when it is loading plugins it stops at a plugin called "WaveShell-VST 9.0.vst (it's an audio plugin, nothing to with Premiere). I don't know why it stops, but I have to wait a lot and it never goes on. I tried deleting all this plugin but it also tries to load it.
In the Premiere Pro Forum thread, one of the Adobe Staff members mentioned that that WaveShell VST was popping up a dialog screen, that was appearing behind his PrPro screen, but when he minimized PrPro, or moved it on the screen (cannot recall the exact operation now), he was able to access that WaveShell dialog, then got it to load properly.
Wish that I could help more,
Europe, Middle East and Africa