"Render As" Dialog Won't Appear: "error

Crosley wrote on 11/5/2011, 11:13 PM
Have searched the forum for similar problems, but don't see any reported. In Sony Vegas Pro 11 (both 32-bit and 64-bit versions, both the "original" builds and the new 424/425 builds) I can't actually render any video.

When I select File > Render As... I am immediately presented with an error dialog that says:

"An error occurred while creating the media file .
Exception thrown by method called "

Yes, there's a space between "file" and the "." The damn dialog won't even report the error correctly. Funky. Similarly, there's no data after "method called ".

I uninstalled all versions of Vegas and did a fresh install of version 11 and still see this behavior. I guess my system is missing something that the new funky Render As dialog expects to find?

Will be sending this info to Sony as a support request, but in the meantime... Anybody seen this and have a solution?

Oddly, I find that other "render" functions (that do not rely on the dialog in question) *do* work. For example, I can "real time render" to a wav file and the "Upload to YouTube" option (which renders and uploads without exposing the Render As dialog) both work.

Of course, any rendering that relies on showing the Render As dialog fails. So, for example, I *can't* do a Tools > Render to New Track, either. But I get a different error message when selecting that option. Vegas reports:

"An error occurred during the current operation.
Error 0x80131501 (message missing)"

This is driving me nuts. Anybody seen this? Of course, this happens on my main editing machine while crappy laptops work just fine. Grumble.

Thanks and Best Regards,
Keith

Comments

enespacio wrote on 11/6/2011, 12:13 AM
I'm getting a few seconds of (Not Responding) when selecting Render As. This didn't happen with the old render dialog, but so far it only lasts a few seconds, and then does open.
James
Crosley wrote on 11/6/2011, 1:06 AM
OK, well, not the same thing. Vegas throws an error for me when selecting "File > Render As" (and won't display the Render As dialog).

Cheers,
K
okahara wrote on 3/11/2012, 4:20 PM
I get the same exact thing as Crosley described in his original post. This makes the program quite unusable. Have sent mail in to support and await a reply. Crosley, did you ever get a fix? I've uninstalled and re-installed and no luck.
FilmingPhotoGuy wrote on 3/12/2012, 1:09 AM
By your specs I see you running WinXP. Vegas 11 is NOT supported for XP.

Vegas 11 FAQ's: Read "Operating System Support"
http://www.sonycreativesoftware.com/vegaspro11introwebinar/qa
ushere wrote on 3/12/2012, 1:31 AM
maybe .net framework isn't upto date?
Crosley wrote on 6/17/2012, 8:50 PM
Nope - Sony support did have any helpful suggestions. Have once again been trying to solve this issue and nothing has helped.

This problem doesn't exactly seem rare, but support doesn't know the fix and neither does anybody else, I'm afraid.

Would be helpful if Sony could actually tell us what it is that Vegas 11 is attempting to do when one selects "Render As..." The error comes up instantly for me upon selecting that menu item.

Corrupt or bad codec? Bad permission somewhere? Who knows?

The latest thing I tried was to install Vegas to a different directory (not the default location). That made no difference either.

Have also cleaned my registry and many other standard things one would do when trying to track down oddball Windows errors like this, but all to no avail.

The only thing I've seen that fixes this problem is to do a completely new Windows 7 install... Which is to say, basically install Vegas on a different/new machine. I'd do that, but that would make me reinstall zillions of apps and I really haven't wanted to bother since Vegas 11 is the only application giving me grief right now.

(BTW, I've even done an "in place" installation of Windows 7 on my machine to try and fix this problem, but that didn't work either. This possibly suggests that the problem lies with some file unrelated to the core Windows install and unrelated to Vegas, but which the Render As routine attempts to read/access. If so, it could be a bad codec, but in my case I don't actually think that's it. Anyway, something's missing or bad but since the error message gives no clues...)

Best Regards,
Keith
Soniclight wrote on 6/17/2012, 11:19 PM
Keyboard Shortcut Workaround?

I have v10 and from what I can tell, you 11-ers have to deal with some new interface/windows issues when doing things like "Render As" (Sony thought sexier look would be better...). Anyway, I do "Render As" so often due to test renders and so I've created a keyboard shortcut -- in my case Ctrl + "-" on the Numeric pad.

Maybe trying a direct keyboard shortcut may not (or may still) call up the same error message when using the File/Render As. Just something to try.
If such would work, that seems to point to some GUI menu bug issue.
Grazie wrote on 6/18/2012, 12:24 AM
@Crosley

What build of VP11 are using? VP11 is now on 682/3. In another post you made you say you "were" on 424(?). There has been much work on aspects of Rendering and I am concerned you have the best option to go forward.

And, what are your system specs? As VP11 has become more dependant on a Users system - OFX and GPU acceleration - and again, I am concerned that you are working with the hardware that you can usefully use.

Unless we can establish these two aspects with you, we are kinda punching in the dark. And my guess so is SCS?

Grazie


Crosley wrote on 9/7/2012, 8:53 PM
Hey Grazie,

Didn't see your reply until now. This problem persists in all newer versions of Vegas Pro. Can't say anything more about it, but I suspect this issue will get resolved in a future version...

-K-