Thanks for that OldSmoke - never noticed it before!

Although I've had some crashes since doing this, in the last few days, I've not had a single crash.

When I say this, I mean I removed all of my development environment, Microsoft Visual Studio, SQL Server Developer etc etc.

I then installed just Sony Vegas 12 Pro build 486.

When I need to do any development, I'll just create a virtual machine. Thinking this just now, I wonder how Sony Vegas Pro would perform if on a virtual machine with absolutely nothing else installed. It might however introduce a whole raft of hardware related issues, re the graphics card etc. Just a thought.

"VegasPro stopped being stable after release of 9.0e"

That is truth. That is fact. It's over. I'm learning another software now as I see the handwriting on the wall. I'll keep using Vegas 9.0 as long as I can but the beginning of forced migration is upon me. I bought 10,11 and 12 hoping for improvement.

What I learned is simple...hope is not a strategy.

Erik

NONE of my 32 bit plugs show up or work in 64bit VP12

afaik 32bit plugins don't work in 64bit. hence most 3rd party 32bit plugins have 64bit versions.

>>VegasPro stopped being stable after release of 9.0e<<

Nonsense.

Both 11 and 12 have worked without any problems whatsoever on my machines.

Do some research, buy the right hardware, install Vegas and that's it. Nothing else required. If you are having problems then it's either your hardware or you have some unnecessary garbage software interfering with Windows/Vegas.

The only thing that has changed since version 9 is that you have to be more careful about hardware ( and software on the same machine ) and it's been like that with all other NLEs since forever.
In the old days you could install Vegas on a toaster and it would have worked.

@ deusx - never worked on my amiga ;-(

To deusx: while your theory is nice to hear, IT is not fact and here is why:

1) Two users can have identical hardware, and nearly the same install pattern, and 10,11, and 12 will act differently 50% of the time between the systems.

2) A baseline system with particular drivers will not consistently work supporting 10, 11, and 12. Why, because the stability is affected by the install pattern and the drivers set for each combo.

3) Many more users are qaulifying frustrations with 10, 11, and 12 than any previously accepted stable release, such as VegasPro 7.0d or 8.0b, etc. These versions have proven to be the most problematic ever.

4) Take the install pattern of different builds such as v394 and v486, many users can achieve better stability by going backwards to v394. This is something that does not ordinarily happen in successive builds.

I am with deusx.

I have all version of Vegas since 7. I had 7 to 11 on the same machine and only changed the machine because my Q6600 has come of age and the motherboard was limited to 8GB. Never ever did I have an issue with hardware and all problems I had where related to drivers for the video card. VP12 394 as well 486 are both stable but 486 has the red preview window bug that forced me to go back to 394. I also have MS Office and lots of other software including 3D CAD on the same machine without any issue.

I also dare to say that Vegas works for the majority rather then the minority as Sony would be out of business already. Users that don't have an issue don't join the forum. I only joined with the de-interlace issue and the recent red preview window bug. The change from VP10 to VP11 was a major one for Vegas with the addition of GPU acceleration. Hardware is not equals hardware; graphic cards are not equal just because both have the same name/extension. I could have blamed software many times for not being stable but in the end I always found the problem to be in my system.

What strikes me about all these problems with v11 and 12, and I do sympathize, it is incredibly frustrating when a pro app like Vegas doesn't let you do your job, is how absolutely stable v11 and v12 have been on the several different systems I have installed it on. I have done several tests, just out of curiosity, based on all the complaints on this forum with my most complex edits, and I cannot get any of the problems that people are having. Now, I have had an issue with the GPU on and Preview set too high, I like my preview ram set to 4096 and with GPU on, I could crash v11 and 12. OK, I set preview to 0 or turn off gpu, never crashes. I don't find the argument that since Vegas offers GPU and Ram Preview that they should just work perfectly together at all times, to be persuasive, how long have we all been dealing with computer programs? I can't be THAT lucky or THAT smart to have all of the systems I've tried v11 or 12 on just work without a glitch. My unfounded hunch is that there has to be something common with these problems that we're failing to see, maybe a system report should include much more than just the basics, like someone's discovery of the logitech mouse software or wacom tablet problem, I wish I knew, I certainly don't think it's stupid people who don't know how to configure their systems, but something else is going on here, or I should be on my way to Vegas (Nevada).

32 bit plugins are automatically 'wrapped' to work in V12-64.

