Just a couple of randome thoughts....

Have you considered uninstalling and re-installing? If you are having that many random problems then quite possibly the install was hosed in some way. If you are using a downloaded file to install, maybe the download is corrupt?? Did you use any custom file locations when installing? (always use the defaults if at all possible)

Have you noticed any other problems with your computer in general....maybe hardware related in some way?? (failing hard drive, bad RAM stick, graphics card, etc)

Is it possible to install on a different computer and just see how it works on it (just to help you and others narrow down if it is computer related, media file related, or software related)?

I've also been using Vegas 8 with no problems.....just as stable as any other version in my case. I've been using it on my main computer and also 2 different laptops with no problems.

Good luck.

havent had an issue so far... been testing it on my laptop but one thing i have learnt with all sony apps, is to NEVER uninstall anything... not only do u nuke ur chances of going back and using a working copy to finish whatever project ur on, but you never what other elements, filters, plugins, settings u might loose by uninstalling.
I usually do system restores, and at the first sign of trouble, i run a system restore toa point before the V8 installation. This way I dont lose anythign critical

Doesn't a system restore just re-install a bad install?
JJK

I've had a problem come up recently where Vegas 8 crashes while rendering projects with JPEGs. No rhym or rreason to it, but even if I convert the JPEGS to PSDs, it still crashes while trying to render. And if I put those pic files with any other video, it crashes. But if I put them on a timeline and render them out by themselves, it works fine (that's been my workaround). A fresh install hasn't helped. It all started when I got an error message during playback, so I think there is some glitch that might be tied to the registry (or whatever else isn't "uninstalled" when you uninstall the app).

Until this happened lately, I was fine with V8.

"Doesn't a system restore just re-install a bad install?"

No because the system restore point was set BEFORE the installation took place.
Form there is u have issues, u can run a registry check/clean or jsut revert back to V7 the way it was before u installed v8

Well, I've just spent the last three or four hours (it's 2am over here) uninstalling everything ... and reinstalling everything and I've just tried another render ... just a simple wmv 13 minutes long ... this time it got to 10% and has just stopped ... not in exactly the same place as before... sometimes it's 30% ... sometimes elsewhere ... I've had the same thing while trying to render m2t's ... DVD Mpegs ... wmv's etc ... and they're always random places Vegas stops OR ... simply gives me an exception error ... or similar.

I've had enough of this. Thanks for all your suggestions. Can't go back to 7 because it's not compatible with the project file and I've done way too much work on the project to restart now ... I've simply been soldiering on hoping things would get better but this is a joke.

Darren Powell

Darren - sorry to hear of your problems. What kind of footage are you putting in the timeline? I had some major problems rendering 1080i 24p footage awhile back but other than that everything that I've thrown at V8 has worked fine.

And I hope you were kidding about going to AVID...unless you REALLY want to get frustrated.

Darren, are you working on a 32 bit timeline or an 8 bit timeline? I have a lot of the same issues when i try to render out a long 32 bit timeline but I switch the project setting to 8 bit and it renders fine... try it for a test and if it is the same for you then we really need to get sony to step up and fix this!! Good luck man!! PS, vegas is still the most versatile editor on the market they just need to make it stable again!!

I haven't tried it but it seems to me that the nearest way to regress a project back to V7 might be to export an AAF file from V8. I'm sure you'd lose a bit in the process though.

At my place of employment we had horrible problems with PPro over the last year and our mantra to our system integrator, Matrox, and Adobe has been "Take it all back, we're moving to Avid".

We were able to get direct phone numbers for people at Adobe and Matrox, I'd hope you could do it with SCS, but it'd be good if they could somehow set up a Skype line for the overseas people

In the end we installed a single FCP system to deal with a long form doc coming up because nothing else could reliably deal with DVCProHD from tape. (Vegas has never been a real consideration at work).

Rob Mack

Darren,

You're not the only one having render problems. I had horrible problems with the first version. 8.0a has been better but I still get renders that go on forever (the system does not even know it crashed it just keeps counting). I'm using Cineform Neo files so it's not only M2t. One workaround I'm using that works fairly well for me is to render out small sections to a new track in the format I'm working in (HDV project intermediate files). Then when I'm ready to render to MPEG I save a new project and delete all of the other tracks except the final render track. I clear the project bin and then restart the computer. Then I reopen that project and render. Works most of the time but still hangs sometimes.

