Kimberly,

It seems from my reading that people running 64bit seem to be the bulk of ones having major problems. I am running 32bit windows and Vegas and only have the closing error you mentioned every once in a while.

On the closing I found if I use the EXIT from the file menu as opposed to the X to close, the error does not seem to happen. Only anecdotal though.

Dave T2

Does Sony even read the 'error' reports we send in?

Probably. Maybe over morning coffee.

Do you have a Wacom tablet installed? Or something equivalent?

Things to try off the top of my head:
-- Unplug and uninstall Wacom tablet
-- Run Vegas in Compatibility mode. This also seems to deal with the Wacom tablet issue.
-- Update your graphics driver to the latest version (or back up to a previously known good version based on feedback from anyone on this forum who has an opinion on which nvidia driver works)

These seem to be the approaches du jour.

Regarding Wacom/Compatibility mode...for me this issue manifested in a crash while adjusting OFX effects. Uninstalling the tablet driver or running Vegas in compatibility mode calmed that particular type of crash.

Rob

What do you have your Dynamic Ram Preview (DRP) set to? Is it higher than 2048? I was experiencing the same issues you seem to be having and found that since I set my DRP to 2048 or less the crashing has stopped.
Try changing it and let us know if it helps. Hope it does.

@DaveT2:

I have a new 64-bit laptop coming in a few weeks -- we can install 32-bit Vegas on the 64-bit machines, yes? I was wondering about that because my fallback computer will be my old Inspiron 32-bit machine.

- No I do not have a Wacom tablet. Atleast not on this machine. My wife has one and she loves it, but we don't do any production work on her workstation.

- This is essentially a new install as of about a month and a half ago. All drivers are up to date. Windows 7 rocks. Vegas is the only piece of software that crashes, and it happens regularly.

- I never use Dynamic Ram Preview. Since it was suggested about a month ago that it MIGHT be causing the problem (and it is not), I turned it to 0. So it is definitely not DRP. I pray it would be such a simple issue.

- I haven't gotten the 'closing error' that you all are mentioning. I HAVE gotten it in the past (have been using Vegas since version 8), but not regularly.

- Stabilization is broken: It fails to properly stabilize 60fps footage. Acts like its working, then does nothing.

- GPU acceleration: When it is turned off, the errors still happen. When on, errors still happen, but everything works like it should, until an error happens.

- GPU while rendering: The Galaxy GTX 670 (like other new cards) is currently not supported for AVC/mp4 GPU accelerated rendering. In Vegas 10 it works brilliantly! In Vegas 11, it says 'no GPU'. So right now I am rendering out an hour and a half event, heavily graded with Neat Video and Magic Bullet Looks that is taking over 27 hours to complete. With GPU enabled it would be half of that. Note: it is a TON of grading, so I am not shocked at the amount of time involved in this particular render, just voicing frustration at the piece of software I paid money for!


I am NOT having these issues in Vegas 10. Now that I have completed my current project, I am moving back to 10. The stabilization plugin in 10 is better, it crashes LESS frequently and just doesn't have these issues.

I will gladly post the next error log in full. If you have any more suggestions feel free to send them my way. I have half a mind to just move completely to CS6 and be done with Vegas completely. So far Sony simply hasn't been responsive. There is a reason that folks like Red Giant haven't ported their suites to Vegas.

I read your post. Did you ever find a solution to this problem?

Problem Description
Application Name: Vegas Pro
Application Version: Version 11.0 (Build 683) 64-bit
Problem: Unmanaged Exception (0xc0000005)
Fault Module: C:\Program Files\Sony\Vegas Pro 11.0\vegas110k.dll
Fault Address: 0x000000018001758E
Fault Offset: 0x000000000001758E

Fault Process Details
Process Path: C:\Program Files\Sony\Vegas Pro 11.0\vegas110.exe
Process Version: Version 11.0 (Build 683) 64-bit
Process Description: Vegas Pro


This error happens daily. I hit play, it crashes... This happens more in 11 than in any other version of Vegas I have ever used. When it DOES work, it works just fine. I'm going back to 10 until Sony releases an update for this.

My specs:
MB: Asus P9X79 Deluxe
Processor: Core i73930K @ 3.2GHz (16 thread CPU, current top of the line)
Ram: 32GB
GPU: Galaxy GeForce GTX 670
Harddrives:
Intel SSD Cherry 520 (120GB SSD) - programs
WD VelociRaptor (10K rpm, 250GB) - scratch disk
G-Speed 8TB RAID5 - backup

This computer runs everything in the world, including Adobe CS6, like a dream. Smooth playback, FX, layering, grading... All of that is no problem, except in Vegas 11.

Does Sony even read the 'error' reports we send in?

...I turned it to 0

Dynamic RAM is used for more things than RAM previews. If you're sure life is better with it off then by all means leave it at zero, but it seems to me that *some* is usually better than none. But that's probably not your problem.

You might try running Vegas in Windows7 or Vista compatibility mode anyway. Although I think it's related to Wacom drivers there might be more to it than that. Compatibility mode would force Vegas to use some pre-SP1 components of Win7, which might make a difference.

Rob

Compatibility mode makes no difference. I have moved the dynamic ram preview back to 2gb. Makes no difference.

Why do you keep bringing up the whole Wacom drivers thing? I do NOT have a Wacom tablet installed on this computer, and I don't plan to. So why are you discussing drivers that are not installed on my system?

Since the W**** tablet and compatibility mode are related it's hard not to mention them both in the same sentence, especially for the benefit of other readers since some readers hit the forum once a month and miss these conversations.

However, as you say, Compatibility mode has no effect, setting DRP to a modest 256MB has no effect, and you have never, ever, ever once had a W**** tablet attached to this computer and so there has never, ever, ever been a driver installed. So we can set those things aside.

