Vegas 6d crash

john-beale wrote on 5/3/2006, 9:42 AM

Does anyone know what this means? This crash ocurred when I re-opened the Vegas window some time after it had successfully completed a several hour render to 1080i HDVi format. I think the only thing I did was slide the scrollbar to view the timeline; I did not do any editing actions.
---------------------------------------------------------------------------------------------------

Sony Vegas 6.0
Version 6.0d (Build 210)
Exception 0xC0000005 (access violation) READ:0xFFA79A8D IP:0x571E1F
In Module 'vegas60.exe' at Address 0x400000 + 0x171E1F
Thread: VideoCache ID=0x30C Stack=0xB70F000-0xB710000
Registers:
EAX=0b70ff80 CS=001b EIP=00571e1f EFLGS=00010246
EBX=00000000 SS=0023 ESP=0b70ff50 EBP=ffa79a89
ECX=0b70ff80 DS=0023 ESI=ffa79a89 FS=003b
EDX=00233dc0 ES=0023 EDI=ffa79b8b GS=0000
Bytes at CS:EIP:
00571E1F: 8B 4E 04 57 83 C1 0C 51 .N.W...Q
00571E27: C7 44 24 10 00 00 00 00 .D....
Stack Dump:
0B70FF50: 0098EFF4 00400000 + 58EFF4 (vegas60.exe)
0B70FF54: 00000029
0B70FF58: 0B70FF80 0B610000 + FFF80
0B70FF5C: 0057220F 00400000 + 17220F (vegas60.exe)
0B70FF60: FFA79A89
0B70FF64: 024F1961 01950000 + BA1961
0B70FF68: 0B70FF80 0B610000 + FFF80
0B70FF6C: 0098EFF4 00400000 + 58EFF4 (vegas60.exe)
0B70FF70: 00000000
0B70FF74: 0B70FFB4 0B610000 + FFFB4
0B70FF78: 7C809C4C 7C800000 + 9C4C (kernel32.dll)
0B70FF7C: 00000000
0B70FF80: 00000000
0B70FF84: 0057235B 00400000 + 17235B (vegas60.exe)
0B70FF88: 00000004
0B70FF8C: 0023F9C8 00140000 + FF9C8
> 0B70FF90: 00655200 00400000 + 255200 (vegas60.exe)
> 0B70FF94: 0098EFF4 00400000 + 58EFF4 (vegas60.exe)
- - -
0B70FFF0: 00000000
0B70FFF4: 005722F0 00400000 + 1722F0 (vegas60.exe)
0B70FFF8: 0098EFF4 00400000 + 58EFF4 (vegas60.exe)
0B70FFFC: 00000000

Comments

JJKizak wrote on 5/3/2006, 11:05 AM

You should (in my opinion) reboot Vegas every 8 hours to reset the paging file. Otherwise it gets real clunky.

JJK

john-beale wrote on 5/3/2006, 4:34 PM

I tried another render to 1080i HDVi. This time, Vegas simply stopped working at 12% complete (the project is only 9.5 minutes duration, but takes several hours to render). The program has not crashed, it is still updating the rendering dialog box with "Approximate time left" and "Elapsed time (hh:mm:ss):" numbers, but CPU usage is 0 and frame # does not change.

This is very frustrating to say the least. My computer is stable with other programs. I've run memory testers with no errors. I have 2 GB ram and the program is not using all of it. What now?

john-beale wrote on 5/3/2006, 5:13 PM

another crash, this time just starting a short render, starting from the middle of my timeline. My project uses 1080i HDV (.m2t) material from my FX1. I do not remember having Vegas crash when I was using DV material. Vegas is supposed to work with HDV, right...?

--------------------------------------------
Sony Vegas 6.0
Version 6.0d (Build 210)
Exception 0xC0000005 (access violation) WRITE:0x3C IP:0x4154A28E
In Module 'cfhd.dll' at Address 0x41500000 + 0x4A28E
Thread: ProgMan ID=0x91C Stack=0xAACF000-0xAAD0000

riredale wrote on 5/3/2006, 5:23 PM

I'm still really new at this HDV thing, but my conclusion so far is to use the captured m2t files to generate DV Proxies and/or Cineform intermediates, and after doing so, throw away the m2t files (figuratively speaking, of course) and deal only with DV and Cineform. For some reason Vegas has a terrible time dealing with numerous m2t clips on the timeline. By contrast, it handles Cineform clips with almost the same ease and alacrity as good ol' DV.

When my project is finished, it's true that I need to render out to m2t in order to print to tape, but I'd have to render to m2t even if my timeline had m2t clips on it. In fact, my PC seems to render faster from Cineform->m2t faster than from m2t->m2t.

john-beale wrote on 5/3/2006, 5:58 PM

Yes, what I did was use GearShift to generate DV proxies, edit, shift back to .m2t and then try to generate the final output. But things aren't going so well, as described above. I would have used HDV-Intermediate if I had 3x more disk space available (this is basically a documentary and there is around 20 hours of footage involved in the edit).

Converting to HDV to HDV-I is also slow, less than 1/10 real time and I don't have enough time to convert the originals now before the project's due... What fun to be on the cutting edge eh?

Oh, how fun... another crash. Is there any useful place to send these little messages? Or should I quit while I'm behind and take up dishwashing...

Sony Vegas 6.0
Version 6.0d (Build 210)
Exception 0xC0000005 (access violation) READ:0xFF0D1430 IP:0x646A81
In Module 'vegas60.exe' at Address 0x400000 + 0x246A81
Thread: VideoRender ID=0xFBC Stack=0xFB5F000-0xFB60000

riredale wrote on 5/3/2006, 9:45 PM

All I can think of is to just highlight a portion of the whole timeline and render just that to a new m2t file. Keep continuing down the timeline until reaching the end. Then just pull in those new m2t clips and do a final render from them.

EDIT: Oh, and as you've probably already discovered, you can turn off the little pictures and audio waveforms and the timeline loading will go MUCH faster.

john-beale wrote on 5/3/2006, 10:48 PM

Right you are. I did exactly that (highlight separate sections of the timeline) and have managed to render it all out to HDV-I, which I can now assemble separately. Once I have it in the HDV-Intermediate format, everything seems to work smoothly. (The final output is m2t to tape, as that's currently my only way to play back 1080i into the client's HD projector.)

Before I was thinking that the .m2t format was slow but at least workable. Now that seems not to be the case. Vegas 6d just is not stable for me if there are too many edited chunks of m2t material on the timeline.