Ive been using Vegas since version 1. I've found it the most intuitive and easiest by far. I've tried out Premiere and a few other of the main NLE's along the way but I agree with other posters here that their UI are much more complicated.

I've had only a few minor issues in the past decade. I've only lost files two times out of the thousands of projects I've done with Vegas. I've had a corrupt project once. Every time Vegas has crashed I've managed to open a backup. I have never lost more than a half an hour of work time. Usually it's pretty easy and quick to repeat that half an hour as well.

I run other programs on my laptop, plenty of them! My desktop however is not connected to the internet as is bare bones, only video and audio related programs. To me the experience has been identical on both machines in regards to Vegas crashing and general reliability. All in all I've found Vegas extremely stable throughout the years and have never considered changing to any other NLE.

This has changed though. Since Vegas came with a 64-bit version I've had trouble with all of them. First 64-bit version I tried was Vegas 10 (I upgraded from V8). It didn't work for me, red frames, not rendering etc. 32-bit was solid though. I always tried the latest 64-bit upgrades but same thing... So I've been using 32-bit happily.

Now with Vegas 12 I can't even open the program without it crashing 2 out of 3 times. It just doesn't work on my machines. They are out of date by now though. Dual core, 4GB memory etc. But I dont have a 32-bit version to rely on this time, wich is a good thing. I think it's about time Sony goes all in for 64-bit.

I will soon buy a new computer and will give V12 a trial run to see how it fares. But I am at the same time prepared to consider other NLE options. First time in a decade...

Sami

Sami... It comforts me that you describe exactly what I've been experiencing. In the beginning, before the 64 bit version, Vegas was much more stable.

John Cline said: 'Van, if you've been using Vegas for ten years then you must know the drill. With every new integer release of Vegas, there will be issues that were not caught in beta testing. (And it appears that they had more beta testers for this release then ever before.) Nevertheless, certain bugs simply don't manifest themselves until it is in widespread use. The first update usually squashes most of the more egregious bugs. I typically wait until the first update before I do any serious work (or complaining.) I In the meantime, I submit bug reports as necessary.'

It's a sad day when one has come to expect the first release of any software to be unusable. I refuse to be conditioned to accept this just because that's what's happened for the last 5 versions of Vegas. I expect better from Sony. We all should.

You talk like I'm encountering obscure, unrepeatable bugs. 15 seconds, repeatable, 1 person. I don't need thousands to find bugs with Vegas. Give me 10 full-time editors working on feature films and I'm confident I'll find you many issues of varying degrees with Vegas.

I complain on these forums because direct messages to those in charge at SCS have been largely ignored. They honestly feel that releasing software with known significant issues is acceptable because they plan to release a patch 2 months later. When complaining on these forums, I'm not looking for solutions, rather support from other users... in an effort to get Sony's attention and encourage them to change their 'QA' methods. Or probably more accurately, to vent... as SCS largely ignores this forum too.

Who here would rather have a solid first release a few months later than an unstable one with a few patches in the same timeframe? Do you guys like being unofficial beta testers for Sony?

The last mammoth thread started by Van had more than 150 posts. Can we break that record now?

:) If only some of those posts were by SCS employees saying: "Hey, you're right, we need to change our quality assurance methods. We'll do everything in our power to release the next version of Vegas when the active count in our bug database is in the dozens, not hundreds."

vkmast wrote: The last mammoth thread started by Van had more than 150 posts. Can we break that record now?

Sure, just post anything - i.e. about the weather - and you know who will within hours or even minutes continue his most enlightened crusade.

I'm really missing the good old "ignore" button :- )

Flame at will - I will not waste time to answer anyway :- )))

I use VEgas as a DAW and as far as video edit HD either from GH2 ( AVCHD ) or whatever clients provide when they do. Never had any problems.

I use Fusion for effects, titles and so on, so Vegas doesn't get much of a workout there.

Before you jump on that try to remember that neither AVID, nor FCP or Premiere do much or any of that. They use after effects or other compositing software for that.

None of these NLEs are really the right tool for that. The fact that you can do it in vegas is a bonus and if it crashes when you do too much of that, well still better than not being able to do it at all which is the case with other NLEs.

