"Just wondering out loud if anyone reboots before install and reboots after install?"

Yes, I do. I would think VEgas needs to know where everything is? . . . It has a devil of a time knowing this when I look for newly created Media. I need to do a refresh. Soooo... there you have it.

Grazie

So you're suggesting that people uninstall Vegas before installing 8c?

Yes, based on the fact of what happened to me. I think if people are having problems and all kinds of crashes, this procedure (uninstall 8b and reinstall 8c) must be on the top to do list.

Steve (theendisnye),

This sounds like Sony is recommending for us to not use m2ts files on the timeline and instead transcode them into .avi files. Did this work for you? Actually, what *didn't* work for you that this solves? I ask because you said you went back to 8.0b and 'it works'.

Confused,
Mike

The Saga Continues.

Tonight I got a BSOD while rendering an AVCHD file. Remember I'm using 8.0b. After that, no more AVCHD renders for me. So, I uninstalled Vegas, and installed 8.0b again. However, I didn't use my original (8.0) install disk - I simply installed the 8.0b patch. But, still no AVCHD renders for me. I get the same issue I had with 8.0c where the time keeps incrementing but the frame count doesn't and I have to use task manager to kill the Vegas process.

For now, since I have to complete this darn project, I'm rendering to "HDV 1080-60i Intermediate" as suggested by Sony to Steve. So far I've got 60% of my timeline rendered - so far, so good.

Whoa is me.....

the mp4 aav that I render for iPod touch wun get the aspect ratio right.It works for vimeo template but not for iPod.I m unsure if it is due to QuickTime update or 8.0.3. Anyone has same encounter?8.0.2 worked fine

All of a sudden I'm getting numerous glitches from my projects

Installed 8.0c over 8.0b and opened one of my projects - numerous issues with renders including random lockups from standard m2t files that originally worked in 8.0b - now that they've been opened in 8.0c, none of the projects opened in the latest version work correctly nor do they in 8.0b - which was working great once I installed the beta m2t reader dll file - but that no longer is working correctly when installed..

Did a complete restore from my acronis image which included my 8.0b install - same results.

None of my projects are working correctly that were opened in 8.0c - WTF!

If the workaround is to transcode my m2t files to AVI - I might as well reinstall my copy of PPro - since I know for a fact that works.

I don't have money to spare to go out and buy a copy of CIneform or any other app to try and resolve what is becoming a regular chain of FUBAR issues with Vegas PRo.

Yeah yeah yeah - there are those not having ANY issues - but it seems each successive release creates more problems than it resolves - that has been the case for me at least.

Too pi$$ed right now to comment any further - I believe Coonass was correct in his assessment of the issues surrounding Vegas Pro - then again, these issues have come to light since moving to Intel Q6600 and Intel Mobo - never had any issues while on AMD.

Cliff Etzel - Solo Video Journalist
bluprojekt | solo video journalism blog

64 bit vegas renders 30 minute show in 35 minutes.(dvd arch preset)
regular 8c renders same file in 22 minutes

so much for speed improvement

...or so much for insufficient information.

Could you be low on RAM?

The 64-bit version may need more RAM for code.

Which CPU are you using?

What's the CPU utilization on each core?

What are you rendering? DV/SD/HD/AVCHD/...?

"64 bit vegas renders 30 minute show in 35 minutes.(dvd arch preset)

Interesting. I get quite the opposite.

'This sounds like Sony is recommending for us to not use m2ts files on the timeline and instead transcode them into .avi files. Did this work for you? Actually, what *didn't* work for you that this solves? I ask because you said you went back to 8.0b and 'it works'.

What doesn't work for me on 8.0b is the ability to import M2TS files over 20seconds particularly those created in vegas and preserve all the attributes - some I lose the video and end up with a single audio track. Some I have the video and 1 audio track.

Steve

Latest status on my end.

I have confirmed that my older Pentium 4 computer can render AVCHD files fine with patch c (it literally takes hours though because the CPU is so slow). Looks like there is something about my new quad core computer that Vegas doesn't like. Now I get to find out what that is. Oh joy.