I would stay away from JPEG is possible (I convert to PSD) and you might try lowering your graphics card acceleration as well. I'm also using a quad core and Vegas 7 never had these types of problems on lesser systems. Though I did not edit HDV projects on V7 which is probably where the problem lies. 32 bit rendering absolutely never works for me which is a shame and I hope they fix that someday..

Regards,

Marc

i agree with the previous post on changing the project setting to 8 bit. I have renders that did not work in the past and in all cases changing the project to 8 bit corrected the failed render. I think Sony has some work to do around that setting.

Hi everyone and thanks for your encouragement!

Marc's post is EXACTLY the same problem as I'm having. Thanks Marc for the info.

Here's the problem as I see it.

Firstly, I have been using Cineform NEO. The last version of Connect HD was stable then I 'upgraded' to NEO and all hell broke loose. Clips would be capture in tiny little pieces, lots of digital breakup with the clips that did work ... problems problems problems.

So, I quite using NEO and just left the Cineform codec to deal with the files that were useable in the project. Cineform support told me that my system must have a 'bottleneck' but that's not possible because I can capture hours of m2t straight off my HDV tape without a single dropped frame! The only reason I was using Cineform was because the file sizes are smaller and do seem to be visually lossless ... plus I can flip my M2 adapter footage on the way in to my machine. Now that I've stopped using NEO I simply capture my M2 footage as m2t's and I have an 'upside down' track in Vegas which flips the footage right way up again ... (the M2 adapter records the footage upside down in the camera ... it's just the way it works ... nice footage though!) ... welcome to my nightmare. I've requested that Sony put a check box in Vegas Capture to allow M2 users to flip their footage on the way in ... would be a handy little feature for people like me.

So, yes Marc, I think the problems we're having are a combination of HDV (no I've never been able to use 32 bit either ... simply doesn't work which is, as you say, a real shame) and possibly the NEO captured files ... along with inherent instability in 8.0a of Vegas.

I like your workaround for rendering. I'm going to try printing to tape today ... and then recapture the vision from the tape as a single m2t ... then mix the 5.1 into that and try exporting from there. Any export would be good right now.

Cheers,

Darren

OK, I just tried Print to Tape and here's the result:

Anybody seen this kind of thing before? Happens to me all the time.

The only difference is that the Exception happens in different modules depending on what I'm trying to do. For example the following dump shows an exception in 'MSCTF.dll' following my attempt at a print to tape ... but if I'm trying to render in other ways I can get errors in the Cineform dll (CFHD.dll or whatever it is) and the NT kernel etc etc etc. Very random ... HELP!!

Darren

-------------------------------------------------------------------------

