Can I ask how big your page file is (and how much RAM?). Also, how many threads are you running at? Tweaking those may fix your problem.

Mike

Well, I tried nesting it, that was a great idea. It was slow as molases, but everything was going well, then it just frooze.

I transfered the project to another computer, crash, crash, crash!

I have 4 gigs of RAM total, on both machines. The first machine is a quad core, and it looks like all four threads are running during render. How would I tweak that? The second machine is a dual-core.

Thanks for your help!
kairosmatt

Have you checked your project and render audio to make sure they are at 48k instead of the 44.1 mentioned in the error.

Dave T2

Try this:

In Vegas, go to Options>Preferences> Video (tab)- set rendering threads to two on your quad core.

For you PC, in the Advanced System Setting>Performance Options> Advanced>Virtual Memory>Change...
-- set up 3GB of page files on your C and D drives (assuming you have two hard drives on your system) or a single 6 GB page file on the D drive.

Reboot and try it again. I used to have a lot of crashes related to JPG images or trying to render HD WMV files or other highly compressed HDV formats and the two things above cleared them up for me.

Mike

DaveT,
So that's what that number means? Interesting, I changed the audio setting and I get the exact same error except it says 48000 instead. This was a 5.1 project, but since I'm just rendering the video I changed it to stereo, no luck. I also deleted all the audio tracks. Still get that error, about half the time.

The other half of the time it says "unknown error."

MTuggy, thanks for explaining all that. I did as suggested, and it seemed to make a small difference. I have rendered out one section that is a minute and a half long! I am going to try it on ONE core and see what happens.

The only solution I have, is to stay up with this thing, keep rendering bit by bit. Fortunately, when it crashes out, it doesn't destroy what its done before.

Anyways, its a long frustrating night ahead. I can only think that long form projects should have their color and fixing and sound mixing done somewhere else, because it seems like the longer and more complicated the project, the more Vegas chokes at rendering.

Any other suggestions would be appretiated also!

kairosmatt

> "AllocateMixBuffer(Microsoft Sound Mapper) : m_wfxPrepared.nSamplesPerSec is 44100!
(m_ccPreroll 141944855234892236 nBuffers 33042996)"

That suggests you may be using the Microsoft Sound Mapper as your audio device. If so, try selecting something (anything) else - preferably the ASIO drivers for whatever soundcard you have.

Mark

HI Mark,
Thanks, that sounds like we're getting somewhere.

I checked the default audio device, and its all set to Realtek HD, in fact on the computer there is no option for Micrososft sound remapping. But the Midi playback device is Microsoft GW Wavetable SW Synth but there are no other options for default. Could this be the culprit? Would I have to find and instal ASIO drivers for the Realtek soundcard and then change the MIDI default?

On the drivers for the Realtek soundcard, there are 20 (!) drivers listed. 11 are from Realtek, 7 are from Microsoft and 2 are "not available." Is there a way to know if one is an ASIO driver?

Thanks!

That sounds like you are looking in the wrong place. I am talking about your settings in Vegas under "Options|Preferences|Audio Device|Audio Device Type".

If this is set to Microsoft Sound Mapper then change it to something else - first choice would be the ASIO drivers for your soundcard (if it has ASIO drivers). Failing that, second choice would be "Windows Classic Wave Driver". Anything would be preferable to "Microsoft Sound Mapper".

Mark

Thanks Mark,
I guess I don't have the realtek HD AISO drivers, so I will try to find them.

But when I chose "Windows Classic Wave Driver" it allows me to choose Realtek HD for all the other defaults.

However, it still crashes! And Vegas says the reason for the error could not be determined.

I don't understand why it should matter though, I took out all the audio tracks and am only rendering video files without sound, but it seems to be affecting at least two computer.

kairosmatt

Okay, finally got an error I can read, and it just replaces microsoft sound mapper with "realtek HD audio output."

I looked for updated audio drivers, but seems I'm up to date.

Sony suggested I uncheck "enable track buffering" and check "disable multi-processor AVI rendering." But neither one worked.

I'm beginning to worry.

kairosmatt

Relax I've had this problem...

Are you using Vegas 8.1... If so go back to 8.0 it seems to be way more stable doing HD rendering for me.

I could not figure out why it would stop rendering then I went back to 8.0 and it all of the sudden worked...

I hope this helps.