In the meantime, I've verified that with patch c on my new quad core I can render mpeg2, full HD (1920x1080) Blu-ray compliant files fine. So that's my work-around until I debug what Vegas doesn't like about my hardware when rendering AVCHD files.

Can anyone explain why the AVCHD codec is more sensitive to my hardware than the mpeg2 codec? I know AVCHD takes more computation than mpeg2 to produce. I certainly don't think my CPU is causing this though.

Hi,

Sad to say but I never had crashes before during editing (or rendering) in 8.0 and 8.0b, but the 8.0c crashes on me about once per edit session. This is not what I would call a complete positive development...

Just died on me with the following message:

Sony Vegas Pro 8.0
Version 8.0c (Build 260)
Exception 0xC0000005 (access violation) READ:0x6D5A0000 IP:0x77665A36
In Module 'ntdll.dll' at Address 0x77620000 + 0x45A36
Thread: VideoCache ID=0x77C Stack=0x624F000-0x6250000
Registers:
EAX=2ac80000 CS=0023 EIP=77665a36 EFLGS=00010206
EBX=1c620000 SS=002b ESP=0624f4dc EBP=0624f5bc
ECX=6d5a0000 DS=002b ESI=29be0000 FS=0053
EDX=000007ff ES=002b EDI=00000000 GS=002b
Bytes at CS:EIP:
77665A36: 8B 11 8B 78 04 3B D7 0F ...x.;..
77665A3E: 85 B1 C5 01 00 3B D6 0F .....;..
Stack Dump:
0624F4DC: 71115516 70FD0000 + 145516 (MilCore.dll)
0624F4E0: 00000000
0624F4E4: 1C620000 1C620000 + 0
0624F4E8: 29BE0020 29BE0000 + 20
0624F4EC: 0624F54C 06150000 + FF54C
0624F4F0: 776ABF7A 77620000 + 8BF7A (ntdll.dll)
0624F4F4: 77707388 77620000 + E7388 (ntdll.dll)
0624F4F8: 0624F530 06150000 + FF530
0624F4FC: 00000022
0624F500: 00000002
0624F504: 00000000
0624F508: 0624F54C 06150000 + FF54C
0624F50C: 00000000
0624F510: 1C620000 1C620000 + 0
0624F514: 1C62AA60 1C620000 + AA60
0624F518: 711155E6 70FD0000 + 1455E6 (MilCore.dll)
> 0624F524: 77707388 77620000 + E7388 (ntdll.dll)
> 0624F540: 776D2926 77620000 + B2926 (ntdll.dll)
> 0624F548: 776C17BB 77620000 + A17BB (ntdll.dll)
> 0624F564: 776CBA45 77620000 + ABA45 (ntdll.dll)
> 0624F57C: 776CBB5F 77620000 + ABB5F (ntdll.dll)
> 0624F5A0: 01010100 00400000 + C10100 (vegas80.exe)
0624F5A4: 0624F4DC 06150000 + FF4DC
0624F5A8: 0624F0C0 06150000 + FF0C0
0624F5AC: 0624F618 06150000 + FF618
> 0624F5B0: 776D2926 77620000 + B2926 (ntdll.dll)
> 0624F5B4: 00517DDA 00400000 + 117DDA (vegas80.exe)
0624F5B8: 00000000
0624F5BC: 0624F5D8 06150000 + FF5D8
> 0624F5C0: 7764F285 77620000 + 2F285 (ntdll.dll)
0624F5C4: 29BE0018 29BE0000 + 18
> 0624F5DC: 75F23593 75EA0000 + 83593 (kernel32.dll)
> 0624F5F0: 1C5A7309 1C4E0000 + C7309 (mcstdh264dec.dll)
> 0624F61C: 1C5A7848 1C4E0000 + C7848 (mcstdh264dec.dll)
> 0624F620: 1C5DBAB8 1C4E0000 + FBAB8 (mcstdh264dec.dll)
> 0624F62C: 1C51213C 1C4E0000 + 3213C (mcstdh264dec.dll)
> 0624F634: 1C4EB088 1C4E0000 + B088 (mcstdh264dec.dll)
> 0624F638: 1C5A729E 1C4E0000 + C729E (mcstdh264dec.dll)
> 0624F660: 1C5A73B6 1C4E0000 + C73B6 (mcstdh264dec.dll)
> 0624F664: 1C5A729E 1C4E0000 + C729E (mcstdh264dec.dll)
> 0624F668: 1C4ED25B 1C4E0000 + D25B (mcstdh264dec.dll)
> 0624F67C: 1C4E148B 1C4E0000 + 148B (mcstdh264dec.dll)
> 0624F688: 0F1AFC0E 0F140000 + 6FC0E (m2tsplug.dll)
0624F68C: 26220F70 26070000 + 1B0F70
0624F690: 00000000
0624F694: 4CE037C3 4BFF0000 + E137C3
0624F698: 4ACA5D90 4A7C0000 + 4E5D90
> 0624F6A8: 0F2767C5 0F140000 + 1367C5 (m2tsplug.dll)
0624F6AC: 00000001
> 0624F6B0: 0F1B3758 0F140000 + 73758 (m2tsplug.dll)
0624F6B4: 4ACA5DA0 4A7C0000 + 4E5DA0
> 0624F6B8: 0F149D40 0F140000 + 9D40 (m2tsplug.dll)
- - -
0624FFF0: 00000000
0624FFF4: 0059B990 00400000 + 19B990 (vegas80.exe)
0624FFF8: 00AE9C84 00400000 + 6E9C84 (vegas80.exe)
0624FFFC: 00000000

