Yeah... I got no choice... I'm back in the EXACT same mess that caused me to revert to 7d :(

Here we go with the crash on render:

Problem signature:
Problem Event Name: APPCRASH
Application Name: vegas80.exe
Application Version: 8.0.0.144
Application Timestamp: 46cb310a
Fault Module Name: vegas80.exe
Fault Module Version: 8.0.0.144
Fault Module Timestamp: 46cb310a
Exception Code: c0000005
Exception Offset: 0043b7e7
OS Version: 6.0.6000.2.0.0.256.1
Locale ID: 1033

Again... this section of video renders fine in 7d

It looks to me that what ever was causing the 7e crashes has been carried on to 8. If this is the case.... I've just WAISTED some money and will have to return to 7d.

nah dude, its not a waste..
youve got smartrendering in long GOP.. that in itself is enough to pay itself off with the time you save..

"nah dude, its not a waste..
youve got smartrendering in long GOP.. that in itself is enough to pay itself off with the time you save.. "
==============================================

Not a stick of good if it's crashing very (on average) 3minutes during render.

I guess I'll go back and try the Vegas capture program and see if that helps. But then again, I switched over to HDVsplit because the vegas capture was scene splitting one frame late every time. That's a lot of manual correcting to do in a video with 200 or more scenes.

After capturing HDV footage and dragging clips into the timeline...Error, Vegas has to shut down.
This has happened on 2 machines, one running 7e and the other Pro 8 on the last few sessions I have uploaded (high school football games).
Need help, need to get the game films edited!
It sounds like we are having similar problems.

Yup.

I complained loudly about the crashing in 7e and it LOOKS like it was ignored and the problem has been carried into Version8. I returned to 7d and the problems went away... maybe it will be the same with you.

But in any event you NEED to file an official problem with the tech people with the above link. If more people go on record with this, then maybe it can be cleared up a bit faster.

When you write the tech guys... give them a link to this thread. The NEEDS to be cleared up... everything (for me anyway) is useless beyond 7d

I agree; everyone experiencing an issue needs to file an official report with the tech support people.

Still, I'm left wondering if they ever check the board here. A quick glance at thread titles should give them a clue regarding problems with the most current build. I mean, when you see topics such as "V8Pro Exit Error", "Vegas Pro has stopped working", "Surprise! Vegas 8 problem", "V8 - HDV Capture Problems", not to mention the title of this thread, I'd like to think that would be sufficient even in the absence of official reports.

"Still, I'm left wondering if they ever check the board here."
======================================================
It seems tome NOT, because there were quite a few threads regarding 7e crashes with HDV render. That's why I feel it's important to start emailing tech support directly with this stuff.

I submitted the problem to Tech Support

Being a curious person that I am, I uploaded the same clips onto a Mac and Final Cut...not one problem. I'm just not ready to make that jump to Mac just yet, but if this problem cannot be fixed then I will be forced to.

Blink, you and Prius are the only two on this thread that show your system specs. Both of you use intel proc's and both have Creative brand cards in your system.

I believe I remember reading somewhere in the past that there were issues with creative pci cards- I could be wrong about that.

I do not use creative products nor do I currently use intel cpu's. I do not have the issue you are experiencing.

If it is easily doable, try removing your creative card/driver and see if that has anything to do with it.

j razz

Right at the top of the forums page it says, "We monitor these boards periodically. However, if you require immediate technical support, please choose from the options on our Support Home Page."

Do NOT, I repeat, do NOT rely on these forums for individual tech support from Sony.

jrazz wrote:

"I believe I remember reading somewhere in the past that there were issues with creative pci cards- I could be wrong about that."

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

Good thought, I think, but it appears as if several other members with non-Creative brand cards are having the same "crash on exit" issue. They are running the latest version of SVMS rather than Vegas Pro 8 but it's a bit strange that the issue is precisely the same and the system specs vary widely.

Also, fwiw, I did not experience this (or any other anomaly) running Vegas 5 and 7 on the same system.

"I do not have the issue you are experiencing.

If it is easily doable, try removing your creative card/driver and see if that has anything to do with it. "
===========================================================
Not that I don't appreciate the suggestion, believe me. Maybe someday when I have little to do, I'll try something like that. But if I thought it had anything to do with my system, I would for sure strip it down and re-do it... but I'm pretty sure it's not the system.

Version7 through to 7d are rock solid... I have no problems. This is in BOTH XP and Vista64. It is with 7e that the problems started.... and it is identical wit XP and Vista64

I even took the "problem" clips over to 7d in BOTH xp and Vista64... and no problems at all. Bring the clips back to 8, and crash crash crash...EXACTLY the same as 7e

So I'm 99.9% sure that they have changed SOMETHING from 7e on. IF you go back and look at the threads of the past, you will also notice an increase in crash complaints... now that could mean anything... but it is interesting.

