You didn't say what sort of audio, which template etc, but I have just rendered a 44,1 khz wav, a 48 khz wav and an AC3 for DVD from both the new 32 bit and 64 bit V11 releases without a problem, so it's not happening everywhere.
I hope you soon get it sorted though - it's so frustrating when a routine task won't work.
i don't doubt you're having problems, but you'd probably be better off FIRST asking if anyone else is having the same problem rather than demanding a recall...
i'm not having any problems rendering to any audio format, but then again, maybe my update was better than yours? ;-)
guitartoys wrote: After installing the 511 Vegas update, I can not render audio for any project, new or old.
This sounds serious - so in order to help documenting a possible bug I tried to render to all audio formats.
Results:
ATRAC: render Ok. No problems
AIFF : render Ok. No problems
AC-3: render Ok. No problems
FLAC: render Ok. No problems
MP3: render Ok. No problems
Sony Wave64: render Ok. No problems
Wave: render Ok. No problems
Windows Media audio: render Ok. No problems
If you are to look on the forums you will see that I too posted about the same issue.
No matter which audio format I select the program crashes. Even if I try to nest a project into another.
Yes it may not happen to all. Most likely something to do with a non controlled variable, i.e differences in installed .Net frameworks, device driver or something along those line that will cause problems for some and not others.
Perhaps it has something to do with what the audio is being rendered from or the project audio properties (Best/Good/Preview). With TWO users reporting the same problem and not having the problem in a previous build something has to be up somewhere. Probably the best way to track it down is to look for what the two users with the problem have in common.
It's getting real close for some type of auditing s/w that'll zap through a system and report back any differential from the SCS straight and narrow. And before anybody stomps over me, I'm not just talking about System Specs.
Once we're talking about .Net this, and CODEC that, and so on, analysing anything will be a moving target, and not going to go anywhere unless we can get to some level playing ground.
Here's a novel thought: how about SCS supplying US with their working recipe?
Now, once that has been road tested out here, AND we still get these reports then what? There're bugs? Or that there needs to be further, fully reality checks by this that know and can make a difference. Until that happens, we're shooting in the dark.
Audio is working fine here guitartoys, cant explain why its not for you. But seeing that others are rendering with audio ok, it does point to the possibility it may not be vegas at fault?
Did you get any further with this. Keep us posted.
PS..
"Here's a novel thought: how about SCS supplying US with their working recipe?"
I asked SCS this exact question recently, not mentioning any names, but i got the response:
We are not allowed to show any favoritism between hardware manufacturers [GPU cards] or CPU types etc. Sony tradition has always been this way and we cannot recommend hardware setups to Vegas users for this reason.
Or words to that effect, not a direct copy.
Well, I'm downloading the update now and will try it to see if it clears up the bugs in my current V11. But what is it with this 'build' number thing? Will there be no more b, c, d, etc?
All I know is a have reverted back to the prior version, and I am happily working again. Not a hitch.
511 simply crashes every single time I try to either a) add audio to the video render, or b) just render audio using any setting.
The only thing I didn't try was to turn GPU acceleration off, as I have been using that without a problem before this patch.
All I know is 425 works just fine.
The moment I load 511, nothing works with audio.
I already lost a 1/2 day's worth of work f'ing with the situation, and I am not about to go to 511 to troubleshoot this for Sony, if we don't even get some basic acknowledgement.
In earlier versions I would get complaints from Vegas - after - rendering, with my Native Instruments Komplete Audio 6 card failing. It is an ASIO interface.
But the NI card works perfectly everywhere else and is running the latest drivers.
So there may very well be an ASIO driver related problem, or something to do with the NI card.
Also, it may very well also be related to the GPU being enabled.
Another variable might be my hardware config, in that I am running an SR-2 motherboard with Dual Xeon hex cores, so 12 cores but 24 threads (24 cores show up in task manager). I have run into problems with a couple of programs not knowing what to do with that many cores, and I have to scale their configuration back.
Once I get done with this project, I will load the 511 patch, and pick my poopy motherboard sound interface, as well as disable GPU processing and see if the problem goes away.
Michael,
Defo try to bypass the ASIO audio side of things in that test. I had a very similar deal with my MOTU asio drivers and would either make the time line stutter like crazy during preview or cause a crash. I eliminated the ASIO setting from Vegas a good while back and simply selected the Mobo audio. This fixed so much for me.
I still use the motu for all my musical studio side, like you, for music creation and guitars (guessing that from your name!). The motu and mobo audio can live quite happily together - into a hardware mixer then amp. Its really worth a try in your test.