I have a brand new OS install from scratch. I wiped out my HDD and started all over. I installed VS 9 and configured the system for this app ONLY. I am following the sticky on how to use VS 9 to a T.
When I am editing, I play/pause, play/pause, play/pause, etc on any clip. After about 3-4 times of this I get a "Ulead VideoStudio has encountered a problem and needs to close. We are sorry for the inconvenience." error.
Constantly. I have no other programs running, no screen savers, etc. Again, this is a brand new install. Anyone have any ideas?
TIA,
-Tom
VS 9 Program Error
Moderator: Ken Berry
-
Riker64
You really had to chime in with a cocky attitude? This is my first post here, what kind of other information is needed? My system config?
AMD XP 2400+ CPU
1.25 GB DDR RAM
3 - 120GB HDDs (1 OS, 1 DATA, 1 VIDEO CAPTURE)
8x DVD+RW Drive
Win XP Pro SP-1
Firewire capture from a Sony DV Camcorder
Registered/Downloaded version of VS 9
Anything else? NOTHING is running except VS 9. Nothing. Fresh install of OS and VS 9, and these errors come up always when play/pause clips during editing.
I knew I should have waited for a Service Pack for VS 9 before using it.
AMD XP 2400+ CPU
1.25 GB DDR RAM
3 - 120GB HDDs (1 OS, 1 DATA, 1 VIDEO CAPTURE)
8x DVD+RW Drive
Win XP Pro SP-1
Firewire capture from a Sony DV Camcorder
Registered/Downloaded version of VS 9
Anything else? NOTHING is running except VS 9. Nothing. Fresh install of OS and VS 9, and these errors come up always when play/pause clips during editing.
I knew I should have waited for a Service Pack for VS 9 before using it.
-
jchunter
Tom,
What are the properties of the video clips that you are editing? (Right mouse on a clip in VS and select Properties) Did you capture them? Are they from a digital or analog source?
VS8 used to display the symptoms that you describe because it had a serious memory leak during editing. I have not observed this behavior with VS9.
Are you editing Mpeg2 or AVI clips?
John
What are the properties of the video clips that you are editing? (Right mouse on a clip in VS and select Properties) Did you capture them? Are they from a digital or analog source?
VS8 used to display the symptoms that you describe because it had a serious memory leak during editing. I have not observed this behavior with VS9.
Are you editing Mpeg2 or AVI clips?
John
Last edited by jchunter on Fri Jul 29, 2005 4:15 am, edited 1 time in total.
-
THoff
Sorry, but sometimes I get tired of answering the same old questions over and over, and having to guess because the person asking the question left out virtuallyall of the relevant details.Riker64 wrote:You really had to chime in with a cocky attitude? This is my first post here, what kind of other information is needed? My system config?
Here is my advice: run Windows Update, and apply all available updates. There were tons of Windows fixes since SP1, including DV device enumeration problems, DirectShow DV decoding fixes, Firewire capture fixes, and others. Update to the latest WHQL-stamped video drivers. Run DXDIAG and make sure all the video tests pass.
-
heinz-oz
And another thing, I presume you have your HD formatted to NTFS, right? What are your project settings? Where do your temp files reside, on the system disk or on one of the others? Do you have, by any chance, the project settings limiting HD and memory use? Don't ask me why these choices are even there, because I cannot think of any valid reason why someone would want to choke his/her system by that means. However, these settings have presumably been set by some installations by default. Can't do any harm to check. If there are limitations set, just untick this option to ensure there are no limitations.
Where does your virtual memory live? System drive? Change it to another physical drive, preferably in its own partition, make that partition about 3 x your RAM in size. In Device manager, set your swap file to this partition, max/min settings identical at min 2 x RAM. This will ensure the swap file doesn't get fragmented. You need to keep a small swap file on the system disk to ensure that the OS can do a memory dump in case of a system error. I have mine set to 172MB.
Let's see how this and the other suggestions work.
Where does your virtual memory live? System drive? Change it to another physical drive, preferably in its own partition, make that partition about 3 x your RAM in size. In Device manager, set your swap file to this partition, max/min settings identical at min 2 x RAM. This will ensure the swap file doesn't get fragmented. You need to keep a small swap file on the system disk to ensure that the OS can do a memory dump in case of a system error. I have mine set to 172MB.
Let's see how this and the other suggestions work.
-
Riker64
-
Riker64
But I have noticed that I get this Program Error crash everytime I have ANY other program up when running VS 9 - even if it is just Windows Explorer.
Another problem I had was when compiling a movie to an AVI file. It would get to 99% and then crash with the resulting AVI being corrupt.
In my video I had a clip that had bad sound - I used a wireless mic and only one channel came in. When I took this bad clip out, the video compiled to AVI just fine. I thought I could work around it by using the Duplicate Channel feature in VS 9 but no luck. So much for that feature working as advertised.
-Tom
Another problem I had was when compiling a movie to an AVI file. It would get to 99% and then crash with the resulting AVI being corrupt.
In my video I had a clip that had bad sound - I used a wireless mic and only one channel came in. When I took this bad clip out, the video compiled to AVI just fine. I thought I could work around it by using the Duplicate Channel feature in VS 9 but no luck. So much for that feature working as advertised.
-Tom