1 person found this helpful
It could well be a program/driver conflict. Unfortunately, I could find no information on that driver from a Google search.
Aside from insuring that you've got the latest version of the driver, I'm not sure what to suggest. It might be worth temporarily disabling the driver (by changing its name to SaffireComp.old) to see if Premiere Elements will load then.
If it does, then you can decide which program is more important to you.
Exactly the same problem...but at least I'm happy to see I'm not alone and it's not my PC.. How is it possible that a brand new installation does not work at all? It seems that the working area is loading when hitting a new project, then it stop and nothing appears. I guess the problem is on the VST instruments dll I have in my HD since I also use DAW programs!! But why Premiere is loading files that are not relevant for this kind of software??
I have no solution, I need to choose a software for video editing and I thought this would be one of the best in this range...but if it does not work, I gonna remove it and try to install some other video editing sw from the competition....:-)
I like to think there is no competition, bb. Just the right tool for each job.
well..you're right, but if on the first instance the sw does not even load, I cannot have the pleasure of deciding if it's the tool for me...probably it is not so, because it cannot be installed side by side to my music sequencers...:-)
It seems that the way to do this is to temporarily rename my Audio .dll folder, for me this was the VST Plugins folder within Cubase. (BTW thanks for the advice, Steve - you mentioned renaming) and then when running PE, hold down <SHIFT> over the start-up screen (and keep it held during the new project selection and the initialisation screen) . This clears the cache of it list of available dll.s and so it scans again, obviously not finding the re-named folder. This list is now saved and will be untouched unless you run with <SHIFT> held down again.
After closing PE, it is safe to revert back to the original dll. folder name, and everything should run well after that.
However, I also agree that Premiere has no business poking around in my Audio Workstation files - why does it need these?