To sum it up. I can record audio and layer as many tracks as I need without slowing Vegas down. I can drop a few layers of HD video, cut, drop a couple of effects and it all works perfectly. If I need some serious compositing or keying I'd be pretty stupid to do it in Vegas when I have fusion on the same machine. Not that I think I'd crash Vegas, but Fusion is a much better tool for that.

VanLazarus; I wish I could think of a rebuttal, but I got nothing.

ritsmer... You want to ignore it all but still felt the need to belittle my concerns? The number of threads that I've started on this forum in the last 6 months is:.... wait for it..... 2.... and one of them was just asking for help with a Vegas problem... hardly an 'enlightened crusade'.

Thanks for your inaccurate and unconstructive comments. Looking forward to your non-response. :)

deusx.... I understand your logic. I'm learning After Effects and will be using it more and more for complex compositing.

But that's one thing I like about Vegas, I can do some pretty powerful compositing in it. There is always ineffeciency in using multiple programs for an edit, sometimes just a few more seconds wasted, but sometimes many more minutes wasted.

Software needs to do what it claims it can do without crashing and glitches. Should I assure clients I can do a job 100% well, when I know that I probably can't do 25% of what they ask for competantly?

Right now Sony touts Vegas (since 11) as supporting a wide range of GPUs. So far, for myself, it has supported neither of the ones I've owned (that they state are supported). This is not right. It's not honest.

But it seems most people on these forums have accepted this and some consider me irritating for expecting better from a software maker. Is integrity too much to ask for these days?

Just an update. Sony haven't come back to me with regards to time code in P2. (Very silent). I have sent them a short clip and a screen grab to shoiw them. My problem with the previous (vegas 11) projects which were crashing was solved by disabling the GPU. As soon as I did that the system allowed me to load the project and work with it.