Nope I'm using 8.0c (tried b too). Can't use 8.1 because none of the plugins (raylight and cinescore and some others) won't work in it.

After, now, 30 hours of rendering hell, it still didn't all come together right. Too many small bits, I thought I was linning them up, but there are gaps where the damn renderer crashed.

I've also tried MP4 and Sony MXF just to see. No good.

Did get some tech support, but the latest one was no help. Just pointed me to a fact sheet, that is not applicable.

I am beginning to see why some call Vegas is a 'toy.' If you can't get your work out, what good is it???????? Another night of hell ahead.

People on this board have been saying that Media Composer is more appropriate for longer, more complex works, but I don't even want to think about learning another system right now. ITs just so easy to edit in Vegas, but rendering is a HUGE issue. I'm already behind because of this, but what the hell else can I do?

Very frustrated, and dissappointed,
kairosmatt

I hear you brother... I'm having a preview problem as we speak... I just can't playback perfectly normal footage.

Anyway I have another idea for you.

How many different hard drives are you using?

Make sure you asre not rendering to the computers operational drive, and depending on the how full your current media drive is it might be safe to be rendering to a third or in my case a fifth drive.

And be sure that if you use an external drive that it's fast enough to keep up with the internals.

ie... firwireB or eSATA.

GOD SPEED

"After, now, 30 hours of rendering hell, it still didn't all come together right. Too many small bits, I thought I was linning them up, but there are gaps where the damn renderer crashed."

Back when I was having massive crashing problems I would use loop render. I would take the piece left from the crash and review it... find out exactly where it crashed. I would then set the next loop render about 10 frames before the end of the last piece. It took all night and I ended up with about 50 crash pieces which I took over to Ulead Movie Factory 6. I trimmed the pieces to fit properly frame wise then smart rendered to one file.

It's a nightmare I agree...I have all kinds of crashes all the time too...
Some things you could try if you havent already that will make things a bit more stable:

- Set the Options, Preferences, video, Dynamic RAM preview setting to 0 during rendering
- I set my page files to be handled by the system
- Reboot before you start te render and shut down all stuff like virusscanners and so on

I dont know if this helps you in your particular case, but it helped for me to get my last project rendered on at least 1 of my 2 PC's...

Hey Guys,
Great suggestions.
Greg: I have three internal hardrives divided up one each for the OS, Mediafiles and renderer. Got that idea from this forum a couple of years ago and it has streamlined things.
Blink, I had thought I was being conscientious with my checking, but it was 4 in the morning and I was a wee bleary eyed. I only missed two spots, less then a second each, but they threw the whole thing off. Most painful.

I tried reverting Raylight Ultra to regular, but same thing. I haven't tried the Dynamic RAM preview yet, thats a good thing to check Dude.

I have, however, figured out what the root problem is (for Vegas anyways). There's too much media FX on too many clips on too long a timeline, it just can't handle them. I know this because I removed 90% of them, and it rendered much better (only stopped once-practically heaven for me at that point).

Some interesting observations:
1. The MPEG2 renders always crashed at exactly the same spot. And you could never render that spot out. Usually it was at a point in the middle of an event/clip.
2. AVIs crashed a various spots, and you could just pick up where it crashed and keep going till it randomly crashed again. AVIs usually crashed right at an edit point.
3. Because of the above two, you could render to an intermediate AVI to help the bad spots for MPEG2.
4. I only got error messages half the time, the other half was unknown, and I wasn't able to observe anything about the differences.
5. The only error message was the audio one reported above event though:
a. audio files would render no problem (AC3 and .wav)
b. the video files I was rendering did not include the audio
c. I had turned off the audio track buffer (as suggested by Kevin at SCS, totally thought that was it)
d. deleted all the audio tracks from the project
6. The results are 100% repeatable on both XP and Vista of one computer, and XP on another computer.

So something is definitely wrong here. And I think the longer and more complex the project, the more render problems you will encounter.

The silver lining: The project didn't need all that CC BS anyway, and was a huge mistake on my part. The footage was fine (and in some cases almost great) but I had been working on the project and looking at the footage so long it had started going bland.
But, a quick render with all the CC and a preview on the TV would have been all it would have taken to see that. Vegas just couldn't handle it. At least now the project is not such a nightmare to render!

Thanks to everyone for their support!
kairosmatt