Vegas Pro 21 - 315 Crashing

joshua-noesser wrote on 6/11/2024, 5:35 PM

I keep getting random crashes on the latest patch. 1st off, does anyone know how to do a clean install and revert everything back to how it comes preconfigured? I must have made 2 dozen changes over the last six months to make 21 stable. Every time it gets stable, they release a patch and break it. I have the crash report, but I can't upload it here, so I am unloading it to Dropbox. Link below.
https://www.dropbox.com/scl/fo/p5y0yeabiypvc69qbr07w/APXfgQ4_LKovG18WJAwDY0k?rlkey=arxr63cec6yzv98ix5whc5g6p&dl=0

Comments

RogerS wrote on 6/11/2024, 5:47 PM

Control+shift and double click the desktop shortcut to revert to default settings. The meaning of the settings did change from pre build 300 to post.

Many crashes are associated with media if you can share MediaInfo for what you mainly use.

joshua-noesser wrote on 6/11/2024, 6:20 PM

Control+shift and double click the desktop shortcut to revert to default settings. The meaning of the settings did change from pre build 300 to post.

Many crashes are associated with media if you can share MediaInfo for what you mainly use.

You have helped me more than once before. We went through the media on the previous patch and turned off a few settings to make it stable again. The media comes from a GoPro 11 and GH6 all running 10bit 4k 60fps. I have been using these cameras for a long time and never had any issues till the last few patches. You can find all this info if you search my posts. I am happy to drop in here if you want it.

As for when I do what you are saying above, does that also change all the bios changes we have had to made over the different patches? What all does this revert? We have made a lot of changes, more then just the top menus, so I am looking to convert everything back to OE. And start over as the Vegas team keeps saying they are fixing the problems but I never changed any settings back after the patches. I am thinking maybe they fixed it....

RogerS wrote on 6/11/2024, 7:16 PM

I can't really keep straight everyone's systems and media. I suggest adding the hardware to your signature on the forum like mine and media- MediaInfo is great to understand what we are dealing with.

There's a huge difference between VP 21.208 and lower and 300 and higher. The decoders that read the media are different and video engine is under construction.

Resetting VEGAS will return all changed internal settings to their defaults. You can save window layouts, etc. and they can be kept. Your projects etc. won't be affected. Nor will extensions, etc. as VEGAS will refind them.

https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-reset-vegas-pro-to-default-settings--104646/

Likely the most important settings to put back are in options/preferences/ file io. The meaning of "legacy AVC decoding" changed for example- if you checked it in 21.208 to avoid so4compound, checking it in 300+ gives you the so4compound decoder!

Gid wrote on 6/12/2024, 4:14 AM

............... You can find all this info if you search my posts. I am happy to drop in here if you want it.

@joshua-noesser You can't expect people to go searching through your past posts to find the information, you'll get limited to no replies that way, so yes post the relevant info on here.

Vegas Pro 18 - 22
Vegas Pro/Post 19
Boris Continuum & Sapphire, 
Silhouette Standalone + Plugin, 
Mocha Pro Standalone + Plugin, 
Boris Optics,
NewBlue TotalFX
Desktop PC Microsoft Windows 10 Pro - 64-Bit
ASUS PRO WS WRX80E-SAGE SE WIFI AMD Motherboard
AMD Ryzen Threadripper PRO 3975WX 3.5GHz 32 Core
Corsair iCUE H150i RGB PRO XT 360mm All-in-One Liquid CPU Cooler
RAM 256GB ( 8x Micron 32GB (1x 32GB) 2666MHz DDR4 RAM )
2x Western Digital Black SN850 2TB M.2-2280 SSD, 7000MB/s Read, 5100MB/s Write
(programs on one, project files on the other)
Graphics MSI GeForce RTX 3090 SUPRIM X 24GB OC GPU
ASUS ROG Thor 1200W Semi-Modular 80+ Platinum PSU 
Fractal Design Define 7 XL Dark TG Case with 3 Fans
Dell SE3223Q 31.5 Inch 4K UHD (3840x2160) Monitor, 60Hz, & an Acer 24" monitor.

At the moment my filming is done with a Samsung Galaxy S23 Ultra 5G & a GoPro Hero11 Black

I've been a Joiner/Carpenter for 40yrs, apprentice trained time served, I don't have an apprentice of my own so to share my knowledge I put videos on YouTube.