Sony Vegas Pro 8.0
Version 8.0a (Build 179)
Exception 0xC0000005 (access violation) READ:0x0 IP:0x74750C22
In Module 'MSCTF.dll' at Address 0x74720000 + 0x30C22
Thread: ProgMan ID=0x1604 Stack=0x3724000-0x3730000
Registers:
EAX=00000000 CS=001b EIP=74750c22 EFLGS=00010246
EBX=00000000 SS=0023 ESP=03724b6c EBP=03724b74
ECX=3cc30000 DS=0023 ESI=3cc37358 FS=003b
EDX=3cc37606 ES=0023 EDI=00000000 GS=0000
Bytes at CS:EIP:
74750C22: 8B 08 3B CB 74 1F 39 99 ..;.t.9.
74750C2A: 80 05 00 00 74 17 50 E8 ....t.P.
Stack Dump:
03724B6C: 3CC37358 3B0C0000 + 1B77358
03724B70: 00000000
03724B74: 03724BA4 03630000 + F4BA4
03724B78: 7473C783 74720000 + 1C783 (MSCTF.dll)
03724B7C: 04090C09 03FC0000 + D0C09
03724B80: 00000000
03724B84: 03724C10 03630000 + F4C10
03724B88: 3CC3FE08 3B0C0000 + 1B7FE08
03724B8C: 000085DE
03724B90: 03724BA0 03630000 + F4BA0
03724B94: 7473C2A3 74720000 + 1C2A3 (MSCTF.dll)
03724B98: 03724C10 03630000 + F4C10
03724B9C: 06370FA0 06110000 + 260FA0
03724BA0: 000085DE
03724BA4: 03724BB4 03630000 + F4BB4
03724BA8: 7473D066 74720000 + 1D066 (MSCTF.dll)
> 03724BB8: 747286AE 74720000 + 86AE (MSCTF.dll)
> 03724BC0: 747275F0 74720000 + 75F0 (MSCTF.dll)
> 03724BCC: 7473D36B 74720000 + 1D36B (MSCTF.dll)
> 03724BDC: 7473D793 74720000 + 1D793 (MSCTF.dll)
> 03724C00: 7473FBB0 74720000 + 1FBB0 (MSCTF.dll)
> 03724C0C: 7473FB2E 74720000 + 1FB2E (MSCTF.dll)
> 03724C18: 7473F99E 74720000 + 1F99E (MSCTF.dll)
> 03724C2C: 68432E46 68210000 + 222E46 (QuickTimeH264.qtx)
> 03724C58: 74725502 74720000 + 5502 (MSCTF.dll)
> 03724C9C: 7472FCD5 74720000 + FCD5 (MSCTF.dll)
> 03724CAC: 74730238 74720000 + 10238 (MSCTF.dll)
> 03724CBC: 7E41F896 7E410000 + F896 (USER32.dll)
> 03724CD4: 74730E6C 74720000 + 10E6C (MSCTF.dll)
> 03724CE4: 74730E71 74720000 + 10E71 (MSCTF.dll)
> 03724D08: 7475E548 74720000 + 3E548 (MSCTF.dll)
> 03724D0C: 74730E78 74720000 + 10E78 (MSCTF.dll)
> 03724D14: 74730E71 74720000 + 10E71 (MSCTF.dll)
> 03724D18: 7E41F84A 7E410000 + F84A (USER32.dll)
> 03724D34: 7E418734 7E410000 + 8734 (USER32.dll)
> 03724D48: 7473F99E 74720000 + 1F99E (MSCTF.dll)
> 03724D58: 7473F99E 74720000 + 1F99E (MSCTF.dll)
> 03724D60: 7E418816 7E410000 + 8816 (USER32.dll)
> 03724D64: 7473F99E 74720000 + 1F99E (MSCTF.dll)
> 03724DB8: 7E440457 7E410000 + 30457 (USER32.dll)
> 03724DBC: 7E418830 7E410000 + 8830 (USER32.dll)
> 03724DC8: 7E4189CD 7E410000 + 89CD (USER32.dll)
> 03724DD0: 7473F99E 74720000 + 1F99E (MSCTF.dll)
> 03724DF8: 7E4185A4 7E410000 + 85A4 (USER32.dll)
> 03724E18: 7E440457 7E410000 + 30457 (USER32.dll)
> 03724E1C: 7E4189F0 7E410000 + 89F0 (USER32.dll)
> 03724E28: 7E418A10 7E410000 + 8A10 (USER32.dll)
> 03724E38: 7E42DBBF 7E410000 + 1DBBF (USER32.dll)
> 03724E70: 7E42593F 7E410000 + 1593F (USER32.dll)
> 03724E98: 7E425981 7E410000 + 15981 (USER32.dll)
> 03724E9C: 00400000 00400000 + 0 (vegas80.exe)
> 03724EA0: 01444328 01150000 + 2F4328 (vegas80k.dll)
03724EA4: 00000000
> 03724EA8: 01213B20 01150000 + C3B20 (vegas80k.dll)
03724EAC: 03724F4C 03630000 + F4F4C
03724EB0: 00000001
03724EB4: 03724ED4 03630000 + F4ED4
> 03724EB8: 7E43204D 7E410000 + 2204D (USER32.dll)
> 03724EBC: 00400000 00400000 + 0 (vegas80.exe)
> 03724EC0: 01444328 01150000 + 2F4328 (vegas80k.dll)
03724EC4: 00000000
> 03724EC8: 01213B20 01150000 + C3B20 (vegas80k.dll)
- - -
0372FFF0: 00000000
0372FFF4: 00525180 00400000 + 125180 (vegas80.exe)
0372FFF8: 00AD8658 00400000 + 6D8658 (vegas80.exe)
0372FFFC: 00000000

Here's another dump .... trying to render to a .wmv. This time it's in module 'Vegas80.exe' ... I don't really want to know what all this means ... I just want to be able to render the first 13 minutes of my project.

Darren

------------------------------------------

