VS10 keeps crashing, need system advice.
Moderator: Ken Berry
You can try re-installing, but chances are you've got a bad video file (or files) this time. Are you working with MPEGs or one of the other highly compressed formats?All of a sudden I am having very similar problems. I've been using VS10 since mid summer with success.... Suppose I'm looking for a re-install?
[size=92][i]Head over heels,
No time to think.
It's like the whole world's
Out of... sync.[/i]
- Head Over Heels, The Go-Gos.[/size]
No time to think.
It's like the whole world's
Out of... sync.[/i]
- Head Over Heels, The Go-Gos.[/size]
-
jchunter
Machineman,
Repeated crashing is highly abnormal for Video Studio 10+. It is a sign that there is something wrong in your computer. Have you checked your video card driver and installed the latest and greatest update? Have 20GB of free unfragmented hard drive space? When you reinstalled Video Studio, did you first manually eliminate all files and folders with "Ulead" in the file name after you uninstalled?
If VS was once stable and suddenly went south, did you install any codec packs or other video applications? Roxio? There are many possible sources of conflict. Have you tried Restoring your computer to it's state prior to the problem?
Repeated crashing is highly abnormal for Video Studio 10+. It is a sign that there is something wrong in your computer. Have you checked your video card driver and installed the latest and greatest update? Have 20GB of free unfragmented hard drive space? When you reinstalled Video Studio, did you first manually eliminate all files and folders with "Ulead" in the file name after you uninstalled?
If VS was once stable and suddenly went south, did you install any codec packs or other video applications? Roxio? There are many possible sources of conflict. Have you tried Restoring your computer to it's state prior to the problem?
-
Machineman
My VS10 was unstable from the start. I did all the recomended seggustions but no fix However I was able to fix it by changeing the playback method.
Go to Preferences: Change the play back method to "High Quality".
Since then I haven't had crashes while using the timeline. My camcorder is the Sony SR100 which was also targeted in the latest VS10 update SP1 which I haven't downloaded yet.
Go to Preferences: Change the play back method to "High Quality".
Since then I haven't had crashes while using the timeline. My camcorder is the Sony SR100 which was also targeted in the latest VS10 update SP1 which I haven't downloaded yet.
-
jchunter
MM,
Interesting workaround but you will never have the patience to wait for VS to render your whole project, just to see the playback.
If I were you I would document all this evidence and file a trouble report with Ulead Tech Support. If the info finds its way to somebody who can see the source code, it might help troubleshoot the problem.
BTW, do you have the CD or did you download VS10+? (possible corrupt dounload)
You are right to defer SP1 until this problem is solved.
Edit: To help troubleshoot, try making a new project with just one or a few video clips and nothing else. See if its stable to edit. If so, add a few more clips and some edits, see if its still stable. It is possible to have a corrupt video file that might cause this problem.
Also, you have never posted your video properties. Please do. It might help.
Interesting workaround but you will never have the patience to wait for VS to render your whole project, just to see the playback.
If I were you I would document all this evidence and file a trouble report with Ulead Tech Support. If the info finds its way to somebody who can see the source code, it might help troubleshoot the problem.
BTW, do you have the CD or did you download VS10+? (possible corrupt dounload)
You are right to defer SP1 until this problem is solved.
Edit: To help troubleshoot, try making a new project with just one or a few video clips and nothing else. See if its stable to edit. If so, add a few more clips and some edits, see if its still stable. It is possible to have a corrupt video file that might cause this problem.
Also, you have never posted your video properties. Please do. It might help.
Last edited by jchunter on Tue Sep 26, 2006 12:52 am, edited 1 time in total.
-
Machineman
I purchased the CD. Every time it crashed I selected to "send" the results to ulead. They probably have 40+ error logs from me.jchunter wrote:MM,
Interesting workaround but you will never have the patience to wait for VS to render your whole project, just to see the playback.
If I were you I would document all this evidence and file a trouble report with Ulead Tech Support. If the info finds its way to somebody who can see the source code, it might help troubleshoot the problem.
BTW, do you have the CD or did you download VS10+? (possible corrupt dounload)
You are right to defer SP1 until this problem is solved.
I only use the timeline playback to check small segments that i edited. Then smart render the entire project.
-
CycleWriter
- Posts: 203
- Joined: Mon Sep 18, 2006 11:25 pm
If you mean the Windows Report dialog box that opens when a program, any program, crashes, it does not send info to Ulead. That info goes to Microsift, which is exactly what happens to it. It gets sifted so fine that no one ever sees it.Machineman wrote:I purchased the CD. Every time it crashed I selected to "send" the results to ulead. They probably have 40+ error logs from me.
-
Machineman
I did not know that, good info.CycleWriter wrote:If you mean the Windows Report dialog box that opens when a program, any program, crashes, it does not send info to Ulead. That info goes to Microsift, which is exactly what happens to it. It gets sifted so fine that no one ever sees it.Machineman wrote:I purchased the CD. Every time it crashed I selected to "send" the results to ulead. They probably have 40+ error logs from me.
-
heinz-oz
Well, we have been waiting for a long time now to find out what your source file properties are or what the duration of your videos is. I think you have a highly compressed source file and your system chokes in the transcoding. The whole thing could be due to a faulty memory stick or other hardware issues.
We will keep going in circles (well, I won't) if we do not get the necessary basic information from you.
We will keep going in circles (well, I won't) if we do not get the necessary basic information from you.
-
CycleWriter
- Posts: 203
- Joined: Mon Sep 18, 2006 11:25 pm
This is my observation since upgrading to VS10+, as well. Perhaps one of the esteemed experts in here can tell me how to fix this problem. Mind you, this is a clean install and I have not yet made any changes to the program (I haven't gotten past this hang problem yet). I start the program and click on Capture at the top of the screen. The capture workspace opens and I then click on the Capture button. A dialog box opens saying "Changing Field Order" at which point it progresses to 50% and hangs requiring a 3-finger salute to close. I have yet been able to get past this point and until I do I can't even select a capture source so I am baffled as to why this happens. At least Ver. 8 will let me get around the program without crashing.Machineman wrote:My VS10 was unstable from the start.
Any ideas, gurus?
-
Machineman
Source files parameters (HDD Sony DCR-SR100 camcorder):heinz-oz wrote:Well, we have been waiting for a long time now to find out what your source file properties are or what the duration of your videos is. I think you have a highly compressed source file and your system chokes in the transcoding. The whole thing could be due to a faulty memory stick or other hardware issues.
We will keep going in circles (well, I won't) if we do not get the necessary basic information from you.
MPEG2 VBR 9100Kbs, 16:9, 720x480
Upper Field, 24bits, 29.97 frame/sec
Audio: Dolby 48Khz, 5.1channel, 448Kbs
I make my project properties the same and do a smart render.
The number of mpegs insterted or duration of project didn't seem to matter. I did tests with only a few source mpegs at <2min long and it still would crash. My typical projects have 60+ Mpegs with total dration 30+min.
It is possible that the SP1 update may solve the issue. Haven't tested it yet.
- Ken Berry
- Site Admin
- Posts: 22481
- Joined: Fri Dec 10, 2004 9:36 pm
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: Gigabyte B550M DS3H AC
- processor: AMD Ryzen 9 5900X
- ram: 32 GB DDR4
- Video Card: AMD RX 6600 XT
- Hard_Drive_Capacity: 1 TB SSD + 2 TB HDD
- Monitor/Display Make & Model: Kogan 32" 4K 3840 x 2160
- Corel programs: VS2022; PSP2023; DRAW2021; Painter 2022
- Location: Levin, New Zealand
The bitrate might be just a bit high for VS to swallow. While technically speaking VS can get above 9000 kbps, its own highest quality setting (and it produces excellent quality) is 8000 kbps.
So on the one hand, you could be having the crashes because VS just doesn't like this little extra over the top. On the other hand, of course, were you to lower the bitrate, this would entail a re-encoding of your video. There is a considerable debate, of which you may be aware, as to whether you should edit and/or re-encode mpeg-2. Some say it should not be done at all. Others argue that if you keep the quality high and minimise any other editing, you can re-encode several times without any degradation visible to the naked eye.
I might add that if you are producing a DVD with a max bitrate, even VBR, at over 9000, some (a lot?) stand-alone DVD players may also baulk at those higher rates and you might as a result get jerky, erratic playback or a complete halt...
So on the one hand, you could be having the crashes because VS just doesn't like this little extra over the top. On the other hand, of course, were you to lower the bitrate, this would entail a re-encoding of your video. There is a considerable debate, of which you may be aware, as to whether you should edit and/or re-encode mpeg-2. Some say it should not be done at all. Others argue that if you keep the quality high and minimise any other editing, you can re-encode several times without any degradation visible to the naked eye.
I might add that if you are producing a DVD with a max bitrate, even VBR, at over 9000, some (a lot?) stand-alone DVD players may also baulk at those higher rates and you might as a result get jerky, erratic playback or a complete halt...
Ken Berry
-
Sadie
I don't know if this is relevant to any of the issues mentioned here, but I just recovered from an episode of the program crashing each and every time I tried to save it. It would crash somewhere in the middle of the save.
I found out that it was due to one little clip I was using (when the save process reached that clip, that's when it would crash). The clip was an avi, but originally it was an .flv file that I converted to .avi using Riva encoder. For some reason, the program didn't like that clip and crashed every time it hit it.
What I did was open Windows Movie Maker and save the clip as a .wma file. I took the original .avi file out of my project, and just replaced it with the .wma file of the same clip that I made in WMM. Worked fine, and now saving is not a problem.
I found out that it was due to one little clip I was using (when the save process reached that clip, that's when it would crash). The clip was an avi, but originally it was an .flv file that I converted to .avi using Riva encoder. For some reason, the program didn't like that clip and crashed every time it hit it.
What I did was open Windows Movie Maker and save the clip as a .wma file. I took the original .avi file out of my project, and just replaced it with the .wma file of the same clip that I made in WMM. Worked fine, and now saving is not a problem.
-
The Star Treker
Machineman, I have the same problem. I got the same error signature you gotten. It crashes when I'm working in the timeline. It crashes before I add any video clips. I uninstalled and reinstalled it but it still crashes. I also closed all the other programs in the background, anti-virus, firewall, and etc. but it still crashes. I ordered the full version from element 5 but I'm not sure if it caused part of it or not. I have a Sony VAIO PC Windows XP Media Edition 2005 with Intel Pentium 4 CPU 3.40GHz 3.39GHz, 2.00GB of RAM.