YouTube videos - https://www.youtube.com/c/Gidjoiner

 

joshua-noesser wrote on 7/18/2024, 7:23 PM

............... You can find all this info if you search my posts. I am happy to drop in here if you want it.

@joshua-noesser You can't expect people to go searching through your past posts to find the information, you'll get limited to no replies that way, so yes post the relevant info on here.

This was meant as a Thank you.

Any sorry for not getting back faster. I was traveling for the last month. Also sort of at my point with this software. After all the tweaks we got this software working okay last time. Cropping clips was smooth, play back was smooth, and then an update comes out and its just as broken as before. Now cropping is jolty, it crashes again, I am not sure what to do at this point.

joshua-noesser wrote on 7/18/2024, 7:35 PM

I can't really keep straight everyone's systems and media. I suggest adding the hardware to your signature on the forum like mine and media- MediaInfo is great to understand what we are dealing with.

There's a huge difference between VP 21.208 and lower and 300 and higher. The decoders that read the media are different and video engine is under construction.

Resetting VEGAS will return all changed internal settings to their defaults. You can save window layouts, etc. and they can be kept. Your projects etc. won't be affected. Nor will extensions, etc. as VEGAS will refind them.

https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-reset-vegas-pro-to-default-settings--104646/

Likely the most important settings to put back are in options/preferences/ file io. The meaning of "legacy AVC decoding" changed for example- if you checked it in 21.208 to avoid so4compound, checking it in 300+ gives you the so4compound decoder!

First off, I want to thank you for all the help. I don't think that came across. I enabled the legacy AVC and that seem to stabilize it. But for some reason some video files are laggy and others not. From the same camera. These are all files I have been using for a long time including the last buids that seems to be stable and not laggy at all. Any ideas?

It makes it hard to cut video as the cursor will just lag, but only on some clips and not all. Also doesn't matter on clip lengh. Which is what i thought at first. I have never had to run a proxy with this machine as the resources are no where near max. The ones that are laggy I can create a proxy which seems to help about half the time. Not really sure what is going on. Seems like some kind of setting issues or software issue.

i9-14900k

96GB Ram
4080 Nvidia

M1 Drives

If you have any ideas I will gladly take it.

RogerS wrote on 7/18/2024, 7:38 PM

Please double-check that all the media was recorded the same way- MediaInfo can help you confirm this. Bit depth (8 vs 10), codec (AVC vs HEVC), resolution, framerate, can all make big differences in performance. Clip length shouldn't be an issue.

