Vegas Pro 17 Crash on Updated Stabilizer

Shiro wrote on 9/13/2019, 7:35 AM

I dont know if its a bug in the software but the builtin Video stabilization effect makes my Vegas pro 17 crash. I've tried different file types and recompiling the source file but that doesnt seem to work. I've reinstalled Vegas 16 and tested the builtin Video Stabilizer on that with the same source file and it seems to work just fine. The crash only happens on Vegas Pro 17. Any thoughts on how to fix this? I appreciate the help.

Comments

j-v wrote on 9/13/2019, 8:10 AM

To use that old stabilizer there is no need to reïnstall another version, you can also use that one in VPro 17 by this setting

met vriendelijke groet
Jan

Camera : Pan X900, GoPro Hero7 Hero Black, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W10, i7 7900 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti.
Laptop  :Asus ROG GL753VD, W10 home, version 1903 build 18.362,295 CPU i7 7700HQ, 16 GB RAM, GeF. GTX 1050 (2 GB) + Int. HD Graphics 630(2GB).VP 15,16,17 and VMS PL 15,16 are installed
Both Nvidia GPU's have driver version 431.86 Studio Drivers
TV      :LG 4K 55EG960V

Dutch video tutorials for beginners

My slogan is: BE OR BECOME A STEMCELL DONOR !!!

Shiro wrote on 9/13/2019, 9:19 AM

To use that old stabilizer there is no need to reïnstall another version, you can also use that one in VPro 17 by this setting

Somehow it still doesn't work even with the old stabilizer, it just crashes halfway through like usual. Thanks anyways, I hope this bug gets fixed in future updates.

j-v wrote on 9/13/2019, 11:06 AM

Nothing wrong with that new Vegas Stabilisation of VP17.
Works very good, so good I not need to use Mercalli 4 anymore.
Works now on events and you get at the start a message how to handle.
Seek the problem on your used hardware and drivers from which you didnot tell anything.

met vriendelijke groet
Jan

Camera : Pan X900, GoPro Hero7 Hero Black, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W10, i7 7900 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti.
Laptop  :Asus ROG GL753VD, W10 home, version 1903 build 18.362,295 CPU i7 7700HQ, 16 GB RAM, GeF. GTX 1050 (2 GB) + Int. HD Graphics 630(2GB).VP 15,16,17 and VMS PL 15,16 are installed
Both Nvidia GPU's have driver version 431.86 Studio Drivers
TV      :LG 4K 55EG960V

Dutch video tutorials for beginners

My slogan is: BE OR BECOME A STEMCELL DONOR !!!

Shiro wrote on 9/14/2019, 2:14 AM

Nothing wrong with that new Vegas Stabilisation of VP17.
Works very good, so good I not need to use Mercalli 4 anymore.
Works now on events and you get at the start a message how to handle.
Seek the problem on your used hardware and drivers from which you didnot tell anything.

From what I know, the hardware I use is surely capable of using Vegas Pro as Ive been able to use different Video Editing software smoothly like Premiere Pro and Hitfilm which are way heavier and are more resource intensive than Vegas

The Hardware I use:

Motherboard: Gigabyte B250 FinTech

CPU: Intel Core i5 7400

RAM: 16GB DDR4 @ 2400Mhz

GPU: Nvidia GTX 1060 (4GB) + Intel HD 630

Storage: Sandisk 480GB SSD + 2TB HDD (7400rpm)

All my drivers are updated to the latest version and are all working properly

Ive also found out that when I use the Stabilizer with "Accurate" analyze method, it crashes halfway through like usual. But when I change it to "Fast" method it works smoothly without crashing. So I found a workaround for this, when I stabilize a footage Id have to analyze it in Fast method and clear the motion data and revert it back to Accurate method to analyze and it and would work properly all throughout. And then theres another problem I recently found, the bezier masking doesnt work properly like the stabilizer. When tracking, Vegas crashes halfway through the process just like what happens on the stabilizer. As of now I havent found an workaround for this yet.

matthias-krutz wrote on 9/14/2019, 2:54 AM

I have only found one clip so far, which crashes in VP16. The reason: an abrupt change of scene in the last frame. I could imagine that abrupt changes could be a reason. These jumps can not be stabilized. At this point, a cut must be made and the regions must be stabilized separately. Now in VP17 it is very easy to use the Stabilizer as Event FX.
Of course, Vegas should not crash, so it would be helpful if you could provide a short example clip for the developers.

