Just a theory as long as your testing.

Try setting your ram preview to "0" and see if it will crash after playback of some material on the timeline.

I have a theory that something between the GPU and ram could be a problem. I base this on the fact that I am having crashes also but only after playing the timeline for a while and when I ask the program to start playing something new, it crashes. Always the same unmanaged exception 0xc0000005. Different fault address than yours but always the same on my machine, every crash.

Dynamic RAM Preview Max (MB): 0
GPU acceleration of video processing: Off

With those settings I added 8 clips, with transitions, FX, Pan/Crop, etc. It's set to loop through the project. I'll leave it playing for a while, then add clips and change parameters.

It's been looping for nearly 3 hours, and I just added a new clip with no crash. I was also able to start a new project this time without it crashing.

1. Installed Sound Forge Pro 10, opened MP3 file.
2. Noticed Aero was off, turned it on.
3. Installed Zoom R16 drivers, set Vegas to ASIO.
4. Changed default project settings to 1080p, 24fps, no deinterlace, best.
5. Plugged phone to USB.
6. Opened Notepad to type this in there.
7. Installed Adobe Photoshop CS6, opened 3D object, painted, animated, rendered movie, imported in Vegas.
8. Set various Video Track FX, including Chroma Keyer, messed around with the FX, Compositing, Reverse.
9. Clicked the X to close Vegas Pro and it crashed on exit.

Problem signature:
Problem Event Name: APPCRASH
Application Name: vegas110.exe
Application Version: 11.0.0.683
Application Timestamp: 4f967c0e
Fault Module Name: sfapprw.dll
Fault Module Version: 11.0.0.683
Fault Module Timestamp: 4f9677d0
Exception Code: c0000005
Exception Offset: 00000000002266f4
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033
Additional Information 1: 2ccb
Additional Information 2: 2ccbf8a2b378defbe49433ccb30c2f75
Additional Information 3: 2407
Additional Information 4: 24076a71231aac64d5f130d0cef6549b

