D-D-D-D-D Desperate rendering crashes.

[Screwball]

Using UVS 9 I have been trying to render and burn for months - literally. Perhaps one in twenty attempts is successful for rendering, and almost never in burning. After my last succesful render, I used Nero to burn - no problems at all. Now I just can't render, the video just stops after about one third. Now I know you will immediately blame Nero but I have COMPLETELY washed the computer of Nero simply because I know it can cause interaction problems. After rendering (someday), I will re-install to burn. Pre-Nero, I have always had this problem. I have followed the manual, I have used your very helpful advice including one members link of succesful rendering and burning, all to no avail. If I can render sometimes, the machine and programme are capable, using precisely the same settings, the other 19 won't render??? The following info may help reduce speculation.

1.67 Processor
608 Meg Ram
16 gb free on 30 gb Drive

I turn off everything not required before attempt
Defrag before attempt
Select Mpeg2 option
Have cleaned and re-installed UVS twice

Using Widows task manager, soon as the process starts it goes to 100% and the swap file uses 331 mgb

If I move the slider during editing to 1/2 way along it goes to 100% and hangs

VIdeo is a combination of uvs video clips and stills

I intended to give up totally using UVS and use Nero 6.6 but it was like driving a Lada after a Maserati, had nothing like the features with UVS.
This last letter is in the hope of some light at the end of the tunnel. I do not think anyone can help, but someone may just have the answer.

[Screwball]

I forgot to say that the video is 33 minutes duration

[Ron P.]

While you have been able to pull this off albeit very few times, most of your problem is with your system. Your trying to tow a crusie ship with a rowboat. It just isn't up to the task.

With 608 MB of RAM, how can you run WinXP with anything else? Add the mininum required to run WinXP to the minimum required to run VS, then other things to make them work together and you're coming up short.

Then you only have 16gig of free space on a 30 gig HDD. The total size of your drive is not enough to handle video editing. You need about 30 gig of free space.

Your video is 33 mins, if it were DV/AVI that would be about 8gig of space needed just to store the clip(s). You still need about 8 gig of additional free space so that VS can work on the file. However if you're using MPEG it requires less space. Even with that your system just doesn't fit the bill for video editing...

[Screwball]

Aplogies for my ignorance, but surely 608 is more than adequate ??? In a reply to a previous similar question, someone was running very successfully VSP on a laptop with XP, a lot less ram and a smaller processor (one of the resident experts here but I can'remember which one). His reply was some relief as it ruled out the possible problem of lack of power. But I must admit that this could explain the processor running at 100%. I have a second 160 gb empty drive. Would it help to run it from here without upgrading the whole machine i.e. is drivespace my biggest problem, or ram or processor? Thankyou for your time.

[jchunter]

IMO, you are computer-light in several areas. However, some users squeak by with less. If you have an empty 160GB hard drive is it installed? If so, you have a lot more than 16GB of free space. Configure the XP swap file on the big drive. Make sure DMA is enabled on all drives. Best performance is usually obtained by having XP and VS on one drive and the video files and project on the other.

I assume that your video source files are AVI(DV) and that you are trying to transcode your project to Mpeg2. Rendering (transcoding) is a compute-intensive operation and so the CPU will be 100% busy no matter how fast it is. Are you using SHARE/Create Video File with the DVD-compliant properties that are specified in the Recommended Procedure http://phpbb.ulead.com.tw/EN/viewtopic.php?t=27 ??? Please list the properties of the source video files as well as the property settings for the Mpeg2 output file.

To start debuging, try creating a SMALL test project with one or two short video clips from your project and see if that will transcode. If so, add a few more clips and stills and try again. etc.