Vegas 8.0b on quadcore does not close/save files
 

I am running Vegas 8.0b on a a brandnew Intel quadcore PC. Here is my problem:

When I try to save an open Vegas file (after changes), the progress bar (left bottom corner) remains 100% but ... nothing happens, the file does not save or close, I have to reset the PC. Never had that problem on my old single core PC. Any help is VERY MUCH appreciated. Thanks a lot in advance.

There must be something else going on as many of us are using quad-core machines with Vegas and it is saving projects. Any other clues as to what might be happening? Does it save nothing at all? or is the project corrupted afterwards? What if you do a Save - As? etc...

It's highly unlikely that it's the processor causing the problem.

Are you running Vista on the new computer?

I am running XP. The project seems not corrupted afterwards (after PC reset, that is), it just has not saved the changes I made.

As has been said, MANY of us are using quad-cores, so dont' worry about that.

Regardless, your problem sounds exasperating...as a temporary fix, try SAVING AS instead of just regular saving. This should be a good workaround.

As Edward suggested, Saving As instead of just hitting the save button also saves the project as if it were new, and avoids .veg corruption issues, especially with complex projects. I personally NEVER use just the save button, it's just a habit I've gotten into after a few issues with veg corruption a couple of years ago.

If that doesn't work, try saving to another hard drive or at least to another folder or your desktop, just to see what happens.

Thanks, Jeff, Edward and Robert, I'll try "saving as".

"Saving as" instead of save seems to work. Thanks a lot.
But there is another thing that disappoints me with my new quadcore - the render speed when rendering nested projects (two vegas files in one vegas master file). Not faster than on my old single core, vegas 8.0b only takes 25% (average) of the CPU power. Is this normal?

I don't routinely use nested projects. However, I can see how they might be limited to one core to render. I've never rendered a nested project and watched to see how much of each core was being used.

Yes, next time I try to avoid nesting projects as well. Render speed in a single project is way faster.

I seem to recall reading here at one time or another that nested projects do render more slowly.