Can anyone make out of this anything that would give a hint what is wrong? Aarghh...

Christian

Hi again,

Just tried to render this project after it died on me and I rescued what i could by opening the autosaved version. The result was not so nice - an error occurred that is not recognized and then this error message after the application died:

Sony Vegas Pro 8.0
Version 8.0c (Build 260)
Exception 0xC0000005 (access violation) WRITE:0x8085FF7B IP:0x7764F8F4
In Module 'ntdll.dll' at Address 0x77620000 + 0x2F8F4
Thread: VideoCache ID=0xF58 Stack=0x61CF000-0x61D0000
Registers:
EAX=8085ff7b CS=0023 EIP=7764f8f4 EFLGS=00010282
EBX=1b7b7f83 SS=002b ESP=061cf590 EBP=061cf5c4
ECX=828cffdf DS=002b ESI=688ec132 FS=0053
EDX=0000828c ES=002b EDI=1b7b0000 GS=002b
Bytes at CS:EIP:
7764F8F4: 89 30 8B 45 E0 8B 55 E4 .0.E..U.
7764F8FC: 8D 7E 08 F0 0F C7 0F 3B .~.....;
Stack Dump:
061CF590: 00000000
061CF594: 01230000 01230000 + 0
061CF598: 1D85DB60 1C8B0000 + FADB60
061CF59C: 00000000
061CF5A0: 010001A0 00400000 + C001A0 (vegas80.exe)
061CF5A4: 868DFF82
061CF5A8: 828CFF83
061CF5AC: 061CF618 060D0000 + FF618
061CF5B0: 776D2926 77620000 + B2926 (ntdll.dll)
061CF5B4: 00C764EA 00400000 + 8764EA (vegas80.exe)
061CF5B8: 868CFF7E
061CF5BC: 00000001
061CF5C0: 1D85DB58 1C8B0000 + FADB58
061CF5C4: 061CF5D8 060D0000 + FF5D8
061CF5C8: 7764F26C 77620000 + 2F26C (ntdll.dll)
061CF5CC: 1D85DB60 1C8B0000 + FADB60
> 061CF5DC: 776528EB 77620000 + 328EB (ntdll.dll)
> 061CF5F0: 776528B0 77620000 + 328B0 (ntdll.dll)
> 061CF5F8: 71BF4FB6 71B40000 + B4FB6 (NetworkExplorer.dll)
> 061CF614: 006451E0 00400000 + 2451E0 (vegas80.exe)
061CF618: 061CF174 060D0000 + FF174
061CF61C: 061CF6A4 060D0000 + FF6A4
> 061CF620: 776D2926 77620000 + B2926 (ntdll.dll)
> 061CF624: 00C76CF2 00400000 + 876CF2 (vegas80.exe)
061CF628: FFFFFFFE
061CF62C: 000003C0
> 061CF630: 17802D6B 177D0000 + 32D6B (mcstdh264dec.dll)
061CF634: 54B0D010 547B0000 + 35D010
> 061CF638: 177DB001 177D0000 + B001 (mcstdh264dec.dll)
> 061CF660: 178973B6 177D0000 + C73B6 (mcstdh264dec.dll)
> 061CF664: 1789729E 177D0000 + C729E (mcstdh264dec.dll)
> 061CF668: 177DD25B 177D0000 + D25B (mcstdh264dec.dll)
> 061CF67C: 177D148B 177D0000 + 148B (mcstdh264dec.dll)
> 061CF688: 1073FC0E 106D0000 + 6FC0E (m2tsplug.dll)
> 061CF6A8: 108067C5 106D0000 + 1367C5 (m2tsplug.dll)
> 061CF6B0: 10743758 106D0000 + 73758 (m2tsplug.dll)
> 061CF6B8: 106D9D40 106D0000 + 9D40 (m2tsplug.dll)
> 061CF6C4: 1073C209 106D0000 + 6C209 (m2tsplug.dll)
> 061CF704: 1080C564 106D0000 + 13C564 (m2tsplug.dll)
> 061CF708: 1080E450 106D0000 + 13E450 (m2tsplug.dll)
> 061CF71C: 1080C33C 106D0000 + 13C33C (m2tsplug.dll)
> 061CF720: 1080C348 106D0000 + 13C348 (m2tsplug.dll)
> 061CF724: 1080E448 106D0000 + 13E448 (m2tsplug.dll)
> 061CF730: 1080643A 106D0000 + 13643A (m2tsplug.dll)
> 061CF738: 1073B86F 106D0000 + 6B86F (m2tsplug.dll)
> 061CF75C: 106F449F 106D0000 + 2449F (m2tsplug.dll)
> 061CF884: 106E9750 106D0000 + 19750 (m2tsplug.dll)
> 061CF88C: 106EA9FF 106D0000 + 1A9FF (m2tsplug.dll)
> 061CF890: 106EA6DB 106D0000 + 1A6DB (m2tsplug.dll)
> 061CF8A0: 108036B1 106D0000 + 1336B1 (m2tsplug.dll)
> 061CF8A8: 106EAABF 106D0000 + 1AABF (m2tsplug.dll)
> 061CF8C0: 106E9820 106D0000 + 19820 (m2tsplug.dll)
> 061CF8D4: 73C18A94 73C10000 + 8A94 (MSVCR80.dll)
> 061CF8E0: 106EE4C8 106D0000 + 1E4C8 (m2tsplug.dll)
> 061CF908: 106EEC8F 106D0000 + 1EC8F (m2tsplug.dll)
> 061CF918: 106E61A5 106D0000 + 161A5 (m2tsplug.dll)
> 061CF928: 106DBB6E 106D0000 + BB6E (m2tsplug.dll)
> 061CF948: 106EFD28 106D0000 + 1FD28 (m2tsplug.dll)
> 061CF984: 108037A9 106D0000 + 1337A9 (m2tsplug.dll)
> 061CF98C: 10803B51 106D0000 + 133B51 (m2tsplug.dll)
> 061CF994: 106F59B7 106D0000 + 259B7 (m2tsplug.dll)
> 061CF9F4: 10803C36 106D0000 + 133C36 (m2tsplug.dll)
> 061CFA00: 006B583B 00400000 + 2B583B (vegas80.exe)
061CFA04: 111B1C40 11110000 + A1C40
061CFA08: 00000331
061CFA0C: 00000000
061CFA10: 061CFA40 060D0000 + FFA40
> 061CFA44: 75EBD71D 75EA0000 + 1D71D (kernel32.dll)
> 061CFA74: 01AEB664 01A30000 + BB664 (vegas80k.dll)
- - -
061CFFF0: 00000000
061CFFF4: 0059B990 00400000 + 19B990 (vegas80.exe)
061CFFF8: 00AE9C84 00400000 + 6E9C84 (vegas80.exe)
061CFFFC: 00000000

