Vegas Crashes ... they kinda suck

MUTTLEY wrote on 7/10/2005, 4:52 PM
Have had this happen enough to scare me:

Sony Vegas 6.0
Version 6.0b (Build 114)
Exception 0xC0000005 (access violation) READ:0x44C IP:0x645166
In Module 'vegas60.exe' at Address 0x400000 + 0x245166
Thread: VideoRender ID=0xF4 Stack=0x927F000-0x9280000
Registers:
EAX=00000000 CS=001b EIP=00645166 EFLGS=00010246
EBX=0000001c SS=0023 ESP=0927fc5c EBP=001ddbc0
ECX=00000000 DS=0023 ESI=00000000 FS=003b
EDX=001ddbcc ES=0023 EDI=14365480 GS=0000
Bytes at CS:EIP:
00645166: 8B 81 4C 04 00 00 74 1D ..L...t.
0064516E: 85 C0 75 17 0F B7 41 12 ..u...A.
Stack Dump:
0927FC5C: 0065C2B9 00400000 + 25C2B9 (vegas60.exe)
0927FC60: 00000000
0927FC64: 008DD1B0 00400000 + 4DD1B0 (vegas60.exe)
0927FC68: 00000003
0927FC6C: 00000000
0927FC70: 14365480 132B0000 + 10B5480
0927FC74: 00000000
0927FC78: 14365478 132B0000 + 10B5478
0927FC7C: 00000000
0927FC80: 00000000
0927FC84: 00000000
0927FC88: 0000001C
0927FC8C: 0065CB26 00400000 + 25CB26 (vegas60.exe)
0927FC90: 13A7F750 132B0000 + 7CF750
0927FC94: 0016DAA8 00150000 + 1DAA8
0927FC98: 14365480 132B0000 + 10B5480
> 0927FD18: 00652519 00400000 + 252519 (vegas60.exe)
0927FD1C: 001DDBC0 00150000 + 8DBC0
0927FD20: 13A7F750 132B0000 + 7CF750
0927FD24: 0016DAA8 00150000 + 1DAA8
0927FD28: 00000003
> 0927FD44: 00653456 00400000 + 253456 (vegas60.exe)
0927FD48: 14365470 132B0000 + 10B5470
0927FD4C: 001DDBC0 00150000 + 8DBC0
0927FD50: 13CAFB08 132B0000 + 9FFB08
0927FD54: 13B19A18 132B0000 + 869A18
> 0927FD5C: 00653408 00400000 + 253408 (vegas60.exe)
- - -
0927FFF0: 00000000
0927FFF4: 005716E0 00400000 + 1716E0 (vegas60.exe)
0927FFF8: 0021C298 00150000 + CC298
0927FFFC: 00000000

- Ray

www.undergroundplanet.com

Comments

Spot|DSE wrote on 7/10/2005, 5:33 PM
Not that it matters a whole lot, but why aren't you using Build 115?
vicmilt wrote on 7/10/2005, 6:10 PM
what's all that mean? what happened?

v
MUTTLEY wrote on 7/10/2005, 6:33 PM
Spot, didn't know I missed an update, downloading it now.

Vic, just up and crapped out on me. At the time it happened I was just changing the preview setting and *poof*, it kind of lagged for a moment and than got the crash pop-up with that stuff in it.


www.undergroundplanet.com
vicmilt wrote on 7/10/2005, 7:16 PM
Did you lose anything (but time and aggravaiton?)
Had you recently saved your project - if so, did you lose that?
If not, did Vegas automatically bring it back anyway (it generally does that for me?)
I don't have any solutions, but if this is a known bug, it's better to be forewarned.

Look, like a lot of guys on this forum, I've been cutting for a LONG time - and every system I ever worked on had it's ups and downs. You do learn to save continually, that's for sure.
And you also learn where "not to go" -you (not just you muttley) are a pioneer on the cutting edge of the media and communcation revolution that will in hindsight be seen as the biggest thing to have happened to civilization - possibly ever.

It's hard to see the forest for the trees (and bugs), but this still beats the crap out of scotch taping little bits of film together, one at a time.

v
apit34356 wrote on 7/10/2005, 9:22 PM
Vicmilt, did your steel shutters work well?

"but this still beats the crap out of scotch taping little bits of film together, one at a time." Well, but you were not subject to catastrophe computer failure with a major power grid failing. ---- just kidding---
Edward wrote on 7/10/2005, 11:57 PM
try doing a 10 minute slide show in Macromedia Director.... ouch
farss wrote on 7/11/2005, 2:13 AM
"but this still beats the crap out of scotch taping little bits of film together, one at a time"

Come on Victor, nothing beats real editing, I reckon it's all in the smell, maybe there's a market for a 'bromine' air freshner for edit suites? Just to give them an authentic smell.
And what was that stuff we used to clean fim with, wasn't it something that's still leaving it's mark in the ozone layer.

I probably shouldn't say this but even back then things used to crash, I still remember picking up the only print of Woodstock in the country off a platter and the middle fell out of it. Four hours and a few extra splices later we had it wound onto a reel.
Bob.
MUTTLEY wrote on 7/11/2005, 8:18 AM

I hear ya Vic, and I'm a fan of Ctrl+S, but that doesnt make it more fun. Yes I did loose some, but just time. No Vegas did not try to bring it back the next time I opened it.

