VideoPaint is crashing with error code 131073:1:4 (Cannot read video) and then insufficient memory 13023:3:1. I have 512 Mb of RAM and XP swap file set to 1.5Gb. Latest MSPRO patch applied.
I have to rework a 27 MB video that I made months ago in WMF format. The project consists of removing some text information in a 5 minute segment.
After unsuccesfully trying some filters in Video Editor, I had to switch to VPaint. This is my first real project in that MSPRO module. Here is how I do it:
1. I select the area that need to be made unreadable
2. I use the Power Duplication tool and copy the selected area to all the frames that need to be affected
3. I select the preview range for the duration of the erase operation
4. I drag and drop the diffuse filter to the edit area and hit OK to start applying the filter.
The % completed status starts pretty fast, seems to use RAM in the beginning. After about 30 seconds, there are more and more disk accesses. Around 50% the process stops with the error messages mentionned above. At this point if I look at the XP Task Manager's Available physical memory it's close to 0.
Are there any tweaks available or is this a memory leak problem?
I am going to submit this problem to Ulead as well, but given their lack of response in the past I hope someone can help me here. Thank you.
Fred
I have to rework a 27 MB video that I made months ago in WMF format. The project consists of removing some text information in a 5 minute segment.
After unsuccesfully trying some filters in Video Editor, I had to switch to VPaint. This is my first real project in that MSPRO module. Here is how I do it:
1. I select the area that need to be made unreadable
2. I use the Power Duplication tool and copy the selected area to all the frames that need to be affected
3. I select the preview range for the duration of the erase operation
4. I drag and drop the diffuse filter to the edit area and hit OK to start applying the filter.
The % completed status starts pretty fast, seems to use RAM in the beginning. After about 30 seconds, there are more and more disk accesses. Around 50% the process stops with the error messages mentionned above. At this point if I look at the XP Task Manager's Available physical memory it's close to 0.
Are there any tweaks available or is this a memory leak problem?
I am going to submit this problem to Ulead as well, but given their lack of response in the past I hope someone can help me here. Thank you.
Fred
Comment