In VideoEditor (in MSP7), I cannot open a movie project previously saved as a .DVP file. Trying to do so makes VideoEditor crash and brings up the "Please send a report to Microsoft" dialog. Can anyone tell me why? How do I save a partially completed project so I can work on it later. Thanks for any help.
Ted Compton
compton@ieee.org
MSP7: Opening a previous *.dvp file makes VideoEditor crash
-
videomartin
It seems you got a crash with video editor.
My last one with a crashed *.dvp i had 4 years ago.
Sometimes the Security option "Autosave" causes a crash, when at the same time some heavy work is done at the timeline (scrubbing or a preview is started).
Therefor i don't us AutoSave since years and save manually (CTRL-S).
In adition i use different *.dvp files f.e on a daily base in greater projects..
My last one with a crashed *.dvp i had 4 years ago.
Sometimes the Security option "Autosave" causes a crash, when at the same time some heavy work is done at the timeline (scrubbing or a preview is started).
Therefor i don't us AutoSave since years and save manually (CTRL-S).
In adition i use different *.dvp files f.e on a daily base in greater projects..
-
rtcompton
Thanks!
Thanks to everyone for your tips.
I have found that it is very easy to make Video Editor crash by using certain commands (see below). When that happens, I find that the *.dvp project file automatically gets trashed so it cannot be opened again. To avoid this problem, I have been making a backup copy of the project file after every "save", so that if Video Editor crashes I can still open the backup file. That seems to solve the problem but it is a nuisance to keep making backup files.
Here is an example of what makes Video Editor crash. In the top right panel (Production Library), when I choose "Audio Filters", click on the filter "Amplify" and then try to apply this filter to an audio clip, Video Editor always crashes. After the "Please tell Microsoft" dialog appears, Video Editor simply closes. When that happens, the project file cannot be opened again. Trying to open it just makes Video Editor crash again.
The only way I have found to avoid this problem is to make a backup copy of the project file before every edit.
I have found that it is very easy to make Video Editor crash by using certain commands (see below). When that happens, I find that the *.dvp project file automatically gets trashed so it cannot be opened again. To avoid this problem, I have been making a backup copy of the project file after every "save", so that if Video Editor crashes I can still open the backup file. That seems to solve the problem but it is a nuisance to keep making backup files.
Here is an example of what makes Video Editor crash. In the top right panel (Production Library), when I choose "Audio Filters", click on the filter "Amplify" and then try to apply this filter to an audio clip, Video Editor always crashes. After the "Please tell Microsoft" dialog appears, Video Editor simply closes. When that happens, the project file cannot be opened again. Trying to open it just makes Video Editor crash again.
The only way I have found to avoid this problem is to make a backup copy of the project file before every edit.
-
htchien
- Advisor
- Posts: 2013
- Joined: Sat Dec 11, 2004 12:10 pm
- System_Drive: C
- 32bit or 64bit: 64 Bit
- Location: Taipei, Taiwan
- Contact:
It seems some DirectX Audio Filter in your system is not compatible with MSP Video Editor. If you are using an purchased version of MSP7, please go to http://www.ulead.com/tech/msp/msp_ftp.htm to download and install the latest SP2 patch and then the problem should be fixed.
If it's not fixed, or you are using an trial version of MSP, you can manually change a setting to avoid the conflict. Check bellow setting to disable DirectX Audio Filter Manager in MSP:
Under system drive:\Documents and Settings\All Users\Application Data\Ulead Systems\Ulead MediaStudio Pro\7.0\msp.ini, change the setting to 1.
[DXAudMgr]
DisableDXAudio = 1
However, this will cause DirectX manager and its audio filters not to load into Production library of VE.
Hope this helps.
H.T.
If it's not fixed, or you are using an trial version of MSP, you can manually change a setting to avoid the conflict. Check bellow setting to disable DirectX Audio Filter Manager in MSP:
Under system drive:\Documents and Settings\All Users\Application Data\Ulead Systems\Ulead MediaStudio Pro\7.0\msp.ini, change the setting to 1.
[DXAudMgr]
DisableDXAudio = 1
However, this will cause DirectX manager and its audio filters not to load into Production library of VE.
Hope this helps.
H.T.
-
rtcompton
Additional comments
Thank you again for your comments.
I installed the SP2 upgrade again. (I had already installed SP2 once before, but I noticed that after the new install the version number changed.) After the most recent SP2 upgrade, I have MediaStudioPro Version 7.20.1006.
After that change, I no longer seem to have trouble with Audio Filters, but I am still having lots of trouble with unreadable project files.
The following problem frequently occurs. After an editing session with Video Editor in which everything seems to be working normally, I save the project file and close Video Editor. At a later time, I start Video Editor and try to reopen the saved project file. At this point Video Editor crashes with the "Send a notice to Microsoft" dialog. After the notice is sent, Video Editor simply closes. When Video Editor crashes, the error message is "The instruction at "0x73dd11c7" referenced memory at "0x00000004". The memory could not be "read".
When this happens, I can sometimes get my project back for further editing by using "Insert/Project..." to insert the old project, rather than using "Open". But many times that also does not work and I have to start the whole project over again. Very frustrating!
If anyone has any additional ideas, I would certainly appreciate them! I am ready to look for some other video editing software to use instead of Video Studio.
Thanks again.
Ted Compton
I installed the SP2 upgrade again. (I had already installed SP2 once before, but I noticed that after the new install the version number changed.) After the most recent SP2 upgrade, I have MediaStudioPro Version 7.20.1006.
After that change, I no longer seem to have trouble with Audio Filters, but I am still having lots of trouble with unreadable project files.
The following problem frequently occurs. After an editing session with Video Editor in which everything seems to be working normally, I save the project file and close Video Editor. At a later time, I start Video Editor and try to reopen the saved project file. At this point Video Editor crashes with the "Send a notice to Microsoft" dialog. After the notice is sent, Video Editor simply closes. When Video Editor crashes, the error message is "The instruction at "0x73dd11c7" referenced memory at "0x00000004". The memory could not be "read".
When this happens, I can sometimes get my project back for further editing by using "Insert/Project..." to insert the old project, rather than using "Open". But many times that also does not work and I have to start the whole project over again. Very frustrating!
If anyone has any additional ideas, I would certainly appreciate them! I am ready to look for some other video editing software to use instead of Video Studio.
Thanks again.
Ted Compton
-
htchien
- Advisor
- Posts: 2013
- Joined: Sat Dec 11, 2004 12:10 pm
- System_Drive: C
- 32bit or 64bit: 64 Bit
- Location: Taipei, Taiwan
- Contact:
Please use some RAM memory module checking tool to check if your RAM memory module in the system is OK and stable. Sometimes the project file will get corrupted when the RAM memory module has some stability problem.
Also defrag your hard disk about once a week, that would help to avoid the crash, too.
And please let us know how many RAM memory do you have in your system. Sometimes if the RAM memory is not much, the crash will also happen. Suggest to use 512MB RAM or higher for video editing.
Hope this helps.
H.T.
Also defrag your hard disk about once a week, that would help to avoid the crash, too.
And please let us know how many RAM memory do you have in your system. Sometimes if the RAM memory is not much, the crash will also happen. Suggest to use 512MB RAM or higher for video editing.
Hope this helps.
H.T.
-
rtcompton
VideoStudio -- can't open project file
Thanks for your suggestions about checking the RAM on my computer
for memory problems and about defraging the hard drive. I have
done both these things, but unfortunately they have not solved
the problem.
I used two different memory checking software programs, one obtained
from Microsoft and the other (Memtest86) I found with a search on Google.
Neither program found any problem with the memory.
Actually, I did not think the memory would be the problem, because I
have two identical computers here. Each is a 3.2 GHz Pentium 4 running
Windows XP professional, 2 GB of RAM and a 120 GB hard drive. Each
hard drive has about 60 GB of contiguous memory available. I have
exactly the same problem with VideoEditor when I run it on either
computer.
I am sort of out of ideas.
Thanks again.
Ted Compton.
for memory problems and about defraging the hard drive. I have
done both these things, but unfortunately they have not solved
the problem.
I used two different memory checking software programs, one obtained
from Microsoft and the other (Memtest86) I found with a search on Google.
Neither program found any problem with the memory.
Actually, I did not think the memory would be the problem, because I
have two identical computers here. Each is a 3.2 GHz Pentium 4 running
Windows XP professional, 2 GB of RAM and a 120 GB hard drive. Each
hard drive has about 60 GB of contiguous memory available. I have
exactly the same problem with VideoEditor when I run it on either
computer.
I am sort of out of ideas.
Thanks again.
Ted Compton.
-
videomartin
Ted,
if i can assume, that you have the XP SP2 already installed, you should have a look onto something like "Data Execution Prevention (DEP)", what Microsoft has included with SP2.
I only have links here to german "speaking" web sites which describes the prevention of XP SP2 after problems, but i'm shure under the above expression you will find a lot of hints at google or other fine Windows help sites.
There are 2 possible definition points for that functionality and white list entries for programs):
- boot.ini
- sytem options (Extended - Performance options)
To deactivate it for a test completely you shold have an entry alike:
/noexecute=AlwaysOff in your boot.ini (hidden write protected file in C:\)
instead of the actual entry /(NO)EXECUTE
This file can be edited with Nodepad.exe, when write protection is disabled.
Perhaps your problem will be catched on that way.
if i can assume, that you have the XP SP2 already installed, you should have a look onto something like "Data Execution Prevention (DEP)", what Microsoft has included with SP2.
I only have links here to german "speaking" web sites which describes the prevention of XP SP2 after problems, but i'm shure under the above expression you will find a lot of hints at google or other fine Windows help sites.
There are 2 possible definition points for that functionality and white list entries for programs):
- boot.ini
- sytem options (Extended - Performance options)
To deactivate it for a test completely you shold have an entry alike:
/noexecute=AlwaysOff in your boot.ini (hidden write protected file in C:\)
instead of the actual entry /(NO)EXECUTE
This file can be edited with Nodepad.exe, when write protection is disabled.
Perhaps your problem will be catched on that way.
-
rtcompton
Can't open *.dvp project files
Martin,
Please give the address of the German Web sites that describe this problem. (Ich spreach Deutsch. Das ist mir kein Problem.)
Vielen Dank.
Ted Compton
Please give the address of the German Web sites that describe this problem. (Ich spreach Deutsch. Das ist mir kein Problem.)
Vielen Dank.
Ted Compton
-
videomartin
Hi Ted,
here we go: This will link you direct to the required article.
http://www.wintotal.de/Tipps/Eintrag.ph ... 6&URBID=12
This is a real powerful site with tons of fine hints for most windows versions.
Viel Glück
here we go: This will link you direct to the required article.
http://www.wintotal.de/Tipps/Eintrag.ph ... 6&URBID=12
This is a real powerful site with tons of fine hints for most windows versions.
Viel Glück