I do it all the time. However, I have had issues like this, where the AC3 failed to render, or rendered at an incredibly slow rate. This was especially true with Vegas 4.0d.

The "solution" is to re-boot, start Vegas, and then immediately run your script. See if that works. Also, what script are you using? I always use the "BatchGUI" script (the one that someone else wrote, but which I modified and which now appears at the Sundance site:

Batch Render Script

The Mutlirender scripts have the same issue. Workaround is to first render a dummy ac3 file using the default template and then render using the template you want.
Bob.

I have also had Vegas 5 attempt to take an icredible amount of render time on an AC-3 file but I was not running a script. I stopped the render and re-booted Vegas and the render then went normally.

Ron

Thanks for the response.

In my software development experience, we call that a 'bug'.... :-) Sony?????

There have been 2 fixpacks to Vegas since this bug was reported. Is this ever going to be fixed???

This is very reproducable:

1) write a short script to render a project to ac3.
2) The script will run and will not do a thing.
3) Do a manual ac3 render
4) rerun the script, it will now load the ac3 renderer and render the ac3 correctly.

2G

The same bug affected the Multirender tool in the Veggie toolkit. SImple workaround though. Render a dummy file using the default template then the renders using custom templates work fine.
Bob.

/edit/ oops sorry I'd already mentioned that!

Isn't this 'fix' good for you?

Is there a little tongue-in-cheek in that question? I hope so.

In answer to your question, NO!!!!!!!!!!!!!!!!!

I have written automated scripts that check dates, dependencies, etc. and render, if necessary, to the various formats. I develop huge projects with up to 25 separate Vegas projects rendering to 6 or 7 formats. If I forget to do this STUPID manual "start an ac3 render, then cancel it" before I start my massive renders, I may end up burning DVDs with old ac3's that don't match the mpgs. That $%$# me off and usually makes me delay my deliverable to my customer (if I happen to catch it when proofing which I sometimes don't since it's often subtle).

<soapbox>
Maybe I come from a different era. I have 30+ years as a software architect/designer/developer. In my book, a bug in a product I sell is a bug, and it's my responsibility to fix it. I would be fired if I told a customer to "just live with it". Yet, I have never in my life seen so many people as on this forum trying to tell Sony it's ok not to fix bugs just because if we stand on one foot and scream some incantation, the bug is a little less painful. "Oh Great Sony, you need not fix this bug for us unworthy customers.... One of our own has figured a way, painful as it is, to work around it, even if forgetting to do the workaround might hurt our reputation with OUR customers...." Sorry, that's not acceptable to me.
</soapbox>

Sony, do you read these forums? Or are we just talking amongst ourselves to make us feel better?

2G