THIS IS NOT NICE - I'm considering going back to 8.0b !!! !!! !!!

Christian

PS: Needless to say how disappointed I feel...

Access Violations are usually when one program tries to write/read a block of memory that is being used by something else. It could be another software or a driver.

Finding the violation tends to be a bit of trial/error. Strip your computer down to nothing but what it ABSOLUTELY needs to operate. Kill all drivers, all software.... everything that you can then try another render. If you render fine then add things on until your renders start crashing.

Blink, thank's for cheering me up. The stupid thing is that this is EXACTLY the same setup and same project, that worked perfectly in 8.0b. The problems started after the upgrade, and nothing else has been installed or removed...

Ok, next i try KillThemAll... wonder if it works on Vista 64, but we'll see...

Christian

Hmm,

I tried to open the exactly same problematic .veg file in 8.1 without doin ANY editing or even touching the timeline.

Surprise - 8.1 renders it without a problem, 8.0c stumbles exactly at frame 0, every time. Both are selected to render a 1920x1080i PAL project to the same Blu-ray Mpg2 template.

The playback on the timeline works in both versions of Vegas with no problems...

What kind of conclusions can we make tof this ???? 8.1 is more stable and works even if there is somewhere a glitch in the timeline (that Vegas caused by itself - not me)?? Or what do you think?

