Is it possible that you need a higher power supply?
I can't render on my machine at the moment, or do anything that requires either the graphics card or computer to work hard. My older machine had a better power supply than the one in my current machine (soon to change) and this cured all rendering, graphics, and game playing problems.

Thanks for taking the time to offer help.
I have done as you suggest, set threads (my computer has hyper-threading) to 1 and 2, tried high and low RAM settings.
It doesn't always hang at 34% but usually between 26% and 38%.
The best result has been 51% when I set threads to 1 and Ram to 16mg. I have appled no special filters.
When I have monitored RAM usage the CPU has been working pretty hard - near 100%.
Still can't figure what could be happening.

Your running out of memory with those stills and pans/zooms.
Render 33 at a time to avi then substitute the rendered file on the timeline and delete the rendered stills and remove them from the project. You can reset the threads to 4 but keep the ram at 16 megs. You will notice as you progress the ram usage in Vegas decreases. I usually reboot to reset the paging file in XP between each render.

JJK

Just as a workaround (which I do not see recommended so far) you might like to render to DV AVI. This has the advantage that even if the render crashes you can load the partially completed AVI back onto the timeline and then continue rendering from that point.

JJK,,,, While this may be a solution... I would hope that Vegas is not really all THAT buggy that such an approach is necessary.

A properly architected program should be able to handle pretty much anything you through at it - and to properly manage the use of RAM. Even if you have 1000 stills on the timeline... they are not all needed (usually) all at the same time. Therefore the program should use them... and then discard them from memory when it needs to.

If that is NOT the way Vegas does it's thing.... then we have a big problem.

I agree 100%. I wish I didn't have to adapt work-arounds for large stills. I have noticed if the stills are kept around 500k that 450 to 500 can be dumped on the timeline no problem. Sometimes they approach 3000k
each which suck the life out of Vegas unless you have about 8 gig of ram. I try to keep mine about 1980k for future use as HDV and some pan/crop zoom. This is with jpg stills and don't know if it works the same with png. Try a one minute credit roll slow speed over a couple of these and things slow down to a crawl.

JJK

what size are the JPEGs you are using (dimensions)?

Thanks to everyone for responding and trying to help. This is the Forum working as it is intended.
To answer the question from Forum Admin the average size of the JPEGs is about 1Mg. I know I could have reduced the size of these files before importing the clips into Vegas, but I never had to before.
The suggested workaround of rendering about a third of the project at a time, to an AVI and placing that on the timeline, seems to work, and therefore solves the immediate problem. So thanks for that.
The question still remains why V5 renders without a hitch, but V6 falters. That is still a puzzle.

I got an alienware, and just got it to work the way I want it. Couple of problems I had in the past were the hard drive, my 'C' was bad, so it kept blue screening me during renders... eventually when i turned it on... and heat. do you have good ventellation? funny thing, i was rendering a clip when i was readin these posts, and almost got to the forumadmin when everything froze... what a ko-eenky-dinky. it was heat that froze me... heh.
put a couple of fans in front of the vents and restarted my render... worked like a charm.

hope this helps.

Hi All,

I have created a veg file that will consistently reproduce this problem (at least on my system). The relevant files can be found at:

ftp://ftp.soundscapemusic.com/pub/

The files you need are:
- Make 6b Hang.zip
- Number 5 is Alive.veg

The ZIP is about 10MB (the included jpg images are large). The purpose is to demonstrate/reproduce the 6b hanging bug. This project consistently hangs Vegas 6 on my machine.

For completeness, I have also made Vegas 5 version of the identical project, which renders without a hitch.

Unzip the files, and load the project into vegas 6. For interest sake, fire up the windows task manager and view the performance tab graphs.

Now start the render in Vegas 6. You will see the page file (PF Usage) climb as the render reaches each new image ... till eventually ... no more CPU activity. It has hung. On my system, that happens consistently about 58% into the render of this project. You may have to kill vegas via the process tab in windows task manager.

As you can see, there is nothing fancy in the project. No zooms, no pan crops, no effects. Just a simple straight through slide show of 10 (admittedly large) slides.

And has been mentioned before, this renders in Vegas 5 without a problem. So, load up my Vegas 5 example, and render it.

I'll be interested to see what results others obtain.

And Sony, any progress on this issue?

Thanks,
Regards Lance.
-----
Lance Lenehan
www.lannistoria.com

After all the feedback I have finally solved this issue for me at least.
The question had been raised about the size of the JPEGs I was using and they were large - 3 to 4 Mg files on average.
I decided to do the project again by resizing all the photos in Photoshop to around digital video size 720 x 540 (Pal), before importing them into Vegas.
I then recreated my 10 min project with Pans, zooms, and dissolves, and rendered it to an MPEG2 file.
This time it rendered without any problems at all.
So for anyone else out there with this issue may like to try this as a solution.

I'm getting render hangs with no still images involved.

There certainly seems to be a problem with Vegas 6.0 that was not there with 5.0.

My personal feeling is that enough time has elapsed since the release of 6.0 for this issue to be examined and resolved - anyone from Sony care to comment on the progress of a fix?