Agreed very bad fopr crashing, I think the worst version of Vegas ever. I had a 52 minute project that crashed every time about 3/5 of the way thorough. I had to split into two and then render each piece and recombine it later which is complete and utter HORSE HOCKEY. I am getting real upset with how unreliable this software is, it better get fixed really really quickly.

This current build is doing really well for me, the last build was dying sometimes every minute with footage from camtasia. Unfortunately I'm not able to say that I never get a crash, but gladly (for me) I have been very stable for all the things I use Vegas for this latest build... so far at least :).

Dave

I, too, am doing quite well with Vegas Pro 12. I use a dual monitor set up with full screen preview on one monitor. It works great with Vegas, and not too bad with Boris Red. Multi-cam edits also work fine. Rendering DV or HDV to a Blu-Ray file works flawless, but if I try to render to a 720x480 ws (16x9) file (.mpg2 or .avi) I must turn off the GPU first or I crash during the render. Those files render fairly fast anyhow. The tougher 1920x1080 & 1440 x 1080 files work with the GPU with no problems. Also, if I do a standard DV project (720x480 at 4:3 aspect in & out) I have no problems & a 90 minute project renders in about 32 minutes (that's fast). This is using an ATI Radeon 6870 with 1 gig of ddr5 RAM, on a Dell Studio XPS motherboard with an i7 processor & 16gig of ddr3 RAM.
Only problems come when attempting a render from 1080 anything to DVD widescreen file or any 720x480 at a 16:9 aspect.

12 is a mess on my system....crashes with New Blue titler, crashes when trying to do a simple 30 sec MOV render (crashes at 12 percent every time) Was crashing trying to open a project (seems related to it trying to ingest MXF files, Does odd things when going back and forth between the desktop and vegas (desktop visable thru vegas window frames, various functions take a very long time to execute. Will be working back in 11 until Sony tries another revision.

Cant even use with the GPU accel on......slows all the functions, preview, render, etc to a crawl...

11 worked fine, (fine being relative in Vegas land) so dont blame this on my system...

I am having major issues with Vegas Pro 12. Crashing so often I feel like I am in a demolition Derby.
Yesterday I tried to render a short (06:20) video to an *.MP4 file, it crashed every time at the end of the render.
I work with interlaced P2 footage and am finding that if I want smooth motion, I cannot rely on the Sony P2 codec to do a decent job, I am taking all my material back into Vegas Pro 11 and rendering that there, the DV Film codecs seem to be more reliable.
Vegas 12 doesn't read the P2 timecode.
Without a doubt, this is the most dissapointing version of Vegas I have ever encountered and I have been using it since Sonic Foundry days (Version 3).
When I started discovering these defects (Very quickly), the first thing I did was turn off GPU accelleration (WHich helped a bit) and I opened Ver 12 and 11 side by side and did a cut and paste of the work from Version 12 into the timeline of version 11, to enable me to render things without bad interfield jitter.
What I suspect is that Sony concentrated on the NTSC versions of the codec and us guys who use PAL can just suffer.
And the worst part is Sony don't seem to have their eye on the ball. For a company which is a leading broadcast supplier (And I have Betacam/Digibeta editing and Sony Betacam Cameras here also), they are doing a fine job of what we call, "Crapping on the rug!".

My crashing has stopped almost completely (one crash yesterday during 8 hours of editing).

I followed a suggestion, I think by Laurence, to set RAM preview to 0. That did the trick. I even have GPU acceration turned on. It means that on the rare occasion that I want to preview something at full resolution, I render that short segment to a new track (under Tools menu). SCS needs to fix the RAM preview bug, but at least I'm able to edit productively.

Thanks to Laurence.

> "I followed a suggestion, I think by Laurence, to set RAM preview to 0. That did the trick."

You know... I hadn't needed more RAM preview since I installed Vegas Pro 12.0 so mine was set to the default, but I usually keep it at 1024. I changed it to 1024 and had 3 crashes within the next hour. I changed it back to the default (200) and I edited for another 3 hrs without any crashes.

Laurence you are definitely on to something there.

~jr