Vegas always crashes and the damn gray screen always appears

vagnerdesouza wrote on 8/28/2023, 10:10 AM

I always had problems with crashes in Vegas Pro. But for a few days now, things have only gotten worse. Does it have anything to do with the release of version 21? No matter what machine I work on, Vegas Pro has an unsolved source file access issue. It ALWAYS crashes.

When I edited with the source files on External Hard Drives, connected with a USB 3.0 cable, I thought that the crashes were due to the slowness of mechanical HDs. But now I'm using an M.2 PCIe Gen. 4.0 ultra fast 7000MB/s and still Vegas Pro crashes.

https://shop.kingston.com/products/kc3000-pcie-4-0-nvme-m-2-ssd?variant=41041994842304

Today I have a "modest" Ryzen 9 5950X machine, 4ghz, 16 cores, 32 threads, 32 GB DDR4 Ram, a GeForce 1050 Ti video card, with NVidia Studio Driver always updated. Ever!

These crashes do not occur in Adobe Premiere or Davinci Resolve. Only occur in Vegas Pro!

How crashes happen: They only happen when I press the space bar. It's like a game of chance: I don't know which time I press the spacebar and the program will crash. I just know that this is a mistake on the part of the software programmers, and I can't stand editing in a program like that anymore.

I edit in Vegas since 2003. Since the time Vegas belonged to the company Sonic Foundry. Almost daily. I have 20 years of full Vegas experience and I know what I'm talking about: PLEASE MAKE THE PROGRAM STOP CRASHING!

Comments

mofobo wrote on 8/28/2023, 10:24 AM

Not much fun praying that autosave did its job before these grey screen crashes happen. I have no solution, but Im suffering the same issues. Hope to get it solved.

Jack S wrote on 8/28/2023, 10:38 AM

@mofobo I'm using VP21 and it's rock solid. Dare I say it, no crashes since starting to use it. I know that's no consolation to you, but my advice would be, to use Live Save to supplement Autosave. I still have Live Save active even though I'm absolutely confident that I won't have any crashes.
You should also post MediaInfo details about the media you're using. It's known that VP has issues with certain codecs.

My system
Genshin Infinity Gaming PC
Motherboard Gigabyte H610M H: m-ATX w/, USB 3.2, 1 x M.2
Power Supply Corsair RM750X
Intel Core i7-13700K - 16-Core [8P @ 3.4GHz-5.4GHz / 8E @ 2.50GHz-4.20GHz]
30MB Cache + UHD Graphics, Ultimate OC Compatible
Case Fan 4 x CyberPowerPC Hyperloop 120mm ARGB & PWM Fan Kit
CPU Fan CyberPowerPC Master Liquid LITE 360 ARGB AIO Liquid Cooler, Ultimate OC Compatible
Memory 32GB (2 x 16GB) DDR5/5200MHz Corsair Vengeance RGB
MSI GeForce RTX 4060 Ti 8GB - Ray Tracing Technology, DX12, VR Ready, HDMI, DP
System drive 1TB WD Black SN770 M.2 NVMe PCIe SSD - 5150MB/s Read & 4900MB/s Write
Storage 2 x 2TB Seagate BarraCuda SATA-III 6.0Gb/s 7200RPM
Windows 11 Home (x64)
Monitors
Generic Monitor (PHL 222V8) connected to GeForce RTX 4060 Ti
Generic Monitor (SAMSUNG) connected to iGPU

Camcorder
SONY Handycam HDR-XR550VE

Jack S wrote on 8/28/2023, 10:40 AM

@vagnerdesouza Presumably you're using VP20 (your grey screenshot implies that). Are you suggesting that the release of VP21 is somehow causing your system to crash more often?

My system
Genshin Infinity Gaming PC
Motherboard Gigabyte H610M H: m-ATX w/, USB 3.2, 1 x M.2
Power Supply Corsair RM750X
Intel Core i7-13700K - 16-Core [8P @ 3.4GHz-5.4GHz / 8E @ 2.50GHz-4.20GHz]
30MB Cache + UHD Graphics, Ultimate OC Compatible
Case Fan 4 x CyberPowerPC Hyperloop 120mm ARGB & PWM Fan Kit
CPU Fan CyberPowerPC Master Liquid LITE 360 ARGB AIO Liquid Cooler, Ultimate OC Compatible
Memory 32GB (2 x 16GB) DDR5/5200MHz Corsair Vengeance RGB
MSI GeForce RTX 4060 Ti 8GB - Ray Tracing Technology, DX12, VR Ready, HDMI, DP
System drive 1TB WD Black SN770 M.2 NVMe PCIe SSD - 5150MB/s Read & 4900MB/s Write
Storage 2 x 2TB Seagate BarraCuda SATA-III 6.0Gb/s 7200RPM
Windows 11 Home (x64)
Monitors
Generic Monitor (PHL 222V8) connected to GeForce RTX 4060 Ti
Generic Monitor (SAMSUNG) connected to iGPU

