smart solution: close dialog automatically :)

I reproduced the behavior on my laptop. The vegas130.exe process continued to keep one cpu pegged. Like everyone else, I choose to check the "Close this dialog box when rendering completes" box, so I don't have a reason to hit Escape or Close when the render is finished.

Also, just because that process is hung doesn't mean you have to do anything right away if you're pressed for time. You can start another Vegas session with the same project and render from that session. The new vegas130.exe with steal cycles from the process that appears to be hung and compete without incident.

My three observations about this scenario:

1) Always strike Control+S before selecting File / Render As so you save all edits before you render.

2) Try to get over the tick of hitting the Escape key. As an AutoCAD and Photoshop user, I've had the tick myself.

3) Vegas 13 probably should deal with an unexpected user response without hanging the session.

Happens here too. VP13 on Win10Pro. But, like John, I have the "Close dialog..." selected and I never hit ESC, I use the mouse to close dialog boxes.

Confirmed here too using V13 on Win 8.1 .. Just never came up for me as I don't hit ESC at that point .. ESC closes the dialog box and leaves you with no way out. Not cool but not really a problem either. I certainly agree with saving your veg file BEFORE rendering.

Confirmed here, but had to force myself - it's never occurred to me to try and use ESC for this sort of thing in Vegas, or any other app !

geoff

Thanks to all for the confirmation.
"Yes it hangs but... ...that's OK. I don't use ESC. "
That's so sweet :) This confirms we all love Vegas.
And I can understand this because I'm aware of this bug since Vegas 9 and I also ignored it for a long time. I got trapped in the lost dialog box a lot and had to redo things but I said "oh well It's ok"
After losing a work lately, I thought it's time to report this issue since I use keyboard a lot and a user hitting ESC key to close a window is not such an unexpected behavior that could not be handled by the developers.

I submitted this issue as a confirmed bug (thanks to you) and I hope it won't appear in the next build or version.

Ok, it hangs, but can i ask why don't you check "close this dialog box automatically"?

I work on audio production too and I render several audio projects at the same time very often. For ex: When I need to render a very long program that needs to be splitted into multiple sections, I open the same project in different Vegas instances and I render them as background tasks while I work on other projects.
When you enable the `Render Complete` dialog, Vegas shows a "%100 complete " at the task bar when it's done. It also shows the output file name in the box. So when you start rendering out sections A, B and C etc... of a project, you don't get confused because the project name is displayed in all completed tasks.
If you use the auto-close dialog box function, you don't get any visual notification that the project render is done. While switching between task, you can accidently try re-rendering an already completed task or close a Veg that is waiting to be rendered. Using that dialog box helps me a lot to quickly see what task is rendered and safe to load/render another project/section in that Veg instance.
If you work on single task, you don't need to use that Dialog Box unless you need to see the Elapsed Time for Rendering.

ok, in this this case i understand
you can save the project in different names, so you know which has finished rendering

[I]When I need to render a very long program that needs to be splitted into multiple sections, I open the same project in different Vegas instances and I render them as background tasks while I work on other projects.[/I]

Why don't you try and use one project with regions and batch render those? Vegas has a build in batch render script or use Vegasaur.

Despite all that, you can still us the mouse to close the dialog box.