Vegas 17 requirements: Processor: 6th Generation Intel Core i5 (or AMD equivalent) or better. 2.5 Ghz and 4 Core minimum. For 4k, 7th Generation Intel Core i7 (or AMD equivalent) or better. 3.0 Ghz and 8 Core minimum

If you're editing 4k, that could be some of the issue.

Also, try to pull one of the GPUs out (or disable it in device manager), reboot the system, and see how Vegas behaves with only 1 GPU present.

@AlesCZ Just wait for the first update. It’s very unstable at the moment unless you’re doing a very simple project. If you have a previous version use it instead. You can transfer your VP17 project using copy and paste from VP17 to say VP1n earlier version. You may lose some VP17 functionality, but it shouldn’t be too long for the update hopefully.

Not saying that say VP16 is perfect, but it is fairly robust, just yesterday I at last finished an old 5 hrs. + project in VP16 and it froze at 92% on the 5th. of 19 regions while batch rendering regions. I just removed the first 4 sets of region markers and it then rendered out the rest. Although I was tempted to use VP17 because of the nice new features, I resisted.

VP17 should be coming out of hospital soon, best of luck.

.NET framework 4.8.0；C++ runtime；DirectX runtime；decoding pack；

@AlesCZ Just wait for the first update. It’s very unstable at the moment unless you’re doing a very simple project. If you have a previous version use it instead. You can transfer your VP17 project using copy and paste from VP17 to say VP1n earlier version. You may lose some VP17 functionality, but it shouldn’t be too long for the update hopefully.

If you consider 4 4k camera angles and a project spanning almost 3 hours with almost half a terabyte of video and thousands of edits and effects applied a "simple project", then yeah, it's only good for simple projects.

read this thread created by meister Nick:

https://www.vegascreativesoftware.info/us/forum/faq-troubleshooting-crashing-and-stability--104785/

OK folks, thank you very much for advices! I'll try to tweak it, or wait for the V17 update.

Have a nice day!

@AlesCZ Just wait for the first update. It’s very unstable at the moment unless you’re doing a very simple project. If you have a previous version use it instead. You can transfer your VP17 project using copy and paste from VP17 to say VP1n earlier version. You may lose some VP17 functionality, but it shouldn’t be too long for the update hopefully.

If you consider 4 4k camera angles and a project spanning almost 3 hours with almost half a terabyte of video and thousands of edits and effects applied a "simple project", then yeah, it's only good for simple projects.

I am happy for you if that's your V17 experience, but I have to say it isn't mine and I think I share that with many users out there. I've been testing a beast with i9-9900K, 32 G ram, an RTX2080ti with 11 gig video RAM, and everything else I could want (yes, SSDs, etc.) and Vegas 17 repetitively crashed on a 12-minute project with many dissolves but no other Fx at all. So, no it's not inadequate hardware. V17 seems extremely sensitive to odd/unusual video source files, but we all know there are better ways of handling odd video other than freezing dead with no error message, no explanation. V16 seems better for me although far from perfect, so yeah, 17 needs some help.

The fact is only a limited number of users on a limited number of hardware configs are having any issues, and many times they are resolved by things like GPU driver updates or rollbacks. Vegas 17 has a few bugs, but for most of us, it's holding up better than 16 did. There's an update on the way before long, so if making a thread about your issue and us going through the troubleshooting isn't enough to solve your issue, then it won't be long before an update likely will.

@thom-drewke Heres two links to some VP17 known issues, might be of help ...

Nicks ...

https://www.vegascreativesoftware.info/us/forum/known-issues-in-the-latest-version-of-vegas-pro--108942/?page=5#ca729921

and WhyDats ...

https://www.vegascreativesoftware.info/us/forum/vegas-pro-17-temporary-list-of-known-bugs-issues-so-far--117008/#ca729763

“but I have to say it isn't mine and I think I share that with many users out there.” I concur completely.

In danger of repeating myself but anyway ... IMHO don’t use VP17 on anything complex/important until the first update arrives, if you can do it in an earlier version. Its simply too buggy and unstable, my experience and plenty of others.

 

In danger of repeating myself but anyway ... IMHO don’t use VP17 on anything complex/important until the first update arrives, if you can do it in an earlier version. Its simply too buggy and unstable, my experience and plenty of others.

 

Thanks for repeating this ,... it should realy be stressed again and again

Consider VP17 upgrade ,.. but only in a max-solid version ,.. and only on BF sale with a significant reduction

1. But does "first update" historically always iron out essential bugs in a sufficient way ?

2. Is it likely to be updated before the Black Friday 29 November ?

My hardware is compareable to OP ,... just I only got a single GTX1060-6GB ,... but 32GB ram

@AlesCZ Just wait for the first update. It’s very unstable at the moment unless you’re doing a very simple project. If you have a previous version use it instead. You can transfer your VP17 project using copy and paste from VP17 to say VP1n earlier version. You may lose some VP17 functionality, but it shouldn’t be too long for the update hopefully.

If you consider 4 4k camera angles and a project spanning almost 3 hours with almost half a terabyte of video and thousands of edits and effects applied a "simple project", then yeah, it's only good for simple projects.

I am happy for you if that's your V17 experience, but I have to say it isn't mine and I think I share that with many users out there. I've been testing a beast with i9-9900K, 32 G ram, an RTX2080ti with 11 gig video RAM, and everything else I could want (yes, SSDs, etc.) and Vegas 17 repetitively crashed on a 12-minute project with many dissolves but no other Fx at all. So, no it's not inadequate hardware. V17 seems extremely sensitive to odd/unusual video source files, but we all know there are better ways of handling odd video other than freezing dead with no error message, no explanation. V16 seems better for me although far from perfect, so yeah, 17 needs some help.

MAGIX needs to update the video engine... and by that I mean beyond just adding in Intel/Nvidia/AMD Decode/Encode Acceleration.

Also, how does the NLE behave when you use Effects that aren't native to VEGAS, but perform the some function (i.e. a BorisFX or NewBlue FX Dissolve, instead of a VEGAS Pro Dissolve)? Most of VEGAS' effects are old as dirt, and have been out of development for a decade. Are we sure that old code isn't causing the instabilities?

People with more comprehensive setups (in terms of plug-ins, etc.) seem to say things are fine on large projects, while people using mostly in-box features are reporting instabilities; so I think this is worth exploring. Is it possible that they are "maintaining stability" by virtue of not using items that trigger the instabilities?

Most users don't post on forums, so we can't really say how many people are [or are not] affected by them. Many users are not likely to even report the issues or contact tech support (something MAGIX does not make "easy," anyways).

I don't use any non-native effects and have few issues, and none that do not have a workaround or solution already.

Historically there have been big bug fixes not long after initial release, and hopefully the same will be true with 17 and address some of the issues people here have uncovered.

I can confirm there is an update on the way in the near future, as the Magix team have revealed that much themselves.

Yes...the update is going though some final testing right now. It should not be too much longer.