fr0sty wrote on 9/14/2019, 4:53 AM

Your hardware is actually on the lower end of Vegas' recommended specs, but as long as you're not trying to edit/stabilize 4k, you should do ok.

Operating system: Microsoft® Windows 10 (64-bit)

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

RAM: 8 GB RAM minimum (16 GB recommended; 32 GB recommended for 4K)

Hard drive space: 1.5 GB hard-disk space for program installation; Solid-state disk (SSD) or high-speed multi-disk RAID for 4K media

Other: Microsoft .NET Framework 4.0 SP1 (included on application disc)

Internet connection: Required for registering and validating the program, as well as for some program functions. Program requires one-time registration.

Program languages

English, Deutsch, Español, Francais

Supported GPU

NVIDIA

For hardware rendering (NVEnc):
NVIDIA® GeForce 9XX series or higher with 4 GB

AMD/ATI

AMD/ATI® Radeon with 4 GB and VCE 3.0 or higher (Radeon Pro series with 8 GB for HDR and 32 bit projects)

Intel

Intel® GPU HD Graphics 530 series or higher

Supported formats

Shiro wrote on 9/14/2019, 5:07 AM

Your hardware is actually on the lower end of Vegas' recommended specs, but as long as you're not trying to edit/stabilize 4k, you should do ok.

Operating system: Microsoft® Windows 10 (64-bit)

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

RAM: 8 GB RAM minimum (16 GB recommended; 32 GB recommended for 4K)

Hard drive space: 1.5 GB hard-disk space for program installation; Solid-state disk (SSD) or high-speed multi-disk RAID for 4K media

Other: Microsoft .NET Framework 4.0 SP1 (included on application disc)

Internet connection: Required for registering and validating the program, as well as for some program functions. Program requires one-time registration.

Program languages

English, Deutsch, Español, Francais

Supported GPU

NVIDIA

For hardware rendering (NVEnc):
NVIDIA® GeForce 9XX series or higher with 4 GB

AMD/ATI

AMD/ATI® Radeon with 4 GB and VCE 3.0 or higher (Radeon Pro series with 8 GB for HDR and 32 bit projects)

Intel

Intel® GPU HD Graphics 530 series or higher

Supported formats

Yeah I only edit 720p and 1080p clips I dont do 4k cuz Im well aware of my specs. Ive even tried clips that have even lower resolution but still crashes.

Shiro wrote on 9/14/2019, 5:24 AM

I have only found one clip so far, which crashes in VP16. The reason: an abrupt change of scene in the last frame. I could imagine that abrupt changes could be a reason. These jumps can not be stabilized. At this point, a cut must be made and the regions must be stabilized separately. Now in VP17 it is very easy to use the Stabilizer as Event FX.
Of course, Vegas should not crash, so it would be helpful if you could provide a short example clip for the developers.

I cant actually provide a specific example clip since I've tried using different types of clips countless times, varying from resolution, size, filetype, bitrate etc. Literally every type of video file I throw at it, it would still crash(on Accurate method that is). Out of curiosity I've even attempted to use the stabilization effect(in Accurate method) on a still image(jpg & png) and it would STILL crash. Even trying to reinstall the whole software, the crash still persists. On the other hand, my VP16 stabilization works just fine. It would seem that the crash only happens on my VP17.

j-v wrote on 9/14/2019, 7:00 AM

Did you already reset V17?

met vriendelijke groet
Jan

Camera : Pan X900, GoPro Hero7 Hero Black, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W10, i7 7900 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti.
Laptop  :Asus ROG GL753VD, W10 home, version 1903 build 18.362,295 CPU i7 7700HQ, 16 GB RAM, GeF. GTX 1050 (2 GB) + Int. HD Graphics 630(2GB).VP 15,16,17 and VMS PL 15,16 are installed
Both Nvidia GPU's have driver version 431.86 Studio Drivers
TV      :LG 4K 55EG960V

Dutch video tutorials for beginners

My slogan is: BE OR BECOME A STEMCELL DONOR !!!

Shiro wrote on 9/26/2019, 2:36 AM

Well it looks like the bug's fixed in the new build update (Build 321)

MagixPascal wrote on 9/26/2019, 10:25 AM

@Shiro Could you give us some feedback for the crash? Is it fixed in the stabilizer and Bezier masking?

Shiro wrote on 9/27/2019, 6:44 AM

@Shiro Could you give us some feedback for the crash? Is it fixed in the stabilizer and Bezier masking?

Both are actually working fine now thanks for asking😄