I have use CTRL+Z in two different ways and they don't crash Vegas but each does something different -- really weird. I programmed one instance in my Wacom tablet to open the extension monitor (and in Vegas I had to reprogram the default ALT SHIFT 4 to CTRL+Z because Wacom can't be programmed to write ALT SHIFT 4 ) and I had long ago already programmed another instance of CTRL+Z into my Shuttle Pro to act as UNDO. They both work in their intended ways. Isn't that weird? In case you wonder, when I changed the Vegas command I hadn't checked to see if CTRL Z isn't already a default for something else because I'm weird too.

Just a quick fyi for those that may have a similar issue.

Vegas Pro 15 Magix AVC NVENC (Nvidia) encoding immediately crashing on Win10.

Card: NVidia 750Ti

FIX: Update to latest Nvidia drivers: 385.41

(Allow Legacy GPU:ON)

Thanks for the update Nigel... good info to those who need it.

Just a quick fyi for those that may have a similar issue.

Vegas Pro 15 Magix AVC NVENC (Nvidia) encoding immediately crashing on Win10.

Card: NVidia 750Ti

FIX: Update to latest Nvidia drivers: 385.41

I had to upgrade my Driver for my Quadro K4200 for NVENC - and I went from 369.26 also to the latest Driver 385.41 (so to the same driver that you use I think).

However, and for whatever reason: I do not see here that this Driver crashes on Win 10, 385.41 runs here fine.

So can we be sure that it is this Driver really?

How do we render multiple of clips in vegas pro 15..?

Batch render script (as in all previous versions)