Glad to solve my problem at least for now, but I'm confused. This at least provea that 8.0c and 8.1 is not coming from the same codebase, but we already knew that didn't we, because of some lacking features in 8.1, that are new in 8.0c...?

Christian

Vegas 8.0c did not fix my 32-bit rendering issue. I open the project in 8.1 and render - no problem whatsoever. My conclusion is that 8.1 has better memory management/access to more memory and it should being 64-bit.

8.1 is not without issues, but I use it preference.

So would I too, but not a single plugin I have and need works in 8.1. That renders 8.1 useless for most of my work for now.

Sad that there were no migration phase possible(?) here for 32 bit plugins (that worked well in 64 bit windows with 32 bit Vegas) to work also in 64 bit Vegas...

Christian

Man I am glad I am still in the SD world maybe by the time I am ready for HD things will be worked out. I still Love Vegas though even with its problems.

Paul B

Just investigated further.

I noticed that 8.0c crashes every time at the first frames of a render if I render out my project as BluRay 1920x1080 50i.

If I rendesr to Mpg2 PAL 50i wide, it works flawlessly!!! 8.1 works both ways.

There is something wrong in the render to HD in 8.0c for sure... Or can you assume that with this thin proof?

Christian

I have been having the exact same set of problems. My system runs windows vista. I was able to render avchd files from my canon hf 10 with the 8b 1440x1080 sony template. However, since my camera records in 1920x1080, I was excited to try out 8c that should support this. I get the same problems as you: 1) vegas disappears during the render, 2) stack trace or 3) stuck frame count. I've given a test file to the tech support but haven't heard back. It seems like others are having some problems with 8c aw well

http://forums.creativecow.net/thread/24/883935#883935

I have had to revert to 8b and go back to the 1440x1080 template. In 8c, the 1920x1080 sony, 1920x1080 bluray, and 1440x1080 sony all crash at random times during the render.

My machine is a dell quad core 2 duo with 4 GB ram as well. I noticed that 8b used less memory and more cpu that 8c. Also 8c's memory usage keeps increasing during the render. Not sure if this means there is a memory leak...

I have no answers yet. Have you figured anything out?

Thanks.

My PC:

XP 32bit
Intel Q6600 Quad
3 Gigs RAM


I have rendered 3 projects with 8C. Every single one has rendered but only after fighting with Vegas 8C tooth and nail on every one.

I have been sucessfull on prolly only 1 out of every 8 attempts.

All my sucessfull attempts were done using 1 processing thread. (along with various other setting changes with RAM.... and lots of prayer)

I love Vegas way too much to leave it. I'm in it for the long haul and I have faith that they are will get this thing fixed.

I HAVE TO BELIEVE THAT THE VEGAS DEVELOPMENT TEAM IS ABLE TO RECREATE THESE RENDERING PROBLEMS IN THEIR LABS.

Guys I hope you are reading these threads and start using US as public beta testers for 8D in the future.

CT