Camcorder
SONY Handycam HDR-XR550VE

RogerS wrote on 8/28/2023, 6:21 PM

Crashes are very frustrating. What media are you working with specifically?

https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

vagnerdesouza wrote on 8/29/2023, 8:10 AM

Not much fun praying that autosave did its job before these grey screen crashes happen. I have no solution, but Im suffering the same issues. Hope to get it solved.

I'm hitting Ctrl+S every time before hitting the space bar. Still, shit happens.
What the program should do is, every time the user presses the spacebar, check if the system is ready to run the timeline or not. I no longer think it's a problem of slowness when accessing the source video, because my M.2 has a speed of 7000MB/s.

vagnerdesouza wrote on 8/29/2023, 8:18 AM

@mofobo I'm using VP21 and it's rock solid. Dare I say it, no crashes since starting to use it.

I was very happy with my Vegas Pro 18. It ran fine, no crashes. Then they released VP19, and the VP18 crashes started. I skipped the VP19 version as the upgrade price was absurd. I bought the VP20 upgrade and was happy for a while. It crashed on rare occasions. Then they released the VP21, and the VP20 crashes increased exponentially. They'll say it's a conspiracy theory. But it is not theory. I'm living it firsthand. On time: The price to upgrade from VP20 to VP21 is 75% of the price of a new purchase. THIS is absurdity par excellence.

bitman wrote on 8/29/2023, 8:48 AM

@vagnerdesouza

The release of vp21 should not have an impact of the local workings of vp20, unless, but that is a wild guess, maybe the Vegas hub / hub explorer has something to do with it (going to the appropriate servers on the internet which may have gone trough changes or are updated for Vegas 21...). That being said, you can eastly rule this out by logging out of the hub.

The best way to tackle this is to start a new small test project and gradually add some media you are having trouble with and observe if the issue still persists.

Also check the hardware integrity of your system (mem test, etc.) and check if you have got some recent windows updates coinciding with the release of VP21.

A software integrity check of the windows system files can sometimes reveal a corrupted system file and repair it.

Last changed by bitman on 8/29/2023, 8:49 AM, changed a total of 1 times.

APPS: VIDEO: VP 365 suite (VP 22 build 194) VP 21 build 315, VP 365 20, VP 19 post (latest build -651), (uninstalled VP 12,13,14,15,16 Suite,17, VP18 post), Vegasaur, a lot of NEWBLUE plugins, Mercalli 6.0, Respeedr, Vasco Da Gamma 17 HDpro XXL, Boris Continuum 2025, Davinci Resolve Studio 18, SOUND: RX 10 advanced Audio Editor, Sound Forge Pro 18, Spectral Layers Pro 10, Audacity, FOTO: Zoner studio X, DXO photolab (8), Luminar, Topaz...

  • OS: Windows 11 Pro 64, version 24H2 (since October 2024)
  • CPU: i9-13900K (upgraded my former CPU i9-12900K),
  • Air Cooler: Noctua NH-D15 G2 HBC (September 2024 upgrade from Noctua NH-D15s)
  • RAM: DDR5 Corsair 64GB (5600-40 Vengeance)
  • Graphics card: ASUS GeForce RTX 3090 TUF OC GAMING (24GB) 
  • Monitor: LG 38 inch ultra-wide (21x9) - Resolution: 3840x1600
  • C-drive: Corsair MP600 PRO XT NVMe SSD 4TB (PCIe Gen. 4)
  • Video drives: Samsung NVMe SSD 2TB (980 pro and 970 EVO plus) each 2TB
  • Mass Data storage & Backup: WD gold 6TB + WD Yellow 4TB
  • MOBO: Gigabyte Z690 AORUS MASTER
  • PSU: Corsair HX1500i, Case: Fractal Design Define 7 (PCGH edition)
  • Misc.: Logitech G915, Evoluent Vertical Mouse, shuttlePROv2

 

 

RogerS wrote on 8/29/2023, 8:54 AM

Can you share the media info? That's the biggest variable (are you using different types of media now than when you started editing with 20?)

21 shouldn't affect 20 directly.

bitman wrote on 8/29/2023, 9:01 AM

@vagnerdesouza Just one thing to mention, I noticed you are running affinity photo application while using Vegas. Normally that should not be an issue, but you mentioned that it crashes with an unsolved source file access issue. Maybe the the other program is still holding the media files preventing access by Vegas...