I have not expected much but I did expected that it will work. Unfortunately, it crashes like a hell :-(

It does not even open Vegas 14 projects normally, only after several attempts I could do it. But then.... it crashed when rendering.

Very disappointing, especially because I already paid. I just wonder why the hell Magix released beta version? Lack of money to finish 15?

Time to learn how to work with Lightworks.

I have not expected much but I did expected that it will work. Unfortunately, it crashes like a hell :-(

It does not even open Vegas 14 projects normally, only after several attempts I could do it. But then.... it crashed when rendering.

Very disappointing, especially because I already paid. I just wonder why the hell Magix released beta version? Lack of money to finish 15?

Time to learn how to work with Lightworks.

set DRAM to 0 still needed as far as I found for rendering.

( https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-stop-vegas-pro-hanging-during-rendering--104786/ )

The Magix AVC encoder - sped up my rendering times very nicely.

How can I reach a simplified Chinese in Vegas Pro 15.0.

I have tested Vegas Pro 15.0 .

But I find that 15.0 can't be switched to simplified Chinese by changing

registry language ID.

In 14.0 this method is valid but it can't work in 15.0.

Someone help me！

It was brought to our attention that a hack was available to change VEGAS Pro to run with some compiled Chinese resources.  This was in violation of a distribution agreement MAGIX has with the Chinese market.

I noticed that when I press CTRL+SHIFT+C it hides the event header buttons with the media info. Can I somehow hide only the event buttons?

This is a bug. I am very sorry about that. That option should only hide the buttons. We will have this remedied in an early update.

 I don't want the program to crush for a simple CTRL+Z - undo. :)

So far I test out, no issue with 'wild' undoing.

Usually it works normally but sometimes god knows why it just makes the program to crash. I can tell some situations when it's more likely to happen, but I will screen record my editing process and I will show you guys what I'm talking about in the next weeks.

Examples when it's more likely to crash: 1. When I undo more times at a time. 2. In large projects (lots of sound and video tracks) when I messed a lot with the Auto Ripple tool before. 3. When I do lots of small edits, modifications and I use more tools at a time it just happens.

I can't reproduce it intentionally, always different undo actions kill it.

Ctrl Z caused a mega crash for me. Ruined my project that I'd been working on for hours. The project freezes at 65% every time I try to load it (after a complete reboot). Even the backup of the same project won't load... same deal - freezes at 65%. Other projects from VP14 load. This was the one and only VP15 project I had and of course it wouldn't open in VP14.

HELP!

Tried numerous trouble shooting options. Display preview ram to 0, disable legacy GPU support, delete cache for all prerendered video. So then I changed my windows layout to default and tried to reload and somehow the failed project file opened. So I saved it as another file. But when I closed VP15 and reloaded it it does the same thing... hangs at 65% and won't load. opened a case with Magix. Don't know what else to do. Was so close to being able to edit and render this project! VP15 is so far a major let down on reliability.

I have not expected much but I did expected that it will work. Unfortunately, it crashes like a hell :-(

It does not even open Vegas 14 projects normally, only after several attempts I could do it. But then.... it crashed when rendering.

Very disappointing, especially because I already paid. I just wonder why the hell Magix released beta version? Lack of money to finish 15?

Time to learn how to work with Lightworks.

set DRAM to 0 still needed as far as I found for rendering.

( https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-stop-vegas-pro-hanging-during-rendering--104786/ )

Thanks set for your suggestion but do we have any idea why do we get all these ´improvements´ and features that do not work and we have to waste time to disable them? For me it is the third time that I bought new version of Vegas and the problems are the same. If they said this was beta version I would understand, but marketing such raw material as finished product is just not fair. This so called upgrades from one version of Vegas pro to higher cost about 250$ a year which is close to monthly payment for Lightworks. Magix, wake up! Respect our time and save us frustration!

I noticed that when I press CTRL+SHIFT+C it hides the event header buttons with the media info. Can I somehow hide only the event buttons?

This is a bug. I am very sorry about that. That option should only hide the buttons. We will have this remedied in an early update.

Thank you.

 I don't want the program to crush for a simple CTRL+Z - undo. :)

So far I test out, no issue with 'wild' undoing.

Usually it works normally but sometimes god knows why it just makes the program to crash. I can tell some situations when it's more likely to happen, but I will screen record my editing process and I will show you guys what I'm talking about in the next weeks.

Examples when it's more likely to crash: 1. When I undo more times at a time. 2. In large projects (lots of sound and video tracks) when I messed a lot with the Auto Ripple tool before. 3. When I do lots of small edits, modifications and I use more tools at a time it just happens.

I can't reproduce it intentionally, always different undo actions kill it.

Ctrl Z caused a mega crash for me. Ruined my project that I'd been working on for hours. The project freezes at 65% every time I try to load it (after a complete reboot). Even the backup of the same project won't load... same deal - freezes at 65%. Other projects from VP14 load. This was the one and only VP15 project I had and of course it wouldn't open in VP14.

HELP!

Tried numerous trouble shooting options. Display preview ram to 0, disable legacy GPU support, delete cache for all prerendered video. So then I changed my windows layout to default and tried to reload and somehow the failed project file opened. So I saved it as another file. But when I closed VP15 and reloaded it it does the same thing... hangs at 65% and won't load. opened a case with Magix. Don't know what else to do. Was so close to being able to edit and render this project! VP15 is so far a major let down on reliability.

 

Making backup copies on an external drive of such valuable works in progress is a must and never fails to save the day.

I just had a redo crash, I try to explain what I did:

I had 4 video channels, - expanded multicam track - lots of muted events and 8 audio channels. I had a fullscreen monitor with the footage I edit and a second screen for the timeline. I changed an even's size multiple times in a row, then I deleted it, then I changed an other even't length in an other track then I pressed two redos in a row and ! crash ! - And I had to use Task Manager to close Vegas Pro. Maybe I worked faster than Vegas could handle the instructions.

There was applied effects on all the video tracks> Sharpen, Levels, LAB Adjust, Color Corrector, - COMPOSITE

I did not use any 3rd party fx.

I know it's hard to recreate the crash intentionally but it would worth trying to.

It's a little pricey for the yearly upgrade. Even if I were to upgrade to the basic edit version at $199. It's too much.... I think $99. is better. Afterall if you're a user with previous versions, why duplicate the add ons over and over again?

 I don't want the program to crush for a simple CTRL+Z - undo. :)

So far I test out, no issue with 'wild' undoing.

Usually it works normally but sometimes god knows why it just makes the program to crash. I can tell some situations when it's more likely to happen, but I will screen record my editing process and I will show you guys what I'm talking about in the next weeks.

Examples when it's more likely to crash: 1. When I undo more times at a time. 2. In large projects (lots of sound and video tracks) when I messed a lot with the Auto Ripple tool before. 3. When I do lots of small edits, modifications and I use more tools at a time it just happens.

I can't reproduce it intentionally, always different undo actions kill it.

Ctrl Z caused a mega crash for me. Ruined my project that I'd been working on for hours. The project freezes at 65% every time I try to load it (after a complete reboot). Even the backup of the same project won't load... same deal - freezes at 65%. Other projects from VP14 load. This was the one and only VP15 project I had and of course it wouldn't open in VP14.

HELP!

Tried numerous trouble shooting options. Display preview ram to 0, disable legacy GPU support, delete cache for all prerendered video. So then I changed my windows layout to default and tried to reload and somehow the failed project file opened. So I saved it as another file. But when I closed VP15 and reloaded it it does the same thing... hangs at 65% and won't load. opened a case with Magix. Don't know what else to do. Was so close to being able to edit and render this project! VP15 is so far a major let down on reliability.

 

Making backup copies on an external drive of such valuable works in progress is a must and never fails to save the day.

Backup copies were made and are reacting the same, but other projects are not affected. There is something in this project that is different... what is unknown and I did or added nothing that was different than any other project in VP

It's a little pricey for the yearly upgrade. Even if I were to upgrade to the basic edit version at $199. It's too much.... I think $99. is better. Afterall if you're a user with previous versions, why duplicate the add ons over and over again?

I would not have minded that much because it is a long time I upgraded, I Am still using VP12. Which works reasonably well for me, still. However I am reluctant to invest 250$ for the quality presented in this build 177. I have not received any answer from Gary when the next upgrade will be available although I understand it is already available internally. My personal opinion is that it was a bad choice to release this build, the state it is in, to the customer, and so I have decided to wait a week or two to see wether the next upgrade will still be available within my 30 days trial period. If not, I have decided to contact Magix customer support with the request to postpone my trial period until the next update will be available, and then continue my trial with that one. In the meantime I decided to keep on using my VP12 which works ok for me.

Downloaded the trial for V15 to see if it had more reliable render with GPU acceleration enabled (it was no more reliable)...

Noted my rendered video was WATERMARKED with a floating "Vegas" square along the bottom... HUH?

I think the trial notes should say somewhere that all rendered output would be watermarked through the trial period. I wasted 2 hours with this render thinking the output would at least be usable if it completed.

Upon first launch of VEGAS PRO 15 (after s/n & loading modules), I get this error message that Microsoft .NET could not be initialized. I checked my computer and I have the latest version. I tried downloading and reinstalling the latest version and it would not let me continue saying the latest version is already installed. You cannot uninstall .NET without screwing-up your computer, so I'm stuck. Any suggestions?

@Barton-Santello In your OS take a look onto your "Windows features". There should be two .NET checkboxes and both should be checked. If not, check them both and restart your system.