Legacy AVC brings back the decoder that was standard in build 208 and older (though it has its own issues and works better for some media than others. With that one I'd use Intel QSV for hardware decoding over NVDEC).

joshua-noesser wrote on 7/18/2024, 9:21 PM

Please double-check that all the media was recorded the same way- MediaInfo can help you confirm this. Bit depth (8 vs 10), codec (AVC vs HEVC), resolution, framerate, can all make big differences in performance. Clip length shouldn't be an issue.

Legacy AVC brings back the decoder that was standard in build 208 and older (though it has its own issues and works better for some media than others. With that one I'd use Intel QSV for hardware decoding over NVDEC).

Same settings for all clips. Took over 200 videos and it is random to say the best. I noticed the better camera has a tad lag when scrolling but plays well. So it makes editing a little harder then easy. But haven't seen the inconsistencies like the info below. Just a reminder this problem is new with this release.

Again, appreciate the help. I am hoping we can get this version stable and working smooth.



 

General
Complete name                            : E:\Videos\Rubicon 2023 Sept 14\GP 11\Trip\GX010975.MP4
Format                                   : MPEG-4
Format profile                           : Base Media / Version 1
Codec ID                                 : mp41 (mp41)
File size                                : 300 MiB
Duration                                 : 20 s 907 ms
Overall bit rate                         : 120 Mb/s
Frame rate                               : 59.940 FPS
Encoded date                             : 2023-09-15 13:39:38 UTC
Tagged date                              : 2023-09-15 13:39:38 UTC

Video
ID                                       : 1
Format                                   : HEVC
Format/Info                              : High Efficiency Video Coding
Format profile                           : Main 10@L6@Main
Codec ID                                 : hvc1
Codec ID/Info                            : High Efficiency Video Coding
Duration                                 : 20 s 904 ms
Bit rate                                 : 120 Mb/s
Width                                    : 5 312 pixels
Height                                   : 2 988 pixels
Display aspect ratio                     : 16:9
Frame rate mode                          : Constant
Frame rate                               : 59.940 (60000/1001) FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 10 bits
Bits/(Pixel*Frame)                       : 0.126
Stream size                              : 299 MiB (100%)
Title                                    : GoPro H.265
Language                                 : English
Encoded date                             : 2023-09-15 13:39:38 UTC
Tagged date                              : 2023-09-15 13:39:38 UTC
Color range                              : Full
Color primaries                          : BT.709
Transfer characteristics                 : BT.709
Matrix coefficients                      : BT.709
Codec configuration box                  : hvcC

Audio
ID                                       : 2
Format                                   : AAC LC
Format/Info                              : Advanced Audio Codec Low Complexity
Codec ID                                 : mp4a-40-2
Duration                                 : 20 s 907 ms
Bit rate mode                            : Constant
Bit rate                                 : 192 kb/s
Nominal bit rate                         : 48.0 kb/s
Channel(s)                               : 2 channels
Channel layout                           : L R
Sampling rate                            : 48.0 kHz
Frame rate                               : 46.875 FPS (1024 SPF)
Compression mode                         : Lossy
Stream size                              : 483 KiB (0%)
Title                                    : GoPro AAC  
Language                                 : English
Encoded date                             : 2023-09-15 13:39:38 UTC
Tagged date                              : 2023-09-15 13:39:38 UTC

Other #1
ID                                       : 3
Type                                     : Time code
Format                                   : QuickTime TC
Duration                                 : 20 s 904 ms
Bit rate mode                            : Constant
Frame rate                               : 59.940 (60000/1001) FPS
Time code of first frame                 : 06:46:00:38
Time code of last frame                  : 06:46:21:51
Time code, stripped                      : Yes
Title                                    : GoPro TCD  
Language                                 : English
Encoded date                             : 2023-09-15 13:39:38 UTC
Tagged date                              : 2023-09-15 13:39:38 UTC

Other #2
ID                                       : 4
Type                                     : meta
Format                                   : gpmd
Codec ID                                 : gpmd
Duration                                 : 20 s 903 ms
Bit rate mode                            : Variable
Title                                    : GoPro MET  
Language                                 : English
Encoded date                             : 2023-09-15 13:39:38 UTC
Tagged date                              : 2023-09-15 13:39:38 UTC
Duration_LastFrame                       : -118

LewyLew wrote on 7/18/2024, 10:50 PM

getting the crashing as well. Uninstalled reinstalled it will not work

 

Extra Information
   File:                C:\Users\jimmy\AppData\Local\VEGAS Pro\21.0\gpu_video_x64.log

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 21.0 (Build 187)
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\WINDOWS\System32\DriverStore\FileRepository\c0315687.inf_amd64_374fae4a4c5ce87a\amdocl64.dll
   Fault Address:       0x00007FFD05AC2F98
   Fault Offset:        0x0000000000222F98

Fault Process Details
   Process Path:        E:\Program Files\VEGAS\VEGAS Pro 21.0\vegas210.exe
   Process Version:     Version 21.0 (Build 187)
   Process Description: VEGAS Pro
   Process Image Date:  2023-11-03 (Fri Nov 03) 01:23:24
 

fr0sty wrote on 7/19/2024, 2:05 AM

@lew You are using a very old build of VEGAS 21, try updating it. Update your GPU driver as well.

RogerS wrote on 7/19/2024, 2:57 AM

I'd test it with build 208 which you can download from here and is the final build in that line pre-revised video engine: https://www.vegascreativesoftware.info/us/forum/faq-where-can-i-download-vegas-pro-and-other-vegas-software--104782/

10-bit 5.3K HEVC will be tough on the system but it shouldn't crash.

Agree on the GPU driver- do a clean delete (ddu uninstaller or GPU maker tool) and then reinstall the current one.

VEGASDerek wrote on 7/19/2024, 6:36 AM

@LewyLew Why are you using such an old build? Are you using a cracked version of VPro 21?

vkmast wrote on 7/19/2024, 1:53 PM

A typo in the comment above. @VEGASDerek actually means VPro 21.

VEGASDerek wrote on 7/19/2024, 3:09 PM

Ha! Yes. Sorry...VEGAS Pro 22 is very much on my mind right now as the team is very busy in trying to get things complete for its release.

LewyLew wrote on 7/20/2024, 1:06 PM

probaly got mixed... let me find a fresh download or can you send me a link.. DUH...on my part.

vkmast wrote on 7/20/2024, 1:18 PM

@LewyLew please see the link in a comment from RogerS.

Reyfox wrote on 7/20/2024, 1:49 PM

Well, I would think that if you start the software, go to Help and Check for software updates, that would solve the problem. Or... I know when there were updates, opening the software, there were notification about it.

Newbie😁

Vegas Pro 22 (VP18-21 also installed)

Win 11 Pro always updated

AMD Ryzen 9 5950X 16 cores / 32 threads

32GB DDR4 3200

Sapphire RX6700XT 12GB Driver: 25.3.1

Gigabyte X570 Elite Motherboard

Panasonic G9, G7, FZ300

LewyLew wrote on 7/20/2024, 3:08 PM

Originally, I had the software from 20.0 and did all the updates. When I ran into the problem, I grabbed what was available, which was the old version. I just reinstalled Build 315 but still have the original crashing problem. Any recommendations?

Extra Information
   File:                C:\Users\jimmy\AppData\Local\VEGAS Pro\21.0\gpu_video_x64.log

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 21.0 (Build 315)
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\WINDOWS\System32\DriverStore\FileRepository\c0315687.inf_amd64_374fae4a4c5ce87a\amdocl64.dll
   Fault Address:       0x000000000FC727EA
   Fault Offset:        0x00000000002227EA

Fault Process Details
   Process Path:        E:\Program Files\VEGAS\VEGAS Pro 21.0\vegas210.exe
   Process Version:     Version 21.0 (Build 315)
   Process Description: VEGAS Pro
   Process Image Date:  2024-05-17 (Fri May 17) 02:43:04
 

 

Reyfox wrote on 7/20/2024, 3:15 PM

@LewyLew start your own post. You are hijacking the OP's post. When you do write up your own post, Read this POST and include information from "B" and "C" in your post. You have a blank user profile with zero information.

Newbie😁

Vegas Pro 22 (VP18-21 also installed)

Win 11 Pro always updated

AMD Ryzen 9 5950X 16 cores / 32 threads

32GB DDR4 3200

Sapphire RX6700XT 12GB Driver: 25.3.1

Gigabyte X570 Elite Motherboard

Panasonic G9, G7, FZ300

joshua-noesser wrote on 7/23/2024, 4:51 PM

@lew You are using a very old build of VEGAS 21, try updating it. Update your GPU driver as well.

Its vegas Build 315

joshua-noesser wrote on 7/23/2024, 4:53 PM

I'd test it with build 208 which you can download from here and is the final build in that line pre-revised video engine: https://www.vegascreativesoftware.info/us/forum/faq-where-can-i-download-vegas-pro-and-other-vegas-software--104782/

10-bit 5.3K HEVC will be tough on the system but it shouldn't crash.

Agree on the GPU driver- do a clean delete (ddu uninstaller or GPU maker tool) and then reinstall the current one.

I might do this. The only downside of 208 was i could see live updates on the video edits (Using other tools)

joshua-noesser wrote on 7/23/2024, 4:54 PM

Originally, I had the software from 20.0 and did all the updates. When I ran into the problem, I grabbed what was available, which was the old version. I just reinstalled Build 315 but still have the original crashing problem. Any recommendations?

Extra Information
   File:                C:\Users\jimmy\AppData\Local\VEGAS Pro\21.0\gpu_video_x64.log

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 21.0 (Build 315)
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\WINDOWS\System32\DriverStore\FileRepository\c0315687.inf_amd64_374fae4a4c5ce87a\amdocl64.dll
   Fault Address:       0x000000000FC727EA
   Fault Offset:        0x00000000002227EA

Fault Process Details
   Process Path:        E:\Program Files\VEGAS\VEGAS Pro 21.0\vegas210.exe
   Process Version:     Version 21.0 (Build 315)
   Process Description: VEGAS Pro
   Process Image Date:  2024-05-17 (Fri May 17) 02:43:04
 

 

I enabled legacy AVC decoding and that seemed to solve the crashing problem (At least so far). Now just have to get through what ever this weird bug is

joshua-noesser wrote on 7/23/2024, 5:01 PM

FYI - I just restarted working on the latest project and now i get that weird latency bug with clips that weren't having the issues before. So it isn't tied to the clip it self. Its just what it feels like that time.