But I do agree that us users (and I have used Vegas since Version 3, before Sony got involved, would like to have something which is technically stable and delivers what it promised, not silence from the suppliers when you send them bug problems.

Same problem here with 12.
I was using 10 (although I bought 11 as soon as it came out)
11 was always crashing, 10 seemed to be more stable and would work for 30 minutes at a time, always giving me the .dll error and the cuda error.
Today I made the mistake of following someones advice and tried running 10 in compatibility mode for W7Pro.
It disabled my ShuttleProv2 so I uninstalled Vegas 10 and reinstalled.
Well, after many tries, it won't register and can't use it.
Tried 11, crashed after 20 minutes.
Asked Sony for help, not holding my breath.
Made another mistake, upgraded to 12, thinking maybe they solved the crashing problem, since I had read many other people had the exact same problem.
Now it crashes every 15 minutes.
Have been working on a movie tetralogy and now everything went to a halt.
BTW, I was having the same problem before buying ShuttlePro v2.
Any suggestions? At least any idea why 10 won't register? I don't expect to get my money back for Vegas 12 but I need to get 10 to work so I can finish this 4 movies.
Any help will be greatly appreciated.

One more thing, Vegas is the ONLY software that crashes in my system. All others work great and constantly, and as you can see, I have a real fast computer and very stable computer.

Carlos, that's horrid.

Is your EVGA GEFORCE GTX 570 one of the SCS recommended cards to use with VP12?

Getting back to VP10, you've had this working? Yes? It was registered on this machine by SCS? How many times have you installed this "Serial" of VP10?

Not good.

Grazie

Multithreaded code? How does that work on an operating system that cannot truly do multithreading?Windows has been doing true multithreading since Windows 95, though Microsoft did not quite do it right until Windows NT. Before that (Windows 3.1 and earlier), it used cooperative multitasking, which meant that a poorly written application could hog the system and not allow other applications to do their work at the same time. But since Vegas does not run under those old versions of Windows, you can rest assured the underlying OS does true multithreading, and it does it well.

And yes, Windows can (and often does) open two or more applications at the same time, though that has nothing to do with multithreading because each application runs in a separate process. Multithreading is about multiple threads within the same process. Like apples and oranges, multiprocessing (running multiple applications) and multithreading (running different tasks within an application) are two completely different things.

I'm glad somebody took the time to explain it to me. Now I have to take back about 300 thousand swear words about Windows.
JJK

Well I have to admit that V12 has given me more trouble than any other version. Blue FX Pro Titler was freezing it; so I took the risk and used the check for update and installed it. Whether the update was meant for Vegas I don't know but you would think so since the update was done via the Pro Titler menu. V12 seems to be more stable with title work now.
But all sorts of other things like zooming right into frame level can freeze it. I have had the red screen and a host of other non logical operations cause a freeze. I expect the odd freeze with all media type software - it just seems to be the norm; but V12 is a real front runner in the freeze department.

I haven't listed any specifics because it doesn't appear to be any specific event that causes the problem. I am going to load the project in 11 and see how it works in it. I started the project in 11 so no problems with a retrograde file version.

Ah I just made some setting changes and as of yet no freeze with the bit that was constantly freezing. I'll see how it stands up to some more work - may have to eat some humble pie :(

Sorry but that is a ridiculous statement. I write software for a living and you don't tell your users to run your software exclusively. And disable ethernet, bluetooth, wireless, antivirius, etc.?? Gimme a break, that is just absurd. No software vendor expects that.

Vegas 12 was released before it was ready, that's the bottom line. Too many people (myself included) are having problems with standard configuations that should have been worked out during beta testing. Hopefully a patch is coming soon.

DavidMJ...

Glad that more programmers are speaking up about the absurd claim that some software (like Vegas) needs to be run exclusively on a system to NOT crash. Vegas is just coded poorly... Nothing more. And SCS refuses to spend the time to clean it up before releasing it.

Yes, a patch will be coming within a few weeks.... but don't hold your breath for it to solve your problems.... you might have to wait for a few patches (or 4 to 8 months).

I think they are doing the best they can with the budget (unkown to me) that they are working with. I would compare it to raising 750 kids on a two party income. Would probably need a Quantum Mechanics test facility to find all the entanglement deviations.
JJK

>> Even AVID will still recommend that you should have absolutely nothing running
>> on your workstation other than their NLE and/or protools

For the record, this is a bogus (from AVID, not deusx) requirement. A modern operating system, like all Windows versions based on NT (2000, XP, Vista, 7, 8) use hardware in conjunction with software to make sure software on the computer can not interfere with other software on the same computer. This means that Vegas, no matter how hard it tries, can not interfere with other software and other software can not interfere with Vegas. The only way they can interfere with each other is if they install device drivers (which most software does not).

This is in the "running" phase. Obviously software can interfere with other software during install (for example) by overwriting files belonging to the "other software". That would be malicious behavior though, and it is unlikely that Windows software post about 1998 does this.

The "only" way two pieces of software can interact in a bad way is if running them in parallel somehow creates a unique burden on your computer that exposes a hardware problem (such as bad memory chips). At least, this is the case if you are not running GPU rendering. Since using GPUs for additional work is relatively new, there is a small probability that two pieces of software can "step on each others toes" while playing with the GPU.

>> In short, if you are running anything while recording audio or editing video you aren't being serious about it

Since recording audio is time critical, I will give you that one, but this can again be "fixed" with the appropriate audio cards. Professional level cards do not rely as much on the main CPU to do their work and should not be (as) affected by running software. When editing, there is no technical reason not to run other software, and avoiding it will only improve stability on systems that have driver (unlikely) or hardware problems.

The reality is that you can not run a personal computer today without running a serious amount of additional software, software that is running constantly, just as a third-party application, but is keeping your system functional or optimized. There is no difference between this software and a browser or an anti-virus package. It's just software. Your NLE is not less (or more) affected by this than by Word or Power Point or Angry Birds (except for CPU usage).

So, while most NLE companies (and some others as well) still have these kinds of statements in their documents, they have not been true or relevant since Windows 98/ME.

I agree with you 100% Vegas 12 AGAIN IS NOT STABLE! I'm having the same problems! I've had Pro 12 Now for 2 weeks now and it crashes at least 30% of the time I'm using it. I've become a Ctrl+save junkie because if I don't I'm screwed! Again Sony has added some really cool new features...when they work! My computer has plenty of power and all that jazz, it's as usual a SONY PROBLEM!
And I too feel like a SUCKER again HOPING VEGAS will finally run properly, but NOPE! Still the SAME OL ISSUES!

What kind of system are you running? Because I'm having the same problems he is! And I know of a couple other people having the same!