Vegas Pro 16 (361) random crash when trying to select 'Render As'

Liberty610 wrote on 1/30/2019, 2:40 PM

I just un-installed Vegas 16, cleared my registry with CCleaner, rebooted, and re-installed Vegas. Still crashing when I click on 'Render as' option.

I see this has been an on-going issue since earlier versions of Vegas. Oddly, this is the first time I have come across it.

I read some forum replies after doing a Google search that said if you load a simple project with a short clip on it (i inserted an empty event), bring up the render as menu, the menu should pop up without issues. When/if it does pop up, you then click cancel on the render window and open the project you need to render (without closing Vegas of course), then click Render as on your actual project. So far, this has worked for me on the 3 times I attempted it.

I have sent over 10 crash reports to Magix on this. Hopefully this gets fixed, because it's super annoying.

j-v wrote on 1/30/2019, 3:07 PM

I think it is not a Vegas problem as you had it also in earlier versions of Vegas, but it is your problem with your hard- and software, so I think complaining and reports will not solve your problem.
You have to do it yourself, maybe make comparisons with other users that don't have and never had problems uptill now with Vegas software programs.

Liberty610 wrote on 1/30/2019, 3:19 PM

No, I have never had this issue with other versions of Vegas, as I stated in my second post:

"Oddly, this is the first time I have come across it.."

This issue didn't start with this version of Vegas until I started loading in longer projects to render (hour+).

After searching it on Google, I see that many others had the issue on various versions of Vegas since version 12. Hence how I found the work around to load a small/short project and open the render box that way.

I don't feel I am complaining. I simply stated the issue is annoying to deal with. After spending hours on a project and it's all ready for the final stages, the last thing you want to see is a crash before you even get to start finalizing it. It's obviously a known issue somewhere if I found more then 5 forums with the issue on it. And when the program crashes, they want reports sent so they can apply updates with possible fixes.

j-v wrote on 1/30/2019, 3:24 PM

No, I have never had this issue with other versions of Vegas, as I stated in my second post:

see this has been an on-going issue since earlier versions of Vegas.

??????????????????????

Are you the same person?

Liberty610 wrote on 1/30/2019, 3:31 PM

Ok, so... I thought I explained that....

"I see this has been an on-going issue since earlier versions of Vegas" - meaning I have see several forums from other users posting about this same exact issue since version 12. I also added, directly after that, "Oddly, this is the first time I have come across it." Meaning I have personally never come across it, but I SEE that others have from the Google search I did of it.

j-v wrote on 1/30/2019, 3:56 PM

Let it be, also if it maybe not only your problem says nothing about the program itself, because with others it runs well, good and fast.
The only thing you are able to hope is that the development team is able to find something on your particular set-up to resolves your problems.

Stefano-Guandalini wrote on 1/30/2019, 4:18 PM

I feel your pain!!! With my Vegas Pro 15 I went through the exact same problem for MONTHS and a total of 27 emails back and forth with the Magix support team. Eventually however they sent the right hint and the problem was solved once and forever. Here is their final, winning hint: As a troubleshooting step, lets have you click Options > Preferences > General tab, and remove the check from the box for Enable QSV Encoding and Decoding (where available) - then click Apply and OK.

Liberty610 wrote on 1/30/2019, 4:19 PM

I don't have any other issues with the program, thus far. I am very happy with it, hence why I upgraded to it. I simply came to a community help forum and asked what could be causing the issue. Thanks for the replies!

Liberty610 wrote on 1/30/2019, 4:24 PM

I feel your pain!!! With my Vegas Pro 15 I went through the exact same problem for MONTHS and a total of 27 emails back and forth with the Magix support team. Eventually however they sent the right hint and the problem was solved once and forever. Here is their final, winning hint: As a troubleshooting step, lets have you click Options > Preferences > General tab, and remove the check from the box for Enable QSV Encoding and Decoding (where available) - then click Apply and OK.

Thank you for the helpful reply Stefano! I did see this was an option to try in other forums I was reading on, but they all said it was only helpful to turn that off if you had an Intel CPU with integrated graphics. I will give this a try tonight and see how it goes and report back!

Thank you again for the helpful reply!

bvideo wrote on 1/30/2019, 11:54 PM

@Liberty610: A long time back I had the behavior in your 2nd paragraph on more than one version of Movie Studio on my previous computer. In watching the program with SysInternals/ProcessMonitor I had the impression that RenderAs was enumerating all the codecs and then crashing. I wondered if it was a codec I had installed. An example of one I installed was one from Grass Valley formerly Canopus. I never did completely solve the problem. Some handwaving workarounds from the web sometimes got me by. A later version of Vegas worked OK.

Any third party codec?

joost-berk wrote on 1/31/2019, 4:04 AM

This is an ongoing issue for me since VP14. I tried everything. Turning off all external hardware, GPU, QSV. Literly everything. Strange thing is that it does not appear on all systems. So what I said, even disabling QSV was not the trick for me.

Yesterday I started VP16 in Windows Compatibility Mode: Windows 7. That seems to work for me! No crashes yet. I tested for a while where I am certain about that crashes had been appeared. But I'm going well on Vegas right now.

Keep you posted!

Liberty610 wrote on 1/31/2019, 4:33 AM

Thank you guys for the helpful replies! I'm glad to see that this is not just me who's had this issue.

Bvideo, I know 3rd party codecs can cause some issues, but I do not have any installed at this time. Thanks for the suggestion, though!

I have not gotten a chance to thoroughly test it yet, but turning off QSV seem to do the trick so far. I did try rendering a project 4 times after I turned it off to see what it did (closing Vegas completely after each attempt), and had no issues. So a big THANK YOU to Stefano for the tip.

The workaround of opening a short project and getting the render window to pop there, then canceling/closing the render window, followed by opening my actual project seems to work for sure. Hopefully the QSV turned off fixes it. If not, I'll try Joost's compatibility mode option.

I too, will report back!

Liberty610 wrote on 2/1/2019, 5:13 AM

I feel your pain!!! With my Vegas Pro 15 I went through the exact same problem for MONTHS and a total of 27 emails back and forth with the Magix support team. Eventually however they sent the right hint and the problem was solved once and forever. Here is their final, winning hint: As a troubleshooting step, lets have you click Options > Preferences > General tab, and remove the check from the box for Enable QSV Encoding and Decoding (where available) - then click Apply and OK.

Stefano, THANK YOU! I have been in and out of Vegas and done several renders since your suggestion with disabling QSV, and I can confirm that the problem has not resurfaced. Thank you again for the great tip! This has been an awesome, and helpful community thus far! I am glad Magix is improving Vegas and keeping it alive!

Stefano-Guandalini wrote on 2/1/2019, 10:03 AM

I am really glad it helped!!

joost-berk wrote on 2/4/2019, 3:18 AM

Okay peeps, I got other (good) news in resolving this issue. If the Render As.. crash still occurs after disabling the QSV (which did not work for me) then you can do two different things...

1, Since Vegas render-dialog strongly relies on .NET Framework 3.5.1 (quote from Magix Support), you need to manualy install this if you are running the latest Windows 10 version. Windows 10 standardly only uses .NET Framework 4.7 and 3.5.1 is turned off by default.

Go to Control Panel -> Programs (Programs and Features) -> Turn Windows features on or off and scroll down the list to find Microsoft .NET Framework 3.5.1. Turn on this feature by clicking the checkbox so it is filled. After allowing Windows to work through applying this feature, restart your system.

2, Run Vegas in Windows Compatibility Mode, as Windows 7. This is not confirmed by Magix, but it works for me.

Goog luck!

vkmast wrote on 2/4/2019, 12:38 PM