This is a new one.. error during rendering, any ideas?

[Nigel O’neill]

Paul

Hope this gets to you in time and that you are feeling better. I would roll back to the earlier version of Vegas 11 that worked for you, get the job done then try to figure out what went wrong. You can download earlier versions from here:

https://download.sonymediasoftware.com/current/

My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Dave Haynie]

If this is the class of “error can’t be determined” that you get immediately, could definitely be your settings.

I had a number of higher bitrate presets, things I’ve been using for years, like 50Mb/s CBR MPEG-2 output, things like that. When I first got Vegas 11, I found a number of these templates errored out with the same sort of message.

I know basically what’s happening here. For rendering, Vegas is spawning a subprocess that’s using independent modules, such as the Main Concept CODECs, etc. I think the design here is such that Sony’s pretty much expecting the Vegas UI to do all the bounds checking for each of these. So they expect the subprocess to pretty much just work… and they fail completely when the subprocess rejects the render, for whatever reason. Clearly, in the case I found, I had parameters that were just dandy in the old version of the Main Concept MPEG-2 engine, but considered out-of-bounds by the new one (I ultimately fixed this by going to a slightly lower bitrate).

I guess I’d find it a little suprising, but maybe less so after my initial experience with Vegas 11, that this might change in-between Vegas 11 releases. Or maybe this was a template you hadn’t used before with Vegas 11. Either way, that’s the one source of this kind of error I’ve run into before, and with at least a credible explanation.

-Dave