Jamon, while I appreciate your efforts, testing and reporting (I'm sure a lot of us do), I can't help but see the irony in this situation: A customer trying to fix a bug in a piece of software (on his own time) that he's PAID a company to design, test and deliver in working order.

More irony: It seems that even more customers have had better luck at figuring out these bugs then the people we paid to figure them out. While the official updates have given some people a little more stability, it's the customers that have been making the real breakthroughs.

If I'm wrong or missing something, I don't mind being corrected, but that's how it appears to me.

Yeah, I'm not sure what happened. I've used Vegas since its first release by Sonic Foundry when it was just an audio multitrack recorder. I don't think I've used every version since, but I've used several, and I don't remember it ever being this buggy, and when there were bugs they were usually fixed with updates.

I'm not sure what else to do. Surely many others have emailed them, so it's not that they aren't aware. I thought maybe they just can't reproduce all the issues people are having, so maybe somewhere in the info we post there might be some clues some developer can use. It's not ideal, but it's been 8 months and it's still not polished.

Jamon,

Thanks for testing my idea. I hope that SCS takes note. I went to render a project of mixed hdv mpg, mxf, and mov files 1920x1080 to HDV 720x480 NTSC Widescreen the other day and had my ram preview set to 4096. The render ripped through the first few hundred frames like lightning and then slowed down to one frame per second. Knowing that this wasn't because of any effects on the timeline, I stopped the render, changed ram preview to 0 and restarted the render. It flew through the entire timeline, rendering at three times the speed of the project, 1 hour timeline in 20 min render. Dynamic Ram preview was causing a problem.

This led me to wondering about the timeline replay crashes that I have been experiencing. As I said earlier, it seems to occur after the ram preview gets full. I am not a programmer, just a user, but it seems that a direction in the code on how to handle the ram is not set correctly and is what could be causing the unmanaged exception crashes.

Anyone with coding experience care to weigh in? Maybe even Forum Admin? Paddy?

Thanks Jamon and Jimsch, I believe this thread allowed me to fix a problem with V11 where the Color Curves settings wouldn't show up after applying it to an event.

It was easily reproducible, all I had to do was to move on the timeline from events to events, play and stop..... and then apply a Color Curves to an event and Vegas would crash (never previewing to ram: shift B)

Setting the ram preview to 0 seems to have fixed the problem. That should bring me back to V11 and I will definetely test this in the coming days.

EDIT: sadly on day 2, the Color Curves does crash V11 with RAM preview set to 0.

Rob

Jamon,

Thanks for your efforts. You mentioned that in your initial setup, you installed the Wacom tablet driver. Why is this part of your setup? We have found that there are incompatibilities between Vegas Pro and this driver (possibly similar drivers as well) that may lead to instability in Vegas. We are working to resolve these issues. In the meantime, I would avoid using them concurrently. Please disable/uninstall the Wacom driver and test again.

Paddy
SCS

Good to know; I read the known issues but don't remember seeing that one. I wonder if the Wacom driver incompatibilities are unique to version 11. The reason why I installed it even in the bare setup is because I use a Wacom tablet instead of a mouse. I don't even have one plugged in, and have used a pen as my primary pointing device for over 10 years.

I'll uninstall the Wacom driver (6.3.2w3) and try again with a USB wired mouse.

Jimsch said: The render ripped through the first few hundred frames like lightning...

I don't know if this was your situation, but that sort of behavior can be normal if those first frames were all cached in the preview RAM, which they probably would be if they were the last frames you'd played. This is not to say that the rest of the observation isn't correct, just that renders usually rip through the cached frames and then slow down.

The fact that your render went so well with no preview RAM at all is interesting but this behavior seems to vary depending on what media is on the timeline and what the output type is. Sometimes this works, sometimes you need a modest amount of preview RAM.

I totally agree that Vegas could be managing preview RAM more cleverly. And I'd love to see a more bulletproof render/compression scheme. I'd be willing to dedicate a disk to it if that's what it took.

Rob Mack

Obviously I've been asleep at the wheel since BOTH my systems have a wacom pad attached. Argh. I'll have to uninstall and see if stability improves.

@paddy-
Which Wacom drivers are the ones that cause the bugs? I am an editor but also an animator, and my main screen is a Wacom Cintiq 21UX. I have used this since Version 7 of Vegas, and never had many problems.

Version 11 of Vegas is uniquely buggy, though I have had much more success using Vegas in "Compatibility Mode" set to Vista Service Pack 2.

A customer trying to fix a bug in a piece of software (on his own time) that he's PAID a company to design, test and deliver in working order.

Yeah, we should all keep the relevant data on our crashes secret, and make them work to reproduce it.

geoff

I set the Dyanmic RAM Preview to 1 and filled up the timeline with 1 hour of clips filled with FX and transitions. I did things in the timeline, stopping and starting, looping, etc., and tried building the RAM preview, which doesn't work because 1 MB is too small.

Set the loop region to the last 10 minutes, rendered as Sony AVC 10 Mbps Blu-Ray preset, 16:06.

I pressed the Esc key to close the rendered dialog box, and the hourglass cursor is going, where I can resize the entire Vegas window, and the dialog disappeared, but I can't click anything and the rendering progress bar is still in the lower left.

I tried clicking cancel in the lower left, but it's not doing anything. I still have the Wacom driver installed, and Internet Explorer is open, with Photoshop, Notepad, and Sculptris.

It's been minutes and nothing is happening, and I can still resize the window, but can't find any dialogs waiting or anything, and no error messages, so I'll have to try to close Vegas.

Clicking the X close button does nothing. But now the hourglass is gone, and I can't alt+tab to Vegas anymore. If I minimize other windows I can see the timeline, but can't click or resize.

Right-click close window in the taskbar does nothing. After End Task in the Task Manager I get:

Description:
A problem caused this program to stop interacting with Windows.

Problem signature:
Problem Event Name: AppHangB1
Application Name: vegas110.exe
Application Version: 11.0.0.683
Application Timestamp: 4f967c0e
Hang Signature: bddb
Hang Type: 6400
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033
Additional Hang Signature 1: bddbc03d42542c8a60e09080c2e24a44
Additional Hang Signature 2: cc94
Additional Hang Signature 3: cc9428d261a9112b5500732dcc2909a7
Additional Hang Signature 4: bddb
Additional Hang Signature 5: bddbc03d42542c8a60e09080c2e24a44
Additional Hang Signature 6: cc94
Additional Hang Signature 7: cc9428d261a9112b5500732dcc2909a7

After restarting Vegas it offers to restore the unsaved project. I set the in and out points to the last 10 minutes again. I see the Dynamic RAM Preview options has defaulted back to 200.

I played the loop region halfway, then pause, return to start of loop, and press shift+b to build the RAM preview. The loop region changes to fit the tiny sliver it can fit in the RAM Preview space.

I go into Preferences and change the allocated space from 200 to 4096 and build again. But after an entire hour, it's only finished a few minutes worth of RAM preview.

So I cancel that and render again using the same preset, which takes 1:01:16. But I realize that before the crash I changed the render quality to Good, and now it's Best, so change that back and re-render, but that's estimated at an hour too. Before the crash it only took 16 minutes, what's different?

I compared the 2 videos, and they're different, so the restored version of the project is not identical to the point of render the first time.

Starting over, save this time prior to render. Dynamic RAM preview off, delete all prerendered video, 11:51.

Dynamic RAM Preview set to 4096, shift+b stopped rendering before around 6 minutes and reset the loop region to match that.

I change the loop region back to 10 minutes, render, 11:26.

So, building the dynamic RAM preview seems to take much longer than an actual render. I'm not sure why. It also doesn't seem to be reused for the actual render, as a cache.

Also had the RAM Preview option defaulted back to 200 even if it was set to 0 and Vegas was shutdown properly.

i've been using a wacom from ver 5 with no noticeable problems?

since 8.1 on i haven't discerned any problems OTHER than the well documented ones others have noticed. i don't see my wacom causing media swap for a start!

i have rsi from using a mouse and am very unlikely to go back to using one.

i occasionally have the dreaded cursor ripple showing up for a moment or two, but this also happens in other progs, even though i have it turned off (properly!)

I also haven't had any issues with prior versions of Vegas Pro alongside Wacom drivers. I haven't uninstalled the Wacom driver to test yet, and am debating not bothering, because from my perspective it's almost like saying a software package is incompatible with keyboard drivers. Many of us use Wacom tablets daily, so it is standard setup.

Well, for me, setting the Dynamic RAM preview to 0 and disabling the GPU acceleration has resulted in Vegas Pro 11 successfully rendering a 3D (SbS) AVC file with the NewBlue Titler enabled. I'm very grateful for the people who figured this out.

Of course, those people do not work for Sony Creative. And, it also implies that two of the default settings cause Vegas Pro not to work. It's almost as if they traded reliability for implied speed (I write 'implied' because crashes eat up time, too).

Thanks again for the extraordinary efforts in debugging Vegas Pro on your own time!

Andy

That's nailing it right on the head. I never heard it described more accurately:
"Trading stability for implied speed" Maybe SCS should use that as Vegas' motto or sales slogan?

I use classic mode with Aero off.

If Vegas is doing a background task of some kind and I click the 'X' to close it, it almost always gives an error. That was previously listed as being fixed. But since I am closing it anyway I do not particularly care as long as it does not corrupt my project.

I noticed that if I should go online with the editing system, Vegas and Nero will have stability problems or are much more likely to. Internet explorer and related plug-ins can cause a ton of problems!

Due to the high expense of using the editing system for internet and general use at 260 watts just sitting idle, I bought me a notebook computer that only uses 10 watts. A maximum of 50 watts (36 watts average) with the external non-led monitor. Still a lot less than 260 watts.

That has knocked a big chunk off my light bill and makes my editing system much better because it is no longer used for the internet. No need for anti-virus and other stuff that uses up important resources. The notebook will pay for itself in light bill savings!

Now is a good time to get a notebook or equivalent if you want to avoid Windows 8 and there are good sale prices.

In other news, one of my hard drives failed with only 12 days left of the warranty. I was having crashes from Vegas while rendering at 99% of two hours with unknown errors before the hard drive failed.

I had a single AVC clip in the timeline, with a 6-point velocity curve. The Track FX had 'Color Corrector', and 'Brightness and Contrast'. The timeline was playing, and when I closed the FX window it crashed:

Description:
Stopped working

Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: vegas110.exe
Problem Signature 02: 11.0.0.683
Problem Signature 03: 4f967c0e
Problem Signature 04: Sony.MediaSoftware.VideoEffectsUI
Problem Signature 05: 11.0.0.683
Problem Signature 06: 4f967ba2
Problem Signature 07: 574
Problem Signature 08: d
Problem Signature 09: System.NullReferenceException
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

I opened the recovered project, but the Track FX were gone. I tried to repeat, having the clip play, then opening the Video Track FX window and adding a Color Corrector. I changed the color, then as it's still playing added Brightness and Contrast and increased Contrast, then closed the Track FX, and when I cicked in the timeline again it crashed:

Problem signature:
Problem Event Name: APPCRASH
Application Name: vegas110.exe
Application Version: 11.0.0.683
Application Timestamp: 4f967c0e
Fault Module Name: StackHash_cdab
Fault Module Version: 6.1.7600.16915
Fault Module Timestamp: 4ec4b137
Exception Code: c0000374
Exception Offset: 00000000000c6ae2
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033
Additional Information 1: cdab
Additional Information 2: cdab6d6541d8f8247ad9af51b54309f8
Additional Information 3: 0d3d
Additional Information 4: 0d3d0b538d99bb325454afc7310e047d

This time, there was no recovered project when I opened. I started fresh, dragged the clip, added Color Corrector, changed the color, added Brightness and Contrast, increased contrast then closed and clicked in timeline, and it's fine.

I tried again, this time adding a Velocity envelope to the video clip first, and again, it's fine.

I could reproduce it with that previous project, but after I started fresh, even though everything was setup basically the same, I couldn't reproduce it with simple steps.

I haven't posted here in a bit, not because there were no bugs, but because I stopped using Vegas. I need to decide if I want to upgrade to v11 this month, so just tried starting an actual project, and it went okay for probably a half hour, but then these crashes.