VP23 is an embarrassment

anthony-chiappette wrote on 10/18/2025, 9:46 PM

I've been using Vegas for a lot of years. I never recall having any problems when the product belonged to Sony. But over the years, Magix Vegas seemed to get a little better. However, VP23 is the complete opposite.

I can edit a video for 5 hours without a hiccup. Then suddenly, it will just freeze up, and I will keep having problems. Rendering? Either I can or I can't. I can try to render my project 3 times, Vegas will crash at different portions of the render process. I can try again, and BOOM, it will fully render. I can't imagine anyone using this software in a professional broadcasting capacity would be happy with it.

I know it's new, but I can't imagine, if anyone tested this, that it passed without any issues. This software was not ready for release and should have been held back until it was ready. What good is a faster rendering engine if you can't actually render?

Sorry if I'm stepping on any toes here, but I have just had enough with 23.

ASUS Prime Z590-A Motherboard with Intel Core i7 11700 8 Core / 16 Thread 2.50GHZ, 64GB Crucial DDR4 3200 (4 x 16GB), nVidia GeForce RTX5060 8GB GDDR7, SoundBlaster X AE5 soundcard, 3 x 4TB Samsung 860 EVO SATA 3 SSD, 2 x 8TB Samsung 870 QVO SATA 3 SSD, 1 x 2TB Samsung 980 Pro NVME PICE4 SSD, 2 X WD 4 TB NVME PCIE3 SSD, 2 X Viewsonic HD monitors, LG Blu-Ray writer. Windows 11 (latest build), currently using Vegas Pro 22 latest build, and limited VP23 use to gauge performance and ease of use differences. Videos come from 2 x Sony HDR CX-405 Cameras, XAVC-S MP4 @ 50Mbps 1080P 60fps video files. (Previously: 2 x Canon HFR800 cameras, MP4 files at 1920 x 1080 60p 35Mbps).

Comments

RogerS wrote on 10/18/2025, 10:28 PM

Can you provide any information about your system, media or Fx in use? There's some combination causing you issues and it needs to be addressed but it's a mistake to think this is a universal problem; overall VEGAS is getting more stable. I assume you are on the current build, 302.

anthony-chiappette wrote on 10/18/2025, 11:44 PM

Hi. Yes, I am using ver 302. I don't have these issues with VP22, at least when it comes to rendering. My system details are in my signature, as well as the types of files I am using. I am not doing anything extraordinary within Vegas, but I do use a lot of text and animated text events.

The details for the files I am using are as follows (from MediaInfo):

General
Complete name                            : F:\Sony HDR-CX405\2025-10-17\2025-10-17 Barbie Pinball CAM A.MP4
Format                                   : XAVC
Codec ID                                 : XAVC (XAVC/mp42/iso2)
File size                                : 15.7 GiB
Duration                                 : 43 min 12 s
Overall bit rate mode                    : Variable
Overall bit rate                         : 52.0 Mb/s
Frame rate                               : 59.940 FPS
Encoded date                             : 2025-10-17 17:04:50 UTC
Tagged date                              : 2025-10-17 17:04:50 UTC

Video
ID                                       : 1
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : High@L4.2
Format settings                          : CABAC / 2 Ref Frames
Format settings, CABAC                   : Yes
Format settings, Reference frames        : 2 frames
Format settings, GOP                     : M=1, N=30
Format settings, Slice count             : 4 slices per frame
Codec ID                                 : avc1
Codec ID/Info                            : Advanced Video Coding
Duration                                 : 43 min 12 s
Bit rate mode                            : Variable
Bit rate                                 : 49.9 Mb/s
Maximum bit rate                         : 60.0 Mb/s
Width                                    : 1 920 pixels
Height                                   : 1 080 pixels
Display aspect ratio                     : 16:9
Frame rate mode                          : Constant
Frame rate                               : 59.940 (60000/1001) FPS
Standard                                 : NTSC
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Progressive
Bits/(Pixel*Frame)                       : 0.402
Stream size                              : 15.1 GiB (96%)
Writing library                          : AVC Coding
Encoded date                             : 2025-10-17 17:04:50 UTC
Tagged date                              : 2025-10-17 17:04:50 UTC
Color range                              : Limited
Color primaries                          : BT.709
Transfer characteristics                 : xvYCC
Matrix coefficients                      : BT.709
Metas                                    : 3
Codec configuration box                  : avcC

Audio
ID                                       : 2
Format                                   : PCM
Format settings                          : Big / Signed
Codec ID                                 : twos
Duration                                 : 43 min 12 s
Bit rate mode                            : Constant
Bit rate                                 : 1 536 kb/s
Channel(s)                               : 2 channels
Sampling rate                            : 48.0 kHz
Bit depth                                : 16 bits
Stream size                              : 475 MiB (3%)
Encoded date                             : 2025-10-17 17:04:50 UTC
Tagged date                              : 2025-10-17 17:04:50 UTC

