Geoff,

I agree. The ASIO drivers "should not have any impact on the render process at all.

But if that were true, I wouldn't have been consistently seeing ASIO error messages at the end of a render.

So I'm inclined to agree with Paul.

I'm almost done with this one project. Once complete, I will give 511 another try to try and troubleshoot on the behalf of Sony.

Peace.

Michael

But if that were true, I wouldn't have been consistently seeing ASIO error messages at the end of a render.

Oh, missed that bit. Maybe that is the problem, that a soundcard driver is somehow being involved in an unrelated activity.

Anyway, I notice no input from SCS in this thread, so assume that means that all resources are busy,being applied to fixing the problem.

geoff

Michael: But if that were true, I wouldn't have been consistently seeing

Geoff: Oh, missed that bit. Maybe that is the problem, ...

well ..... we all missed that seemingly critical information! - I read and re-read all posts above - it was never mentioned!

I humbly suggest to Michael that he accurately reports the circumstances of his problem and everything that happens including any error messages, otherwise there is little point in posting anything in this Forum; merely venting your frustration does nothing for anybody....

OK,

Time for me to begin drinking heavily.

AH HA I FIGURED IT OUT

What the heck MIDI has to do with a render, I have no idea.

The other week, I was messing around with MIDI, as I was playing with my iPad to use it as a control surface. I had gotten a couple of apps I wanted to try on my iPad, AC-7 Core and OSC.

So I turned on MIDI. I didn't really have the time to get it working, and forgot about it.

I went to the preference page, and saw I still have MIDI checked, and unchecked it. Wa la, everything works.

Glad to figure it out.

Peace

Michael

Time for me to begin drinking heavily.

.... presumably to wash down a large portion of Humble Pie ?!?! Ha Ha

Humble Pie?

Really?

The software works perfectly before the upgrade, then is crap after the upgrade, with me changing nothing in between? With no description what's wrong.

I'd be happy to eat humble pie if the earlier version behaved the same as the update. But it didn't. The old version worked perfectly with the MIDI settings turned on and left on.

The new version is what changed, not my settings. They were the same as before.

When you have to "undo" something to make an update work, that isn't me, that's the software.

Dude, I run a software company, and if my guys released this. I'd be tearing them a new one first thing when I got to the office.

Michael

GuitarToys you may be on to something. I was to (before updating to 511) was getting errors about my MOTU drivers failing. However my errors would appear after trying to close a project. I figured that the error came because my projects are in 44.1khz and the new default projects (that loads when a project is closeda0 is 48khz, and the driver would crash when changing sample rates.

There was ZERO problems with rendering audio before I went to 511, as soon as I did I could not render in any format other that Real Time Render. I did not change a single thing other that the update. Now as it is happening to some and not others, then that would not me that it is NOT a Vegas problem, and at the same time does not mean it IS a Vegas problem. But obviously something in the update does not play nicley with something in the systems of those affected.

I have rolled back 425 and rendering audio is possible.

I'm trying to figure out why MIDI would impact an audio render at all.

I guess there might be MIDI automation with some of the audio parameters. But simply having MIDI turned on shouldn't crash things.

But now that you mention it, there might be some relation with an ASIO device that has MIDI built onto it.

My NI Komplete Audio 6 has MIDI in and out on it.

I didn't realize it, but I had taken the NI off my main computer to record a gig with my laptop, and my main computer reverted to the Windows Driver. So I wouldn't have a render problem.

But when I would do a render, with my ASIO driver selected, I would after the render completed, and I clicked close to the render dialog box, I would get the following error.


The ASIO device Komplete Audio 6 caused an internal exception (0xe06d7363) and has been disabled.
The ASIO device Komplete Audio 6 caused an internal exception (0xe06d7363) and has been disabled.

It is consistent as heck.

ASIO driver, I get the error

Microsoft Sound Mapper, no error.

Three of my four sound interfaces all have MIDI built in.

I will try my 4th interface and see how it goes.

I will start a new thread with my findings.

Peace.

Michael

I will have to try it with my MIDI disabled. But I am not sure how MIDI would affect a render either. I do need my MIDI though as I have a control surface in my setup.

I think if you just select the MS Sound Mapper, instead of using the ASIO driver, you will be OK.

It seems like Vegas is having problems using an ASIO device, if it has MIDI built in, even if you AREN'T using MIDI.

M

Update (immediate) to my other feedback.

I just tried to render from the special new admin level userid that I used to install Vegas Pro 11 510/511. I did this after configuring Midi to use my MAudio Midi device (2x2) and turning on my Mackie MCU control surface.

The traps are back.

They are definitely related to having a Midi port configured for use within Vegas Pro 11 510/511.

I tried two different Midi devices. My MidiSport 2x2 (a USB attached interface) and my PreSonus FireStudio (firewire attached interface). The render traps occur any time either Midi device is in use by Vegas Pro. I use a Mackie MCU HUI device. It doesn't have to be configured with External Control active for the trap to occur.

How do we proceed to resolve this?

Thanks, Marc

YES! THANK YOU, THANK YOU, THANK YOU for giving out this information.

I'm also a victim of this same problem. Running build 511 on Win7 64-bit.

I was about to rip the final bits of hair I have left as I was trying to figure out what the h*ll was wrong with my project. Didn't have much crashing issues ("much" = no more than the usual every 15-30 mins as the project got bigger). Every time I tried to render it to ANY possible video format (I probably tried them all out, with different resolution settings and all), the end result was always immediate crash of VP11 right after the rendering started.

I changed the video rendering settings from the render template --> disabled the audio altoghter (rendered just the video) and voilá! IT'S RENDERING! Can't believe it, but it's true! I AM SO HAPPY! ^___^

BTW, I think it has something to do with complex automation envelopes in the video tracks, because right after I made a few of those with my control surface, that newer version of the same project just wouldn't render anymore and crashed Vegas.

Now ... will have to investigate how to get the audio track back together with the video.

Huge thanks to whoever who spotted this problem in the first place and "thumbs up" (the poop chute) to Sony for letting your paying customers do the beta testing for you. No problem, our pleasure. Geez.

Ah, the "semi-final solution" was already posted up there.

Yep, having MIDI ports enabled was the cause of the crashes in my case as well. All MIDI I/O's disabled from MIDI Preferences -> rendering video with audio works again, just like it's supposed to.

Wonder if they'll fix this in the next major update and charge us for it. Wouldn't be a bit surprised, "lol".

I too have been having the same problems with no audio rendering. I also feel like a Beta tester. I had got very annoyed by the Crash message. I cannot understand why Sony software engineers do not make the program put up its own error message when incompatibilities are found. I had discovered that reverting to the previous build solved it.

Thanks to others here for finding out that turning off the MIDI stuff is a successful workaround. I have not tried it yet, but I will tomorrow.

I have also had mysterious crashes simply dragging .ts HD video files to the timeline. But that's another story...... Probably another software bug?

UPDATE: Thanks, guys! Just tried switching off the MIDI output in settings and my audio rendering now works. What a strange bug, come on Sony, sort it out please?

I rarely post, but just wanted to say that I've had the same problem and this has solved it. I'd like to be able to use my MCU Pro control surface without having to enable/disable MIDI ports whenever I want to render, so Sony, please fix this in the next build. My thanks to the tenacious user guitartoys who found us a workaround in the interim.