Since you say that the crashes occur when you hit play, I'd look to drivers, like the one for your Motu card. I assume that this sort of thing had been solved but you might search the forum for ASIO. And just because a problem was solved for VP10 doesn't mean it stayed solved. Vegas changes, drivers change, Windows gets patches, and so on.

Does VP11 crash every time you hit play, or just sometimes? Only over certain types of media, or all types?

Rob

The MOTU 896 is not currently hooked in and drivers were removed a while back. I am using the on-board MB sound, which is fine. I wanted to remove ALL variables to this, and I am left with software.

It doesn't happen every time, but almost every time. In Vegas 10, no problem. It chugs right along and doesn't fuss when I hit play. In Vegas 11 I have to save after every major revision so that I don't loose 2 minutes of color correcting...

To me it seems that is has to do with large scale projects. The main project I finished recently which is where all of this came to a head, was a 4 camera concert. Most people I meet who use Vegas are doing so with simple project... Capturing gameplay footage, editing home videos, simple promotional projects... I am doing business with this software and it is just way to unstable.

If Sony patches V11 by the end of July, and it fixes all of this junk, I will continue to use it. If not, my staff and I will go through the Adobe CS6 crash course and move all future projects to Premiere.

My computer is a top of the line beast of a workstation. I can throw ANYTHING at it and it just laughs... except for Vegas 11. Sony just isn't taking their software development seriously, and they obviously don't read the crash reports. I've been filling them out and including my email in them for about a year now. Never heard from them, nor are they fixing the problems...

I have no idea what the problem is but I assume if it happens when you hit play that there's a driver conflict. This thread might be interesting: http://www.sonycreativesoftware.com/forums/ShowMessage.asp?MessageID=818283&Replies=0

You're doing what I would do with the hardware which is to start removing and simplifying. However, that's a lot of effort to go to when you're supposed to be editing.

In Production we don't fix things during the job, we replace them. If a camera, an HMI, or a dolly goes bad we call the rental house and get a replacement hauled out to the location if at all possible. Similarly, you might be better off trying Vegas on some other machine, especially since it doesn't really need the beast you're running it on.

We had a similar experience with Premiere Pro CS2. We bought three systems, "beasts" for their day, and three Matrox Axio cards. The idea with the Axios was that they'd do some hardware acceleration, pass the OpenGL bits to a high end graphics card, and let the CPU do the rest. These systems were able to to short pieces of a couple of minutes but anything longer crashed at the drop of a hat. It was obviously going to be impossible to edit long form projects and so we added an FCP system to the complement.

There were a couple of things going on with the PPro systems. The first was that our knowledge pool went back to the early 90's with Media100 systems on the Mac. It was an unquestionable given that ALL edit systems needed specialized hardware. When we finally got tired of Apple screwing us over and we saw demos of the Axio cards we saw an opportunity to jump to Windows platforms. There was absolutely no chance in a million years that we'd adopt Vegas because of its lack of hardware support. The same went for Final Cut since there was no acceleration available.

When the PPro systems started blowing up in our faces (32-bit software, 32-bit OS, and fairly fat media streams needing to move from card to card to CPU) I suggested removing the Axio cards and trying it without acceleration. Unfortunately, the fact that we had these "Beasts", had bought into the hardware acceleration, and just generally had too much of our mindshare invested in it meant that there was just no willingness to try to make the software work on lesser hardware.

Which is funny because eventually we moved most projects to FCP on much simpler systems with no hardware acceleration at all. But the person in charge (who wrote the checks) couldn't bring himself to try PPro bare because he'd invested his money and perhaps a bit of pride into the "beasts".

Which is to say that you might question whether you have to run Vegas on that particular machine.

As to SCS' commitment to the software and to tech support...they're selling a consumer product. Back in our Media100 days we had no problem getting their support on the phone. We were on a first name basis with them. This has not been the case with Adobe or with Apple, but I'm sure they answer email faster than the six weeks SCS takes for direct tech support questions. And I don't think SCS ever answers the automated crash reports. Someone else may be able to say otherwise.

If I were to guess where I might get better support I might think of Avid or Grass Valley. Everyone else is really just making their money from Prosumers. FCP does have the advantage of having a big base of professional users who are smart and have seen most problems, and it runs in a very predictable hardware and software environment.

Rob

Its funny you should mention that option. I got my start on the old Trinity editing systems. I have no clue if thats actually the name for the system... Its probably just the name of the manufacturer. Back then they were using Soundforge for audio mastering, but had not moved to Vegas (or any other NLE). It was rough work but made me greatly appreciate NLEs!!!

Honestly, when I build a computer it really is an investment. I will not be downgrading in order to make Vegas happy. Instead I will be moving to Adobe CS6, where every plugin in the world is supported.

I completely understand the merits of building within what Vegas 'likes", but if Vegas can't handle the current generation of graphics cards or any other part of my build, then I wont hesitate to move elsewhere.

When Final Cut X came out, folks left it in droves. Why? Because of missing features? In Vegas the missing features are structural integrity and GPU integration. Those are much more important than any other 'extra' feature. I will continue to use it on all existing projects and have attempted to sign up for the beta. I genuinely LOVE Sony Vegas, but 11 is by far the buggiest version I've ever used.

I am using 10 every day. Its rock solid. Hopefully the next update will address all of these issues and I can get back to loving the most direct NLE I've ever seen. I don't want to go through the hassle of learning CS6, or migrating existing projects, or spending money on it... I want to stay. But the argument of paying a re-stocking fee on a bunch of great hardware, or selling stuff at a loss, in order to appease software is pretty crazy.

On Sony's site is just says you must have a GPU of X or greater. If they don't support the new GTX 670+ cards, then they need to say so!