APPS: VIDEO: VP 365 suite (VP 22 build 194) VP 21 build 315, VP 365 20, VP 19 post (latest build -651), (uninstalled VP 12,13,14,15,16 Suite,17, VP18 post), Vegasaur, a lot of NEWBLUE plugins, Mercalli 6.0, Respeedr, Vasco Da Gamma 17 HDpro XXL, Boris Continuum 2025, Davinci Resolve Studio 18, SOUND: RX 10 advanced Audio Editor, Sound Forge Pro 18, Spectral Layers Pro 10, Audacity, FOTO: Zoner studio X, DXO photolab (8), Luminar, Topaz...

  • OS: Windows 11 Pro 64, version 24H2 (since October 2024)
  • CPU: i9-13900K (upgraded my former CPU i9-12900K),
  • Air Cooler: Noctua NH-D15 G2 HBC (September 2024 upgrade from Noctua NH-D15s)
  • RAM: DDR5 Corsair 64GB (5600-40 Vengeance)
  • Graphics card: ASUS GeForce RTX 3090 TUF OC GAMING (24GB) 
  • Monitor: LG 38 inch ultra-wide (21x9) - Resolution: 3840x1600
  • C-drive: Corsair MP600 PRO XT NVMe SSD 4TB (PCIe Gen. 4)
  • Video drives: Samsung NVMe SSD 2TB (980 pro and 970 EVO plus) each 2TB
  • Mass Data storage & Backup: WD gold 6TB + WD Yellow 4TB
  • MOBO: Gigabyte Z690 AORUS MASTER
  • PSU: Corsair HX1500i, Case: Fractal Design Define 7 (PCGH edition)
  • Misc.: Logitech G915, Evoluent Vertical Mouse, shuttlePROv2

 

 

bitman wrote on 8/29/2023, 9:15 AM

@vagnerdesouza Using the restart option instead of shut down option - of your PC - once in a while may clear things up, since all the drivers and applications will initialize properly (and not use the saved and possible corrupt state of the last boot to save time on startup).

APPS: VIDEO: VP 365 suite (VP 22 build 194) VP 21 build 315, VP 365 20, VP 19 post (latest build -651), (uninstalled VP 12,13,14,15,16 Suite,17, VP18 post), Vegasaur, a lot of NEWBLUE plugins, Mercalli 6.0, Respeedr, Vasco Da Gamma 17 HDpro XXL, Boris Continuum 2025, Davinci Resolve Studio 18, SOUND: RX 10 advanced Audio Editor, Sound Forge Pro 18, Spectral Layers Pro 10, Audacity, FOTO: Zoner studio X, DXO photolab (8), Luminar, Topaz...

  • OS: Windows 11 Pro 64, version 24H2 (since October 2024)
  • CPU: i9-13900K (upgraded my former CPU i9-12900K),
  • Air Cooler: Noctua NH-D15 G2 HBC (September 2024 upgrade from Noctua NH-D15s)
  • RAM: DDR5 Corsair 64GB (5600-40 Vengeance)
  • Graphics card: ASUS GeForce RTX 3090 TUF OC GAMING (24GB) 
  • Monitor: LG 38 inch ultra-wide (21x9) - Resolution: 3840x1600
  • C-drive: Corsair MP600 PRO XT NVMe SSD 4TB (PCIe Gen. 4)
  • Video drives: Samsung NVMe SSD 2TB (980 pro and 970 EVO plus) each 2TB
  • Mass Data storage & Backup: WD gold 6TB + WD Yellow 4TB
  • MOBO: Gigabyte Z690 AORUS MASTER
  • PSU: Corsair HX1500i, Case: Fractal Design Define 7 (PCGH edition)
  • Misc.: Logitech G915, Evoluent Vertical Mouse, shuttlePROv2

 

 

relaxvideo wrote on 8/29/2023, 9:44 AM

I often have this grey screen while start timeline playback with ONLY a normal size picture event!

So by me it's not because video decoding, however i have much less crashes when editing canopus hqx avi-s, than h264 mp4s.

#1 Ryzen 5-1600, 16GB DDR4, Nvidia 1660 Super, M2-SSD, Acer freesync monitor

#2 i7-2600, 32GB, Nvidia 1660Ti, SSD for system, M2-SSD for work, 2x4TB hdd, LG 3D monitor +3DTV +3D projectors

Win10 x64, Vegas22 latest

vagnerdesouza wrote on 9/3/2023, 6:10 PM

Can you share the media info? That's the biggest variable (now than when you started editing with 20?

I use only files of my camera Sony a6300. MP4 files, codec XAVC-S, 50000mbps, 1920x1080 59,94fps.

RogerS wrote on 9/3/2023, 8:58 PM

Hmm, those files are well known and work fine in VEGAS. They are also not data-heavy and shouldn't have issues- I use RX100, a6500 and a6600 X-AVC S files directly from mechanical HDDs.

I can't really say what is the issue then. Perhaps back up your preferences for 21 and try a reset and see if it's any better.

I have 20 and 21 both working here and the only interaction I see is with Hub- log in via 20 and 21 stays logged in it seems. The preferences and other working files are stored in different folders (annoyingly! Had to set up 21 again to mirror how I had 20).