A Crash after 1 1/2hrs... and that was just 52%... Ouch!

Yeah, try rendering with GPU OFF.
That's the only way I can render out to MP4.

Ok, but I bought a $130 card just so I could use GPU. what the heck?? also I'm rendering at a very high bitrate of min 28mbps and max of 50mbps. I think that's why it's taking so long.

Long renders don't bother me as I'm usually asleep or doing something else while it takes place.

My Ouch! is the thought of me waking up to find that my render had crashed. Or, returning home after a couple of hours to find a crash. 3hrs would be a long time to 'babysit' a render.

As quickly evident here in the forums... GPU is not 100%.

ahh, gotcha on the ouch part. I was afraid my render time was not fast enough for GPU standards. So, you still suggest I just use cpu until it's either fixed or something? I'm kind of bumbed i spent the money on this card only to have to use cpu. It's takes a lot longer on cpu and brings my whole system to a snails pace. I can do it in the middle of the night, but often times it takes even longer than the night. like 10-15 hours and i have to work on my computer during those times.

I'm definitely not an expert on determining WHY things crash/fail. I'm the type to find a way to get it done. My workstation does not utilize GPU for anything in any program. It's just too old and too weak.

In your crash log, I see: Fault Module: C:\Windows\system32\nvcuda.dll

That tells me to turn OFF GPU. at least during rendering

Looks like your project may possibly be a Family Easter video?
If so, considering you're scared of render times and need to use your workstation in the morning... maybe you'll have to render your project in sections then piece it all together 'smart render' in the end.
-or-
start your render early
-or-
use your workstation late

You do not list any specs in your profile.
As always... I'm curious how PremierePro would run on your system?

yeah, it's a family easter video. But I also am doing more professional vids with my band and stuff too (still a hobby though). I understand it's the gpu issue. But i was even told to not get amd cards specifically for compatibility reasons and to get nvidia gforce cards with cuda to ensure it would work without issues. So i did, but I guess that's not enough. I've already put too much money into my video efforts now upgrading to vegas 11 and getting this card and even a new monitor and camera ha! So I def can't get premiere now lol. unless they have a trial which I couldn't find on their site. So far this easter video is the only one giving me issues, (which could be a good thing) but the other vids I've been working on are only 1-2 min vids with very little cuts and effects. This one has more effects and cuts involved and is 10 mins. I'll make a longer video that's different and try again and post my findings. I'll also experiment with smart rendering too. and thanks for your time!!

Suggest you monitor your CPU temperatures throughout the render as well.

cpu on the card or on my system?

Me too. Here is an exerpt from some of the support correspondence I've had with Sony Customer Service:

Update: Crashes when rendering to AVC/AAC (both Sony and Main Concept) templates still occur. The Vegas Pro 11 (build 595) software is exhibiting the same "error/fault" symptoms as did the earlier issues I identified in both Vegas Movie Studio HD 11 and VMS 11 Platmium (builds 142 and 295). I have narrowed down a work around by limiting renders to "CPU" only. The PRO 595 program recognizes that GPU acceleration is available (OPTIONS-> PREFERENCES ->VIDEO TAB ->GPU ACCELERATION -> pull down menu shows: "Advanced Micro ... inc. JUNIPER) ... as well as confirming multiple features, media generators, effects, etc. that are supported. That being said, I am appreciative of now being able to use the CUSTOMIZE features in Vegas PRO to understand how to at least dig deeper into my "crashing" issue. I intend to spend more time finding the ideal compromize for a workable .mp4 render template. As it is now, the AVC/AAC choices can only be used by forcing the ENCODE MODE of the Main Concept and Sony Memory Stick template(s) to "Render using CPU if available". Said another way, I will get "crashes" (error messages) if ENCODE MODE is in "Automatic" or "Render using GPU only. I feel better now ... but it would still be nice to be able to use the full power of my OPEN CL (Radeon HD 5770) graphics card ... :-(

Possible Alternative: If you could recommend another graphics card ... possibly a proven NVIDIA one the Vegas PRO developers designed their program around and like ... I'd consider changing my hardware platform.

"File: J:\My Movies\Vixia\family\easter.veg"J Drive? This is a real shot-in-the-dark, but I had a similar problem to this that was fixed by enabling paging on my external drive. I would have thought virtual memory would be associated with executable, but apparently not.



...Jerry

Thanks Jerry, I'll try looking into this too.

musicvid said, "Suggest you monitor your CPU temperatures throughout the render as well.Welcome back? I for one, missed your insight into all things Vegas.

...Jerry

ok, i checked the temp of the card and it was only at 48 degrees when it crashed just now. so that's not an issue b/c it's normally at 40-45 degrees while not rendering.

I'm going to change the hard drive now and see if that helps.

I also changed the directories and put the .veg and all media on the C: drive instead of J: drive and it still caused the error. I submitted a ticket with sony support. I'll let you know if they find anything out.

"I also changed the directories and put the .veg and all media on the C: drive instead of J: drive and it still caused the error"The key is to render to a drive that has paging enabled. Assume you rendered to C: as well?

...Jerry

ok, i'm going to try again just for the heck of it. I still haven't heard back from sony support on this either. it's been about a week. oh well.

I recently had a problem timeline. The issue was a specific effect combination on a specific video event. It would render to that point and then freeze every time. Slightly modifying the effect solved the problem.

In a more general sense, previous versions of Vegas have had sluggish timeline performance and rendering issues with projects that have lots of media assets (100+) and timeline events.

To avoid this I break complex videos into smaller segments, each with its own project file. I will render each segment as an MXF file and then place the mxf files into a new project for final rendering to mp4 and DVD formats. MXF (HDCAM EX preset) retains enough quality for my purposes, is very stable with Vegas, and renders to mp4 quickly.

Again, I only do this for complex projects; I've never had an issue with long projects unless they have a large number of media assets and a large number of timeline events.

3 & 1/2 days of constant crashing: GPU on/off and a variety of ram settings, all for nought.

Changed my project to 8 bit from 32 bit FP and now I can render mp4 without a problem. Yet another bug!

M

Checking in has there been an update about this?

Any word on this anyone? I have disabled GPU and still am unable to get through a render I did notice this though, when I removed my timecode track, which was on an empty event, I was able to get through the render. When I enabled the timecode track, the problem is still persisting.