Sony Vegas Pro 8.0
Version 8.0a (Build 179)
Exception 0xC0000005 (access violation) READ:0xFF3B2E44 IP:0x6AF6FE
In Module 'vegas80.exe' at Address 0x400000 + 0x2AF6FE
Thread: ProgMan ID=0x1644 Stack=0x372F000-0x3730000
Registers:
EAX=3ce913a8 CS=001b EIP=006af6fe EFLGS=00010202
EBX=0204dc80 SS=0023 ESP=0372f320 EBP=00000070
ECX=ff3b2e20 DS=0023 ESI=689f6160 FS=003b
EDX=69001be8 ES=0023 EDI=001d0010 GS=0000
Bytes at CS:EIP:
006AF6FE: 8B 41 24 FF D0 85 C0 74 .A: 0B 83 C5 01 3B 6C 24 10 ....;l
Stack Dump:
0372F320: 3CE913A8 3B0C0000 + 1DD13A8
0372F324: 69001BE8 68810000 + 7F1BE8
0372F328: 69001BE8 68810000 + 7F1BE8
0372F32C: 8B635415 80000000 + B635415
0372F330: 0326E270 03180000 + EE270
0372F334: 3A1C7824 3A0C0000 + 107824
0372F338: 000001B5
0372F33C: 00000009
0372F340: 00000001
0372F344: 00000000
0372F348: 001D001C 00140000 + 9001C
0372F34C: 006A7D9E 00400000 + 2A7D9E (vegas80.exe)
0372F350: 69001BE8 68810000 + 7F1BE8
0372F354: 00000000
0372F358: 6916BD78 68810000 + 95BD78
0372F35C: 0326E270 03180000 + EE270
> 0372F360: 006A8AFD 00400000 + 2A8AFD (vegas80.exe)
0372F364: 3A1C7824 3A0C0000 + 107824
0372F368: 8B635415 80000000 + B635415
0372F36C: 6916BD78 68810000 + 95BD78
0372F370: 00000000
> 0372F384: 006C4ECA 00400000 + 2C4ECA (vegas80.exe)
0372F388: 3A1C7824 3A0C0000 + 107824
0372F38C: 8B635415 80000000 + B635415
0372F390: FFFFFFFF
0372F394: 6916BD58 68810000 + 95BD58
> 0372F3A8: 006C51FB 00400000 + 2C51FB (vegas80.exe)
0372F3AC: 00000000
> 0372F3B0: 006C52A7 00400000 + 2C52A7 (vegas80.exe)
0372F3B4: 3B0A7664 3A0C0000 + FE7664
0372F3B8: 6916BD48 68810000 + 95BD48
> 0372F3BC: 006C53A0 00400000 + 2C53A0 (vegas80.exe)
- - -
0372FFF0: 00000000
0372FFF4: 00525180 00400000 + 125180 (vegas80.exe)
0372FFF8: 00AD8658 00400000 + 6D8658 (vegas80.exe)
0372FFFC: 00000000

Darren, you are certainly not alone. I posted a while back with Vegas 7 when I found I couldn't render WMV HD files more thatn 2.5 minutes in length. Then I found similar crashes (hard reboot required) trying to render any HD format more than 3 minutes in length. I also found some projects with JPEG images (especially 8 megapixel or higher images) would crash the renders as well. I hope the Sony Vegas gurus are reading this post as this is a real problem for a lot of people. You won't notice it until you try to render to HD quality output so since most of us produce still in DVD quality, it may not be on a lot of people's radar (yet).

Another note, I lowered the dynamic RAM settings and that seemed to allow me to render m2t files and MOV HD files successfully. I suspect there is a memory leak problem going on here.

Note: I have the same exact problem on my laptop system which is running Vista with WMP 11. Same issue, two very different systems.

Mike Tuggy

I have had big problems with jpeg's as well and have found that you have to keep them below 7 or so megs.

I have also had problems rendering m2t.... especially m2t that has been captured from other capture programs.

Vegas 8 seems to work best if you capture as one long m2t stream (in other words scene detect off) and manually clip the scenes on the timeline. It's longer and more of a pain in the ass, but I find that this reduces the crashes to near zero

Thanks Mike,

Yes, it's nice to know you're not alone.

This instability is not acceptable from Sony. I have a major project underway and I need to be able to render.

If anyone has any ideas regarding getting a HD render out of Vegas Pro 8 for a large project please let me know.

Cheers,

Darren

Have you tried breaking the project into smaller sizes?

Break it into smaller chunks, render each chunk then render those chunks through as one. It may be slow and painful but it could get you through this one.

The other thing I have done before is I've taken all the bits and pices of various crashes and stitched them together. In otherwords... if it crashes at frame 5000 then I will start my next render at 5001 until it crashes again at say... 10500. Istart the next render at 10501.... etc.

In the end i'll take all the pieces, put them together and render them as one. It's long and tedious but it has gotten me through a few crunches in the past.

Thanks Blink3Times ... I can't even get Vegas to render a minute and half at the moment ... really weird ... and really scary.

I just tried rendering to 720 HD a minute ago and Vegas got to just over and minute and just disappeared off the screen! No error message ... nothing.