Right. I am not denying that it is not an issue with Vegas. But, I am denying it is completely Vegas. If it was just Vegas, everyone would have this problem. Therefore, it must be Vegas+something. You have ruled out the OS so we know it is not that. The only other thing it could be is the Vegas/hardware/driver combo specific to the systems that are experiencing this. I don't know what it would be as I do not have the problem you do. I think the best way to get a good grip on the issue is to have everyone who is experiencing this problem to list their specs and see what the common thread is. That is just a suggestion, but I think it would give a lot of info to Sony to correct the issue on their end as well as the optional possibility of you doing a work around on yours.

j razz

I'm curious as to how many are experiencing the crashes with Intel versus AMD setups...

I just upgraded to VP8 on my AMD 3800+ X2 with 4GB Matched RAM running x64 XP Pro and I have found it to be much faster and as stable as V7.

I'm still holding out on moving to HDV due to the many issues related to editing HDV, so my standard def footage is not causing any issues.

Cliff Etzel
bluprojekt

"I'm still holding out on moving to HDV due to the many issues related to editing HDV, so my standard def footage is not causing any issues."
==============================================
It is the scene split HDV that is causing the problems... DV works fine.

Granted, my HDV has been captured and scene split by HDVsplit... but then again... it works great in 7d.

I'm going to try the Vegas capture/program again and see if that makes a difference.... but like I said above... I switched over to HDVsplit because the Vegas scene split was splitting one frame late all the time.

"But, I am denying it is completely Vegas. If it was just Vegas, everyone would have this problem. "
======================================================
I can't say at this point that it is COMPLETELY vegas either since the clips were captured by HDVsplit... NOT vegas itself. But what I CAN say is that SOMETHING changed between 7d and 7e, because HDVsplit works fine with 7d.

I use HDVSplit as well without issue most of the time. When I use Vegas 7 and capture I get scenes that are split at wrong frames.

j razz

Okay... here's the scoop.

I used the Vegas capture program in version 8 to captur 8 minutes, 55 seconds of HDV (64 scenes)

I was a little bit nervous about forward compatibility so I took the clips BACK to 7d and put together a simple timeline with dissolves. It was rendered as 1080/60i, "best" 19M, audio: 48000, 384 M2V/MPA

7d rendered without issues in 14:15

I took the same project over to 7e... render was incomplete (crashed) at 11:28 and at frame 12,079.

The crash report:

Description:
Stopped working

Problem signature:
Problem Event Name: APPCRASH
Application Name: vegas70.exe
Application Version: 7.0.0.216
Application Timestamp: 4637061c
Fault Module Name: sonymvd2pro_xp.dll
Fault Module Version: 1.0.0.0
Fault Module Timestamp: 44a3c9ea
Exception Code: c0000005
Exception Offset: 00044778
OS Version: 6.0.6000.2.0.0.256.1
Locale ID: 1033

I then took the same project over to Vegas8... render was incomplete. Crashed at 8:02 at frame 12,082 (note the time difference between 7e and 8.... that's the smart render!!)

The Vegas 8 crash report:

Description:
Stopped working

Problem signature:
Problem Event Name: APPCRASH
Application Name: vegas80.exe
Application Version: 8.0.0.144
Application Timestamp: 46cb310a
Fault Module Name: sonymvd2pro_xp.dll
Fault Module Version: 1.0.0.0
Fault Module Timestamp: 44a3c9ea
Exception Code: c0000005
Exception Offset: 00044778
OS Version: 6.0.6000.2.0.0.256.1
Locale ID: 1033


Take note that the crash reports are pretty close to identical.

The crashing is not near as bad with Vegas capture as with HDVsplit... but it's still there.

And here's something really neat.... frame 12082 is a scene split... 7e crashed at 12079, (12,079 being the REAL spot that should have been split). There is 3 frames difference between those 2 numbers. It just so happens that the Vegas capture program (for me anyway) is 3 frames late in splitting a scene.... coincidence???

Maybe a bit different in my case: ever since I installed V8 trial, working in V6 has been hampered. Slow and then crashes. I'm not even working in HD, just basic 640x480.

Until I decide to get the actual V8, it's outta here, now un-installed. I've got work to do.

Interesting note...

I captured the same footage through Vegas8 capture WITHOUT scene split. I put the entire clip on the timeline and di a manual scene split, and it rendered fine. So IMO... Vegas 7e AND 8 is having some kind of trouble scrubbing over and rendering automatic scene splits. Now whether this is the scene split subroutine, or Vegas itself sausing the problems... I do not know.

Yup..

It most DEFINITELY has something to do with the scene splitting NOT being accepted in 7e and 8... but it IS accepted by 7d

I ran short capture and isolated one automatically split scene that neither 7e or 8 will accept... it crashes them both. This same scene works fine in 7d. When I capture this SAME footage without scene detect (place it on the time line and manually cut the scene) it plays/renders fine in 7e and 8

The automatically split scenes with the Vegas capture program are not being rejected as frequently as with HDVsplit... but still... there are some that ARE being rejected (resulting in a crash) and all it takes is ONE to ruin a 3 or 4 hour render.

Blink, please check your email.

-Vegas Dev