What do I need to do to make Vegas 17 stable?

AlesCZ wrote on 9/14/2019, 1:54 PM

Hello,

how to make Vegas Pro 17 stable on my system? During video editing (h264), Vegas crashes several times within one hour. Very randomly. I do not know what to do.

My system:
Win 10 64bit

i7 4790k

GTX1080, GTX1070(no display) , drivers 431.86 studio

16GB RAM

__________________________________________________________________________
I understand that it is difficult to determine the cause of the problem, but other software works fine. (Cinema 4D, Affinity Photo, Blender, Davinci Resolve).

 

What should I do with it?

Comments

LongIslanderrr wrote on 9/14/2019, 2:11 PM

They are most definitely working on an update I am not able to make Vegas 17 stable on my system either I am using 16 until they patch the bugs

fr0sty wrote on 9/14/2019, 3:06 PM

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.

JN_ wrote on 9/14/2019, 6:20 PM

@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.

Last changed by JN_ on 9/15/2019, 2:53 AM, changed a total of 4 times.

 

Desktop and Laptop basic specs ...

Both run Win 10, has latest updates ...

Running latest ver. of Vegas Pro with latest updates.

VP13 B453 also.

Vegaseur and Pluraleyes installed on both ...

Quicktime 7.79.80.95

PC ...

i9 9900K, Intel Graphics 630. Nov 2018.

Mem. 32gb DDR4

Graphics card .. Nvidia Rtx 2080 Ti

Nvidia Graphics driver .. latest Studio driver.

Latest Intel Graphics driver

 

Laptop ... (Acer Predator G9-793-77AC)

CPU .. i7-6700HQ Skylake-H

Memory ..16GB DDR4 

Graphics card .. Nvidia GTX 1070, latest Studio driver.

lan-mLMC wrote on 9/14/2019, 7:00 PM

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

fr0sty wrote on 9/14/2019, 7:43 PM

@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.

AVsupport wrote on 9/15/2019, 2:53 AM

read this thread created by meister Nick:

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

 

Last changed by AVsupport on 9/15/2019, 2:54 AM, changed a total of 1 times.

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

16GB (2x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

AlesCZ wrote on 9/17/2019, 12:47 PM

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

Have a nice day!

thom-drewke wrote on 9/17/2019, 1:25 PM

@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.

Right now watching my Vegas 16 Pro crash on my temporary HP Omen 875 series, i9-9900K at base 3.60GHz, 32 G ram, Windows 10 Pro (64 bit of course), C: drive is brand new 1 TB Intel SSD plus 2 TB D: drive for storage and GEForce RTX 2080ti

fr0sty wrote on 9/17/2019, 1:31 PM

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.

JN_ wrote on 9/17/2019, 6:03 PM

@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.

 

Last changed by JN_ on 9/17/2019, 6:08 PM, changed a total of 2 times.

 

Desktop and Laptop basic specs ...

Both run Win 10, has latest updates ...

Running latest ver. of Vegas Pro with latest updates.

VP13 B453 also.

Vegaseur and Pluraleyes installed on both ...

Quicktime 7.79.80.95

PC ...

i9 9900K, Intel Graphics 630. Nov 2018.

Mem. 32gb DDR4

Graphics card .. Nvidia Rtx 2080 Ti

Nvidia Graphics driver .. latest Studio driver.

Latest Intel Graphics driver

 

Laptop ... (Acer Predator G9-793-77AC)

CPU .. i7-6700HQ Skylake-H

Memory ..16GB DDR4 

Graphics card .. Nvidia GTX 1070, latest Studio driver.

Mister Mahler wrote on 9/17/2019, 10:24 PM

 

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

Editor_101 wrote on 9/17/2019, 10:27 PM

@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).

fr0sty wrote on 9/17/2019, 11:20 PM

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

RogerS wrote on 9/19/2019, 10:22 AM

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.

fr0sty wrote on 9/19/2019, 11:05 AM

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

MagixDerek wrote on 9/19/2019, 11:09 AM

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

AlesCZ wrote on 9/19/2019, 1:50 PM

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

By the way, white balance is not neutral by default. But you may already know that. :)