I'm running a quadcore box, as much RAM as you can stick in it ... Terrabytes of HD space on a couple of SATA Raids ... GeForce 7900 Series card outputting at high res through a Matrox TripleHead2Go box ... perfectly stable ... surround vision and sound ... and everything in my universe would be perfect if I could just render the &*%$###% project...

I'm seriously considering sueing Sony for lost productivity ... this is ridiculous ... they can afford it ... but I can't.

Darren

Latest render trying to render to DVD.

Darren Powell

-----------------------------------------------------------------


Sony Vegas Pro 8.0
Version 8.0a (Build 179)
Exception 0xC0000005 (access violation) READ:0x0 IP:0x0
In Module 'vegas80.exe' at Address 0x0 + 0x0
Thread: ProgMan ID=0x17D8 Stack=0x377E000-0x3780000
Registers:
EAX=00000000 CS=001b EIP=00000000 EFLGS=00010212
EBX=38819e48 SS=0023 ESP=0377edec EBP=0377ee18
ECX=9d3155ca DS=0023 ESI=78134d09 FS=003b
EDX=00000000 ES=0023 EDI=0377eedc GS=0000
Bytes at CS:EIP:
00000000: .. .. .. .. .. .. .. .. ........
00000008: .. .. .. .. .. .. .. .. ........
Stack Dump:
0377EDEC: 2C4CB4C9 2C4C0000 + B4C9 (mcmpgmux.dll)
0377EDF0: 38819E48 38600000 + 219E48
0377EDF4: 00000000
0377EDF8: 000605F8 00030000 + 305F8
0377EDFC: 00000000
0377EE00: 33BCD9D7 33BB0000 + 1D9D7 (mcplug.dll)
0377EE04: 365862A0 364F0000 + 962A0
0377EE08: 0377F2B8 03680000 + FF2B8
0377EE0C: 6D9A0028 6D9A0000 + 28
0377EE10: 001C0000 00140000 + 80000
0377EE14: 00000000
0377EE18: 00000078
0377EE1C: 33BC94DB 33BB0000 + 194DB (mcplug.dll)
0377EE20: 33BC2100 33BB0000 + 12100 (mcplug.dll)
0377EE24: 0377EEDC 03680000 + FEEDC
0377EE28: 3BC14668 3A0C0000 + 1B54668
> 0377EE34: 78180A9B 78130000 + 50A9B (MSVCR80.dll)
> 0377F19C: 201D1B1A 20000000 + 1D1B1A (xpsp2res.dll)
> 0377F2B8: 003A0044 00360000 + 40044 (sfwbdmux.dll)
> 0377F2BC: 0046005C 00400000 + 6005C (vegas80.exe)
> 0377F2C0: 00410045 00400000 + 10045 (vegas80.exe)
> 0377F2C4: 00550054 00400000 + 150054 (vegas80.exe)
> 0377F2C8: 00450052 00400000 + 50052 (vegas80.exe)
> 0377F2CC: 00540020 00400000 + 140020 (vegas80.exe)
- - -
0377FFF0: 00000000
0377FFF4: 00525180 00400000 + 125180 (vegas80.exe)
0377FFF8: 00AD8658 00400000 + 6D8658 (vegas80.exe)
0377FFFC: 00000000

well, using straight m2t (from v1p), @ 8bit, and converting all my stills to png - i've completed numerous short form programs, and three 1hr plus doco's.

i had some issues with 8, but 8a seems to have cleared them up. one thing i did find, and notified sony about was:

using 'no-recompress' produces an 'illegal' stream that WONT print back to tape. turning off no-recomp gives a printable file.

i'm sorry you're experiencing so many problems, but i tend to think like others that it could well be hardware / bad install related. since you've done a clean reinstall, i'd be checking for bad memory...

good luck, and having come from avid, i'd certainly think twice before going back!

leslie

Hang in there Darren.

We have grown so accustomed to our technolgy these days, that it drives us to insanity when it turns on us. I have had a couple of similar days this week myself. I cannot offer up advice to pull you out of your jam, but I can say this.........the only reason I chose Vegas was because of this forum and the people involved with it. It is obvious that you take pride in your work and know a thing or two about what you are doing. This forum is full of people just like you. I have seen them volunteer so much time and effort to resovling issues that I felt they should present a bill and appear in the project credits. This site is full of genuine kind people that truly enjoy helping.

I hope this post reaches you with a fully rendered 13 minutes in hand.

Take a deep breath.

All the best, Joe