Other
ID                                       : 3
Type                                     : meta
Format                                   : Sony Real Time Metadata
Codec ID                                 : rtmd
Duration                                 : 43 min 12 s
Bit rate mode                            : Constant
Time code of first frame                 : 83:01:01;02
Stream size                              : 152 MiB (1%)
Encoded date                             : 2025-10-17 17:04:50 UTC
Tagged date                              : 2025-10-17 17:04:50 UTC
AutoExposureMode_FirstFrame              : Full Auto
AutoFocusSensingAreaSetting_FirstFrame   : Center Sensitive Auto
ShutterSpeed_Time_FirstFrame             : 1/60 s
CameraMasterGainAdjustment_FirstFrame    : 9.00 dB
ElectricalExtenderMagnification_FirstFra : 100%
AutoWhiteBalanceMode_FirstFrame          : Automatic

 

Typical timeline screenshot (From VP22 as I cannot complete this project in VP23)

 

ASUS Prime Z590-A Motherboard with Intel Core i7 11700 8 Core / 16 Thread 2.50GHZ, 64GB Crucial DDR4 3200 (4 x 16GB), nVidia GeForce RTX5060 8GB GDDR7, SoundBlaster X AE5 soundcard, 3 x 4TB Samsung 860 EVO SATA 3 SSD, 2 x 8TB Samsung 870 QVO SATA 3 SSD, 1 x 2TB Samsung 980 Pro NVME PICE4 SSD, 2 X WD 4 TB NVME PCIE3 SSD, 2 X Viewsonic HD monitors, LG Blu-Ray writer. Windows 11 (latest build), currently using Vegas Pro 22 latest build, and limited VP23 use to gauge performance and ease of use differences. Videos come from 2 x Sony HDR CX-405 Cameras, XAVC-S MP4 @ 50Mbps 1080P 60fps video files. (Previously: 2 x Canon HFR800 cameras, MP4 files at 1920 x 1080 60p 35Mbps).

anthony-chiappette wrote on 10/19/2025, 2:07 AM

It seems every time it crashes and I get the report error dialog, this is the culprit:

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 23.0 (Build 278)
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispsi.inf_amd64_9cefe84c51ec4d1b\nvopencl64.dll
   Fault Address:       0x00007FFB2EEF9E60
   Fault Offset:        0x0000000000149E60
 

 

I guess that indicates a problem with the video card? (RTX 5060 8 GB - latest studio driver)

ASUS Prime Z590-A Motherboard with Intel Core i7 11700 8 Core / 16 Thread 2.50GHZ, 64GB Crucial DDR4 3200 (4 x 16GB), nVidia GeForce RTX5060 8GB GDDR7, SoundBlaster X AE5 soundcard, 3 x 4TB Samsung 860 EVO SATA 3 SSD, 2 x 8TB Samsung 870 QVO SATA 3 SSD, 1 x 2TB Samsung 980 Pro NVME PICE4 SSD, 2 X WD 4 TB NVME PCIE3 SSD, 2 X Viewsonic HD monitors, LG Blu-Ray writer. Windows 11 (latest build), currently using Vegas Pro 22 latest build, and limited VP23 use to gauge performance and ease of use differences. Videos come from 2 x Sony HDR CX-405 Cameras, XAVC-S MP4 @ 50Mbps 1080P 60fps video files. (Previously: 2 x Canon HFR800 cameras, MP4 files at 1920 x 1080 60p 35Mbps).

fifonik wrote on 10/19/2025, 2:08 AM

As you mentioned old Sony Vegas, you may try to turn off HW decoder (the old Sony Vegas did not have it). You should be fine with your FullHD footage (well, I'm not sure as your timeline looks much more complicated than mine).

At least check if you have the same settings related to HW in VP23 as in VP22 ('File I/O' & 'Video' tabs)

From my personal experience HW decoder is "the thing" that causing issues. I do not have issues with it while editing 1080-60p, but with 4K-60p VP22 is crashing quite often when HW decoder is ON (not using VP23 yet).

Camcorder: Panasonic X1500 + Panasonic X920 + GoPro Hero 11 Black

Desktop: MB: MSI B650P, CPU: AMD Ryzen 9700X, RAM: G'Skill 64 GB DDR5@6000, Graphics card: MSI RX6600 8GB, SSD: Samsung 970 Evo+ 1TB (NVMe, OS), HDD WD 4TB, HDD Toshiba 4TB, OS: Windows 10 Pro 22H2

NLE: Vegas Pro [Edit] 11, 12, 13, 15, 17, 18, 19, 22

Author of FFMetrics and FFBitrateViewer