Vegas 6.0b hanging (crashing) all the time

[Dr. Dropout]

Re reducing the thread count to 1: this will make Vegas 6 tax the system similarly to Vegas 5 during rendering, and as such might help diagnose the render failure being reported. Maybe there’s a heat problem (just as an example) that gets exposed by using multiple render threads.

Render times and HT:

Hyperthreading is, as you know, very different from a true dual proc. HT is cool, there is some benefit, I run an HT system, but the future is (for both AMD and Intel) multicore, and it is with dual and multicore rigs that you’ll see the most benefits from the multithreaded rendering enhancements made to Vegas 6. We do have test projects that show render time improvements with HT… but true dual and especially multicore systems is where the threading changes really shine.

[Alan Reitano]

I am having the same exact problem…There are other people in Nashville TN having the same issue….From some test I have done…It seems that Vegas 6 is storing something in memory…I’ve looked at the memory usage during playback and every time Vegas 6 has crashed it had used all of the memory…I have 1 gig in my machine but have used vegas 5 on a laptop with 512meg for years and had not one single issue…

I have been using vegas since ver 3.0 and it has been rock solid…But 6.0 crashes regularly and reports from associates indicate even more problems than I’m having…

I have reverted to Version 5.o and it is rock solid on the same machine…Also it only uses about half of the memory during playback and about the same during rendering…

Vegas 6.0 seems to be more solid…(although still not comfortable) when all preview is turned off during rendering….

At first I did not believe that this was a Vegas issue…But I am convinced that smoething somewhere is using up memory faster than the machine can respond…When the memory is gone the machine crashes…

Any Suggestions?

Alan

[Chris Young]

Alan ~

No suggestions as yet. I have managed to get around the render problem in most case when I have set the ‘Dynamic RAM preview’ settings back to 16MB. Even set at this figure though there are massive memory consumption problems when rendering timelines with large 32 bit TGA files, i.e. 3000 x 3000 pixels. If you have say three or four layers of these all with ‘pan’ moves set in the pan and crop settings V6b just chokes up and then hangs. Funny one, because on V5d with the same jobs on the same machine and it just chugs on through with never a problem. Speed wise as yet I have seen no real improvement in V6 over V5 running on a P4 3.2 Gig machine. As Dr. D says we probably won’t see much render speed improvement until we move V6b to a dual proc or dual core CPU.

I can’t understand though how you can edit away in V5d using a high dynamic ram preview setting, of let’s say 1 Gig, and then render a timeline with nil problems and without having to change this setting. Try leaving a high dynamic ram preview setting in V6b, useful for your more complex longer previews, and then render. If we do this in V6b we know we are heading for disaster. It becomes an absolute memory hog and we know it is going to hang. Not very confidence inspiring!

I am by no means convinced that there isn’t some major memory/render issue with V6 and the sooner it is admitted and worked on the better. Trying to defend V6 and fend off the numerous posts around many forums re this issue is not what you expect from the likes of Sony, especially if they want more editors to consider it a ‘pro’ tool. Going on Sony’s past performance I think that this will be something that they will be looking at real soon… I hope!

Chris Young
CYV Productions
Sydney

[Chris Young]

Alan ~

No suggestions as yet. I have managed to get around the render problem in most case when I have set the ‘Dynamic RAM preview’ settings back to 16MB. Even set at this figure though there are massive memory consumption problems when rendering timelines with large 32 bit TGA files, i.e. 3000 x 3000 pixels. If you have say three or four layers of these all with ‘pan’ moves set in the pan and crop settings V6b just chokes up and then hangs. Funny one, because on V5d with the same jobs on the same machine and it just chugs on through with never a problem. Speed wise as yet I have seen no real improvement in V6 over V5 running on a P4 3.2 Gig machine. As Dr. D says we probably won’t see much render speed improvement until we move V6b to a dual proc or dual core CPU.

I can’t understand though how you can edit away in V5d using a high dynamic ram preview setting, of let’s say 1 Gig, and then render a timeline with nil problems and without having to change this setting. Try leaving a high dynamic ram preview setting in V6b, useful for your more complex longer previews, and then render. If we do this in V6b we know we are heading for disaster. It becomes an absolute memory hog and we know it is going to hang. Not very confidence inspiring!

I am by no means convinced that there isn’t some major memory/render issue with V6 and the sooner it is admitted and worked on the better. Trying to defend V6 and fend off the numerous posts around many forums re this issue is not what you expect from the likes of Sony, especially if they want more editors to consider it a ‘pro’ tool. Going on Sony’s past performance I think that this will be something that they will be looking at real soon… I hope!

Chris Young
CYV Productions
Sydney

[Chris Young]

Doh! Sorry ’bout the double post. Got a phone call and didn’t realise that I had already sent it after I hung up.

Chris Young
Sydney