- Ray

www.undergroundplanet.com
Liam_Vegas wrote on 7/11/2005, 9:44 AM
Did installing v6.0b help with this particular problem?
vicmilt wrote on 7/11/2005, 7:53 PM
Couple o' answers here...
apit - thanx for asking about my shutters... what a pain in the *** !

We spent half a day last week, grunting out the shutters and screwing them into place (good valuable editing time - gone forever). Now I'm living in a darkened steel tomb - God forbid we have a fire - there's no way out.

farss
I am an unabashed fan of yours, but cutting film sucks - to me it's like comparing cruising a major highway in a "super-bus", with travelling on wood wheels and a covered wagon - yeah I remember the smells - I think that stuff was called tetrachloride, but whatever it was, I'm sure I gave up months of life from breathing it. You've conveniently forgotten logging dailies, slugging missing frames of film and waiting three days to see a lower third - nooop - this is heaven! I LOVE non-linear and I LOVE vegas -

now Muttley - I am SO glad that you didn't lose any footage or drives or anything but time. Just chalk up your "lost time" against the time you saved by doing everything electronically - that still leaves you weeks of time to piddle around, that you would have spent:
syncing dailies, waiting for work prints, logging dailies and sorting clips into bins (bins were big rolling baskets that actually had dozens of feet hanging from little pins - you had a couple of these around the room. If you wanted to find a clip, you'd look it up in the book, find the correct bin, then sort of look at a dozen or two strands of film, finally find one that might be correct, and "trim" it with a cutter, then paste it into your show with perforated scotch tape (at $50 a roll). Think you want a dissolve? Make a line with a china marker on the workprint... ah well.... yada yada yada - it wasn't any easier and you had ALL kinds of OTHER problems - scratches, dust, dirt... the moviola chewing up your best scene -

and don't think the "other" non-linear systems are free of crashes, bugs and awful problems - THEY ALL GOT 'EM. (My daughter works up at Fox and you should have heard them crying when they installed their new super Gucci AVID Adreniline - hey that's what separates the men from the boys... being able to hang in and Get It On...

Muttley - You do Great Work.... I say, Quitcher Bitchin' and get back to it. :>))

best to all -
v
ps - today my computer decided it wasn't necessary to navigate anymore - oh well - we'll get over it, soon... somehow...
Catwell wrote on 7/11/2005, 7:59 PM
I think the discussion of film editing needs a reminder of my early years,scraping the emulsion and cementing the clips together. Oh dear, I am showing my age.
JJKizak wrote on 7/12/2005, 5:50 AM
Dupont 901, Eastman 910.

JJK
DavidPJ wrote on 7/19/2005, 5:42 AM
I'm running Vegas 6b with 2GB Ram and it seems like every time before I'm done with a 3-4 hours editing session Vegas will crash. I can't duplicate the cause of the crash, but it seems like it's likely to crash when I have multiple instances of Vegas opened. Media Manager is disabled.

With Vegas 5d, I almost never had a crash. I'm hoping Vegas returns to that level of stability in the next maintenance release.
JJKizak wrote on 7/19/2005, 6:51 AM
Same with me. It's caused by V6 running out of memory. Work around is to save project about half way through the day, then reboot to reset the paging file. Also to keep the ram setting at 16 megs. Actually what happens is any other application that is open at the time will crash too, Forge, Acid, etc.

JJK
rmack350 wrote on 7/19/2005, 8:18 AM
I've not specifically had this happen with Vegas but other apps I use run up the paging file. I've learned to keep the task manager open and keep an eye on the cpu and memory usage.

I'll bet there are some nice little monitoring widgets you could get that would help with this.

Rob Mack
DavidPJ wrote on 7/19/2005, 9:20 AM
Yes, in my case when Vegas 6 crashes it's also catastrophic, the entire PC crashes and must be rebooted.

Regarding the RAM render setting, 16MB is pretty small to be very useful. Does the RAM render setting actually allocate this space so no other apps, including Vegas itself, can use this memory for anything other than RAM renders?

Has memory management changed from V5 to V6? I never noiticed memory/paging issues with V5.
JJKizak wrote on 7/19/2005, 10:28 AM
All I know is if you start setting the ram over 16 it crashes faster on my system. And make sure your Win XP ram default setting is set to application and not cache. There was no problem with ram in V5 other than very large projects.

JJK
jkrepner wrote on 7/19/2005, 10:36 AM
For me, when 6 crashes, I don't have to reboot. Which is a good thing.

On a side note:

I wonder if Sony realizes how many customers they lose when messages like this appear (un-answered by Forum admins) on messages boards, especially on company forums such as this one. Many people read forums for a few days/weeks before making a software purchase, because, it's a great way to see how the program actually works or doesn't work for real users.

If I had a niche software company, I would respond to EVERY single negative post, not the topic, but the post, with some sort of official company response. I know these message boards are for users to help one another and not a direct line to tech support, but I think Sony should pay more attention to them. Perhaps they could devote some of the money they use to send me 2 or 3 Acid catalogs in the mail each month to having someone reply to problem posts on the Forums.

.02
DavidPJ wrote on 7/19/2005, 12:09 PM
Thanks JJK. I'm going to lower the ram render memory and see if it helps. Also checked XP memory usage and it's already set to Programs not system cache.