DX are not ;-(

geoff

My jaw drops when I read threads like this one. What on earth is going on here?

I know I'm repeating myself, but my desktop machine hosts my web server, all my office apps, my games, my TurboTax program (yeah, that time of year again), everything. It's up 24/7. AND it's my editing workstation, currently running V9 after years of faithful service with V7. What can I say? V9 is a champ, cleaning up a couple of quirks in V7, adding some really nice tricks like Elastique and smart rendering (from V8). NEVER seen a crash in either program. I edit mostly 60-90 minute HD stuff destined for DVD, the rest of the time audio for creating CDs. Lots of tracks, lots of color correction and tweaking. No Media Manager, no fancy titling. Single 24" screen. I don't use DVD-A either.

I'm not trying to rub salt in the wound here, just wondering how is it that things could have changed so much in just a couple of years? Was there a total rewrite of the code beginning with V10 or 11? Or am I just not pushing the program as hard as others?

Riredale, what exactly are you saying?

G

Single screen is a very stable way to run Vegas. That is what I understood from the post.

Eight people have identical systems.

Person's A, B, C, D, E, F, G and H start with no problems at all. After a while person A's system starts to crash and/or have other weird problems. The others are still doing fine. Person A has auto-updates enabled while the other person's do not.

Later on Person B starts having problems. Person B got some new and various video cameras plus a very high res still digital camera. The others are using consumer type HD cameras. Person B mixes various camera videos in the project with some being of a moderate bit rate and others being a high bit rate. Person B also adds some very high res stills on a track on the timeline.

Later on Person C buys a number of fancy add-on's. Person C starts having crashes and problems.

Even later Person D sets Vegas options for 'Thumbnails to show in video = All' while Person's E-H has it set as 'Head, Center, Tail'. Person D gets occasional crashes while Person's E-H do not.

There is a lot more but I think you all get the idea. Beyond the basic hardware and software there can be any number of whatever's a person has on their system that can cause many kinds of problems.

A long time ago I had a mix of cameras with various types of video's in my project. I always eventually had problems. Even without problems there was still the extra work trying to make some kind-of match between them. I now have 5 cameras that can record the same type of videos. So matching them is very easy. Even though multiple types of Video can be on the same time-line and/or project I noticed that Vegas does not always like that. Vegas does not always like very high bit rate videos and very large graphics.

I keep it as simple as possible. The lowest resolution and bit rate that really gets the job done. Higher is just a waste of time and resources! I use the 1440x1080 HQ setting on all of my Sony cameras. Yeah I can use the 1920x1080 full HD and a high bit rate but all it does is take a ton of time to load, build peaks and slows down the editing and rendering. The final result with full HD is better but not enough to justify it!!! The settings I use makes everything faster and much less crash prone. It has been a very long time since I had a Vegas crash or anything weird happen.

Another thought, I know how upset a person can get when things go wrong especially when there is a dead-line nagging at them. Coming to this forum and starting a thread while all upset and ranting away without any info on system specs or anything else will accomplish absolutely nothing! I ought to know, I did it myself in the past and got no-where!

Best thing to do is walk away for a bit, calm down and then give as much info as possible so we can all help.

Ok, that is my sermon for today. LOL!

PEACE!

Danny Fye
www.dannyfye.com/ccm

The excuses being given above remind me of the ones given for British automobiles and motorcycles in the 1960s.

Bob.

but british cars / bikes of the 60's WERE excuses and need none ;-)

@Myerz - This is the greatest thread I have ever read on here.

FYI, I have several custom built BEAST workstations... All stable except for the top of the line one that has the latest i7 6 core processor. The others have i7 4 core, top of the line. All EVGA GTX 570 cards. Sony just isn't keeping up, and they don't care.

I use V10 for most projects, but occasionally will try a project in 11 to see if I can run it with GPU enabled... Then it starts to crash and I am reminded why I am sticking with V10. Or I have to stablize something and keep wishing it was V10.

I would encourage you to learn CS6 instead of Final Cut. I am about to do the entire training course along with all of my staff. Moving over there in the hopes of being fully migrated by Summer. I am sick n tired of horrible tech support (non-existent really) and a second rate product.

Seriously sometimes it seems like people here are encouraging us to check our brains at the door...

"Im not having any problems, just run the 32bit version on Windows XP."
"Turn off GPU acceleration and put ram preview at 0."

Seriously...?? Turn off that new feature that we paid for, that works on other NLEs without constant crashes!

It blows my mind that people who have no problems with Vegas 10, 11, or 12, are on here preaching that all our problems are NOT because of bugs in the software! They live in a mystical world of lolly pops and fairy tales. Enjoy. Lucky for you.

Sometimes, I can get through a Vegas project with only a few problems (crashes), or there are others where I'm about to kill myself or throw the computer out the window.

I will always have a special place in my heart for Vegas, even with it's growing instability, and undoubtedly continue to use it for some time to come. But I just bought the Adobe Production Premium Suite CS6 and will use it on our next project.

I'm sure it's not perfect either, but hopefully, I'll actually be able to use my GPU and not get the avalanche of instability I sometimes get on projects in Vegas.

@flacnvinyl

I am using Vegas 12 build 394 with Windows 7 64 bit, driver 296.10, GPU=On and ram preview at 200.

It is rock solid on my system.

Grazie, sorry--I guess my rambling post wasn't very clear.

I was just wondering at what point Vegas became more tender. The older versions seem to be pretty much bulletproof. Perhaps there is/was some significant event in the Vegas development timeline that changed its behavior.

A complete guess - 3D?

I suspect the primary event was moving to 64 bit, and second and more devastating was introduction of GPU acceleration.

I have thought for some time (although I'm not smart enough to be able to provide proof) that one of the issues is the way RAM is delegated and released. I was having good stability until I started working on documentary projects and having temp timelines with over six hours of footage. Then crashes, media replacement and others became daily occurrences - always when doing something that I would associate with data being moved and RAM being refreshed - adding media, saving a project, moving the playhead to the far end of the timeline.

If a problem like this with RAM usage is occurring (and I think the fact that simply adjusting preview RAM has so many various impacts adds weight) each system may have its own particular "point of no return" where problems begin manifesting. It would explain why some problems can't be duplicated by users or SCS, and would explain why some claim to have no problems. I was one of those when my projects were just a bit smaller.