Vegas 12 crashing really annoying

Sparky874

Sparky874

Well-known member
Hello all. Just venting my frustration! I just had a great PC built just to run Vegas 12 and we used all the hardware the Sony site suggested we use for optimal performance. However! It's just crashing loads when I use the Titler Pro 2 tool, can't seem to cope with multli layer video tracks, just really disappointing. I may have to crack on with vegas 9 just to maintain my sanity. I have bags of ram (64mb!) and a spanking new gfx card, there shouldn't by any issues and yes I am using the lastest updated version. Come on Sony! :evil:
 
The usual recommendations are to disable GPU for rendering and set your Preview RAM to 200 MB.
BTW, if you're using a 600 series NVidia card, you won't see any performance boost as Sony has yet to update Vegas to take advantage of this series of card :(
Open a support ticket with NewBlue and see if they can help. They are on other forums and, unlike Sony, are generally quick to respond to user problems.

Mike
 
Thanks Mike, I am using a NVIDIA GeForce GTX 570 card with 64mb of RAM (system only built last week). I never have any issues with Vegas 9 just the later versions. The frustrating this is the Titler software is powerful but just crashes the system all the time. It's not just that though, suddenly Vegas doesn't like rendering out gfx clips with alpha channels either! Should I only keep the Preview RAM to 200mb even though I have heaps of extra RAM available? What happens if you increase this amount say to 1000? I'll see if I have the 'disable GPU for rendering' set as well. Thanks for taking the time to help. Sparky
 
Mike, I just tried as you suggested 'disable GPU for rendering' on a render that had been freezing and driving me crazy in Vegas 12 all day, and it rendered out first time after the change, so thank you! But why did disabling the GPU make such a difference - in laymans terms! Thanks, Sparky
 
Sparky874 said:
Mike, I just tried as you suggested 'disable GPU for rendering' on a render that had been freezing and driving me crazy in Vegas 12 all day, and it rendered out first time after the change, so thank you! But why did disabling the GPU make such a difference - in laymans terms! Thanks, Sparky
Click to expand...

This kind of stuff is really complicated under the hood, but in layman's terms: less to go wrong.

To make a loose analogy, compare it to an old car with automatic everything versus an old simple car.
The automatic car has tons of bells and whistles, motorized windows, computerized shifting for the transmission, but as those things age, so many weird malfunctions can occur. If the windows stop rolling down, is it because of a bad switch, burnt out motor or a blown fuse? If the car isn't shifting properly, is it because of a computer controller problem, or a bad transmission? The old simple mechanical car, with roll down windows and manual transmission has far less to go wrong, which is why they tend to last longer. Also, when something DOES go wrong, it's usually very easy to pinpoint the problem and fix it.

GPU acceleration is complicated. The idea is to have a spare processor to take some of the load off the CPU. However, each video card is different and although there are proposed standards, they sometimes have minor incompatibilities that can become major problems in the wrong situation. The question is, like the car analogy above, is it the GPU chipset? Or the driver controlling it? Or is it Vegas that isn't interfacing properly? Or all of the above? Disabling that acceleration means there are less steps involved and simplifies the process of rendering. It will likely be slower as a result, but it will be more robust.

I've personally found that whenever I have problems rendering from anything (after effects, premiere, vegas, etc), disabling GPU and/or multiprocessing almost always fixes it. At the cost of slower performance, however.
 
I need help with Titler Pro - it works for me BUT I get flashing of the center part of the screen both in Vegas Pro and after I have rendered. Any help would be appreciated. I have an ASUS with 10GB of ram. Nothing as sophisticated as I am reading about here.
 
I am running a test with NewBlue, they were VERY responsive to my questions re flashing titles. Back with results soon.
 
Sparky874 said:
Hello all. Just venting my frustration! I just had a great PC built just to run Vegas 12 and we used all the hardware the Sony site suggested we use for optimal performance. However! It's just crashing loads when I use the Titler Pro 2 tool, can't seem to cope with multli layer video tracks, just really disappointing. I may have to crack on with vegas 9 just to maintain my sanity. I have bags of ram (64mb!) and a spanking new gfx card, there shouldn't by any issues and yes I am using the lastest updated version. Come on Sony! :evil:
Click to expand...

Is 64mb of RAM a typo?
Pro 12 requirements are "4 GB RAM (8 GB recommended)" and "512 MB GPU memory" (bottom of page):
http://www.sonycreativesoftware.com/vegaspro

Windows alone needs 128MB at a bare minimum. If actually 64mb of RAM, of course it would be constantly crashing.

Or am I missing something with your post?
 
Vegas Pro 12 was so poor at handling .mov files that I finally learned to use Premiere CS6. I hope a new update comes fixes this soon, because I am getting used to the Premiere interface.
 
THis is sooo annoying. I can't edit anything anymore. Quicktimes, Red... the simplest edit just makes Vegas crash. This happens in a freshly formatted macbook pro and a PC workstation with plenty of ram and decent graphic card.
I even tried installing vegas in a friends computer to see what happened, but it crashes there too.
Interesting to mention that rendering projects is fine, it's only while editing when it crashes.
I dn't know what's changed, when I installed vegas 12 for the first time it used to work really well. These days it's just impossible to edit anything.
Anyone else experiencing this problems?
 
hmmm.. Just the opposite for me. I can edit fine. I have the newest version, Pro 12. I'm having a terrible time trying to render P2 .mfx to .mp4. I have tried both main concept and sony codex. I started off this morning getting .mp4 files just fine, then after about 4 files (5 - 10 mins each) it started saying the file was rendered ok, shows up with a length like 200k etc, but when try to open get a 'can't open file' error. I can see the 'length' listed on the earlier files but no length or any info about file in the 'properties' on the 'bad' files. I have tried deleting and reinstalling Vegas, moving all the files to different drives, rendering to different drives etc... Now, finally I got 2 .mp4 files in a row, using the Sony codex... So i didn't really make any changes, Vegas just decided to cooperate.... Any way, I too, am 'really annoyed'. I have 3 hours of MXF files that need to be transcoded to .mp4 for upload and am having fits...!
 
This is very disheartening to hear. Macgregor, installing it fresh on another machine should yield the same experience as when you first bought and installed it. I'm wondering, are you opening the same project on each machine that is failing? It could be something about that particular project that is causing Vegas to crash. Maybe a corrupted file or bad sfk or something. Or does it crash on anything you throw at it after a fresh install?
 
M. Gilden said:
This is very disheartening to hear. Macgregor, installing it fresh on another machine should yield the same experience as when you first bought and installed it. I'm wondering, are you opening the same project on each machine that is failing? It could be something about that particular project that is causing Vegas to crash. Maybe a corrupted file or bad sfk or something. Or does it crash on anything you throw at it after a fresh install?
Click to expand...

Nah, new projects, and very simple ones. Usually after a few seconds playing, Vegas freezes. With quicktime files, with red files... I don't understand this. The system is the same. Some conflict with an update?
I tried intalling other versions of vegas 12 (older versions of v12) but that didn't change anything.
 
macgregor said:
THis is sooo annoying. I can't edit anything anymore. Quicktimes, Red... the simplest edit just makes Vegas crash. This happens in a freshly formatted macbook pro and a PC workstation with plenty of ram and decent graphic card.
I even tried installing vegas in a friends computer to see what happened, but it crashes there too.
Interesting to mention that rendering projects is fine, it's only while editing when it crashes.
I dn't know what's changed, when I installed vegas 12 for the first time it used to work really well. These days it's just impossible to edit anything.
Anyone else experiencing this problems?
Click to expand...
hi Mac. I have very similar problems.,I just revert to vegas 9 now and only user v12 for certain things. It's a real shame as I had a machine built just for 12.
 
What OS are you using? My Windows 7 machine (3.5 years old) has remained rock solid running Vegas 12.
 
Guess what I'm doing. I formated the computer again. From scratch. And I've installed w7, quicktime and now vegas 12. ANd it works rock solid with the projects that used to crash.
So my plan is install one program at a time to see what's making vegas crash so much.
As I said, I enjoyed months of vegas 12 without any problems until I started geting the software to freeze or crash so often that it was impossible to work.
 
wow, I think I got it.
Vegas becomes unstable right after installing Davinci Resolve lite. wooooooooooooooooooooooooo
 
Interesting, more find outs: installing avid codecs 2.3.8 also makes vegas unstable.
Does anyone know if davinci resolve also installs the avid codecs package? because that could be the whole issue I'm experiencing here.
 
You must log in or register to reply here.
Back
Top