Has anyone else had problems starting the Video Editor after SP3 (or SP2) upgrades? I upgraded from 7.1 which was working fine to SP3 and now the edit wont start. Last thing it tries is Initialising Audio Filters. I uninstalled then tried SP2 and that has same problem.
My system is WinXP Pro SP2. All audio drivers are up to date. Audio is Creative Audigy.
Any help appreciated as I need to get the HD capability of SP3.
Thanks
Video Editor 7 wont start after SP3 upgrade
-
Terry Stetler
- Posts: 973
- Joined: Thu Mar 17, 2005 3:34 pm
- Location: Westland, Michigan USA
Some DirectX audio filters installed by other programs do not follow "the rules" and can stop MSPro 7.x in its tracks during startup.
Ulead's tried to patch MSPro to fix the problem with many of them, but with new ones coming out all the time it's an endless task.
All I can say is that I'm VERY picky about what hardware/software I install on my editing systems. I'm also very un-trusting of audio cards whose maker starts with "C"
Result: no such problems for years.
One possible workaround is to disable the ability to use DirectX audio filters. This is done by loading in the copy of MSP.INI found in
C:/Documents and Settings/All Users/Application Data/Ulead Systems/Ulead MediaStudio Pro/7.0/
Once MSP.INI is loaded into Notepad look for the entry;
[DXAudMgr]
DisableDXAudio=0
and change it to this;
[DXAudMgr]
DisableDXAudio = 1
This will make it so DirectX audio filter support is not initialized and therefore cannot be used, but it should get you going until further diagnosis can identify the culprit plugin.
Of course as of MSPro 7.2 there is support for Steinberg Cubase VST compatable audio plugins, and there are a ton of those available on the internet both commercially and from the open source community, so.....
Directions on creating the proper folder for VST plugin *.DLL's is in the last 2 service pack release notes. This link should get you started in building up your collection;
http://www.sounduser.com/software/vstplugs/p1.html
Just make sure you only use the ones for a PC since there are a ton of 'em for MAC's only.
I'd also not install them more than one at a time, starting up MSPro between each installation and checking the filter for expected functionality on a *.wav file before proceeding.
DON'T test audio filters on MP3 or WMA files. Those may be legal to use on the timeline but doing effects on them is not a good practice. Ick....
If the filter isn't working or doesn't meet your expectations then you can just delete it before moving on to the next one.
Ulead's tried to patch MSPro to fix the problem with many of them, but with new ones coming out all the time it's an endless task.
All I can say is that I'm VERY picky about what hardware/software I install on my editing systems. I'm also very un-trusting of audio cards whose maker starts with "C"
Result: no such problems for years.
One possible workaround is to disable the ability to use DirectX audio filters. This is done by loading in the copy of MSP.INI found in
C:/Documents and Settings/All Users/Application Data/Ulead Systems/Ulead MediaStudio Pro/7.0/
Once MSP.INI is loaded into Notepad look for the entry;
[DXAudMgr]
DisableDXAudio=0
and change it to this;
[DXAudMgr]
DisableDXAudio = 1
This will make it so DirectX audio filter support is not initialized and therefore cannot be used, but it should get you going until further diagnosis can identify the culprit plugin.
Of course as of MSPro 7.2 there is support for Steinberg Cubase VST compatable audio plugins, and there are a ton of those available on the internet both commercially and from the open source community, so.....
Directions on creating the proper folder for VST plugin *.DLL's is in the last 2 service pack release notes. This link should get you started in building up your collection;
http://www.sounduser.com/software/vstplugs/p1.html
Just make sure you only use the ones for a PC since there are a ton of 'em for MAC's only.
I'd also not install them more than one at a time, starting up MSPro between each installation and checking the filter for expected functionality on a *.wav file before proceeding.
DON'T test audio filters on MP3 or WMA files. Those may be legal to use on the timeline but doing effects on them is not a good practice. Ick....
If the filter isn't working or doesn't meet your expectations then you can just delete it before moving on to the next one.
Terry Stetler
-
zstylus