VEGAS Pro 23 build 302 General Discussion

Comments

RogerS wrote on 12/2/2025, 8:16 PM

@Sadlylate Alpha channel formats still work in VEGAS. Quicktime decoding edit: still functions, and other formats are migrated to the native decoders such as Apple ProRes.

Last changed by RogerS on 12/5/2025, 4:32 PM, changed a total of 1 times.

Custom PC (2022) Intel i5-13600K with UHD 770 iGPU with latest driver, MSI z690 Tomahawk motherboard, 64GB Corsair DDR5 5200 ram, NVIDIA 5070 (12GB) with latest studio driver, 2TB Hynix P41 SSD and 2TB Samsung 980 Pro cache drive, Windows 11 Pro 64 bit https://pcpartpicker.com/b/rZ9NnQ

ASUS Zenbook Pro 14 Intel i9-13900H with Intel graphics iGPU with latest ASUS driver, NVIDIA 4060 (8GB) with latest studio driver, 48GB system ram, Windows 11 Home, 1TB Samsung SSD.

VEGAS Pro 21.208
VEGAS Pro 22.250
VEGAS Pro 23.302

Try the
VEGAS 4K "sample project" benchmark (works with VP 16+): https://forms.gle/ypyrrbUghEiaf2aC7
VEGAS Pro 20 "Ad" benchmark (works with VP 20+): https://forms.gle/eErJTR87K2bbJc4Q7

thesammy58 wrote on 12/5/2025, 1:55 PM

@Sadlylate Alpha channel formats still work in VEGAS. Quicktime decoding functions and other formats are migrated to the native decoders like Apple ProRes.

This seems to contradict this comment made by a member of the VEGAS Pro team recently:

https://www.reddit.com/r/VegasPro/comments/1nblk51/comment/nd2ruf4/

The File I/O Surrogate was rewritten with the release of 23 and its only existence is to handle Quicktime decoding. If Apple ProRes now handles the decoding natively then I'm wondering what the actual purpose of the I/O Surrogate is for or maybe I'm misunderstanding something somewhere

RogerS wrote on 12/5/2025, 4:30 PM

Yes, I think my comment was imprecise. ProRes is decoded natively as are more snd more formats. QuickTime still does DNxHR and a few others that have yet to be migrated.

Last changed by RogerS on 12/5/2025, 4:30 PM, changed a total of 1 times.

Custom PC (2022) Intel i5-13600K with UHD 770 iGPU with latest driver, MSI z690 Tomahawk motherboard, 64GB Corsair DDR5 5200 ram, NVIDIA 5070 (12GB) with latest studio driver, 2TB Hynix P41 SSD and 2TB Samsung 980 Pro cache drive, Windows 11 Pro 64 bit https://pcpartpicker.com/b/rZ9NnQ

ASUS Zenbook Pro 14 Intel i9-13900H with Intel graphics iGPU with latest ASUS driver, NVIDIA 4060 (8GB) with latest studio driver, 48GB system ram, Windows 11 Home, 1TB Samsung SSD.

VEGAS Pro 21.208
VEGAS Pro 22.250
VEGAS Pro 23.302

Try the
VEGAS 4K "sample project" benchmark (works with VP 16+): https://forms.gle/ypyrrbUghEiaf2aC7
VEGAS Pro 20 "Ad" benchmark (works with VP 20+): https://forms.gle/eErJTR87K2bbJc4Q7

Howard-Vigorita wrote on 12/6/2025, 11:48 AM

@Sadlylate Alpha channel formats still work in VEGAS. Quicktime decoding functions and other formats are migrated to the native decoders like Apple ProRes.

This seems to contradict this comment made by a member of the VEGAS Pro team recently:

https://www.reddit.com/r/VegasPro/comments/1nblk51/comment/nd2ruf4/

The File I/O Surrogate was rewritten with the release of 23 and its only existence is to handle Quicktime decoding. If Apple ProRes now handles the decoding natively then I'm wondering what the actual purpose of the I/O Surrogate is for or maybe I'm misunderstanding something somewhere

@thesammy58 Just to be clear, the developer's statement about the File I/O Surrogate is, "It is still needed if you enable the QuickTime decoder." I understand that to mean that if you don't install QuickTime decoding drivers and enable them in Deprecated Preferences, the File I/O Surrogate could be completely removed from Vegas. But my experience is as @RogerS mentioned... Vegas cannot process DNxHD without both QuickTime & Avid drivers installed and QuickTime decoding enabled.

Lamyss wrote on 12/7/2025, 8:55 PM

Hello, I took advantage of a promotion to buy Vegas Pro 23 on the official website https://shop.vegascreativesoftware.com/ I knew that the French version was not working, so I installed it in English version, but after the installation, the software systematically gets stuck! 😦

Hoping to have a solution / Thank you for your help, beautiful day

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 23.0 (Build 302)
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\WINDOWS\SYSTEM32\ntdll.dll
   Fault Address:       0x00007FFCF315C1FE
   Fault Offset:        0x000000000001C1FE

Fault Process Details
   Process Path:        C:\Program Files\VEGAS\VEGAS Pro 23.0\vegas230.exe
   Process Version:     Version 23.0 (Build 302)
   Process Description: VEGAS Pro
   Process Image Date:  2025-09-27 (Sat Sep 27) 00:42:20

 

RogerS wrote on 12/7/2025, 9:19 PM

@Lamyss Is it an issue with Visual Studio? https://www.vegascreativesoftware.info/us/forum/warning-ms-vc-14-50-v145-kill-vegas-permanently--150332/