VEGAS Pro 23 build 302 General Discussion

Comments

ChrisD wrote on 11/25/2025, 12:30 AM

Indeed, both are just editing tools and I like to use both.

Agreed. No argument there.

I think the free version had/has limitations with 10-bit HVEC H.265. I shoot mostly Sony S-Log or DJI D-Log M and editing and rendering became an issue. I rarely use AI, other than the odd subtitle; not sure if DR's Magic Mask counts.

Right tool. Right job. Davinci's tracking (yes, I miss Mocha Vegas), compositing, lightning fast rendering, and to a degree, colour grading are light years ahead. For now.

My problem is that my keyboard muscle-memory leans towards Vegas. I do what I need in DR, e.g. tracked callouts, some titles, etc., and then round trip back to Vegas for arrangement, cuts, and sound design -- usually via Cineform (I'll get my coat) or ProRes.

 

 

3POINT wrote on 11/25/2025, 12:59 AM

@ChrisD I shoot 10-bit HEVC (DJI Osmo Pocket 3) and that is no issue to edit/render with DR free. Rendering with DR free is almost twice as fast as VP23, even (much) more when effects, Titling, optical flow resampling, stabilisation etc are used. Some keyboard shortcuts (especially for splitting and trimming) I use in Vegas, I customized in DR. Most I like the ability to have more timelines in a project instead of Vegas nesting.

jkerry wrote on 11/25/2025, 8:00 AM

Just installed Vegas 23 upgrade. But can not find how to move the timeline to the top of the main window.

Any assistance would be helpful.

Jeff

eleven wrote on 11/25/2025, 9:03 AM

@jkerry In Vegas Pro 22, there was an option to move the timeline to the top of the main window, but in VEGAS Pro 23, it seems that option has been removed.
It’s possible that this change is related to the more flexible docking layout in VEGAS Pro 23, which may have led to the removal of the ability to move the timeline itself.

OS: Windows 11 Pro 24H2(26100.7462)

CPU: AMD Ryzen 9 3900X 12-Core Processor

RAM: 32.0 GB

Graphics card: NVIDIA GeForce RTX 3060 Ti

C-drive: NVMe M.2 SSD 1TB(Seagate FireCuda 530)

MOBO: ASUS TUF GAMING B550-PLUS

RogerS wrote on 11/25/2025, 9:48 AM

Isn't there a view/layout setting for this?

3POINT wrote on 11/25/2025, 10:44 AM

Just installed Vegas 23 upgrade. But can not find how to move the timeline to the top of the main window.

Any assistance would be helpful.


Dexcon wrote on 11/25/2025, 4:54 PM

@3POINT  ... The timeline placement issue in VP23 is covered in the following forum thread:

https://www.vegascreativesoftware.info/us/forum/no-option-to-put-timeline-display-at-top-in-vegas-23--149585/#ca941406

The relevant quotes from this thread are:

VEGASDerek wrote on 9/10/2025, 2:54 AM

That option was removed because you can now dock any window below the timeline. New docking areas are available below, to the left and to the right of the timeline. Currently we do not have a layout which has all the default windows at the bottom, but you can manually move all the windows and then save that layout.

... and:

VEGASDerek wrote on 9/15/2025, 1:46 AM

We will look into creating a new pre-installed layout that has the timeline on top and the default docked windows in the bottom docking area. This will make life a little easier for those who previously used that timeline location preference.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition; Samsung S23 Ultra smart phone

Installed: Vegas Pro 13, 15, 16, 17, 18, 19, 20, 21, 22 & 23, HitFilm Pro 2021.3, DaVinci Resolve Studio 20.3, BCC 2026, Mocha Pro 2026, NBFX TotalFX 7, Neat NR 6, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 12, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11 25H2

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

3POINT wrote on 11/26/2025, 12:51 AM

@Dexcon I'm not sure what you're trying to tell me. The thread you're referring to was released before Magix added the pre installed layout in a later update, which I showed @jkerry.

Dexcon wrote on 11/26/2025, 1:06 AM

@ChrisD ... Sorry, I hadn't realised that the top display layout had been updated in build 302.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition; Samsung S23 Ultra smart phone

Installed: Vegas Pro 13, 15, 16, 17, 18, 19, 20, 21, 22 & 23, HitFilm Pro 2021.3, DaVinci Resolve Studio 20.3, BCC 2026, Mocha Pro 2026, NBFX TotalFX 7, Neat NR 6, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 12, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11 25H2

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

ChrisD wrote on 11/26/2025, 2:25 PM

@ChrisD ... Sorry, I hadn't realised that the top display layout had been updated in build 302.


@Dexcon ZZZZ. Wait. What? 😴

thesammy58 wrote on 11/26/2025, 6:26 PM

Has anyone figured out yet how to re-enable the Quicktime support for rendering? I have it enabled in the deprecated features list and have my render window set to show ALL formats but it is still missing.

 

My setup:

VEGAS Pro 23.0 (Build 302)

OS: Windows 10 x64 22H2

GPU: NVIDIA RTX 4070 SUPER (Studio Driver 591.44)

CPU: AMD Ryzen 9 5900X

Mobo: MSI MPG B550 Gaming Plus

Boris FX Continuum Complete 2026.0.0, NewblueFX Total FX360

EricLNZ wrote on 11/26/2025, 7:09 PM

@thesammy58 You have QT installed on your system?

Gary-Burlingame wrote on 11/27/2025, 1:33 AM

I can't find any mpeg 2 options in the "render as" menu in Version 23.0 build 302, so I am unable to create render files for burning DVD or Blu-ray discs in DVD Architect. Was mpeg 2 removed intentionally from the software or can it still be added to my "render as" options? For the past 10 days, Vegas tech support has been unresponsive to my emails other than to say that they'll "respond soon." Please help as I have clients waiting who've ordered DVDs and Blu-rays. Thanks.

andyrpsmith wrote on 11/27/2025, 2:54 AM

Here are plenty of Mpeg-2 options. Do you have the show all filter on?

Sadlylate wrote on 11/27/2025, 2:53 PM

Has anyone figured out yet how to re-enable the Quicktime support for rendering? I have it enabled in the deprecated features list and have my render window set to show ALL formats but it is still missing.

Quicktime does not seem to work in Vegas 23 as of yet. No word from the developers so far so we just have to be patient unfortunately...

DMc wrote on 11/28/2025, 1:30 PM

I worked with Vegas Pro 20 for years with no problems at all. All of the features worked well, and the performance on my PC (i7-9750H CPU @ 2.60GHz, 16GB RAM, NVIDIA GeForce RTX2060 6GB) was fast and smooth. After much thought and testing out the trial version of Pro 23, I made the upgrade. So far, it's been a disappointment. Video previews stutter, and rendering speed is significantly slower, even without using the AI video effects. When rendering with any of the AI effects, the speed drops to 4 to 5 fps no matter what I do to optimize the performance settings. If anyone has a way to improve the performance, I'm open to any suggestions. I've been a Vegas user since the Sony days; the Magix versions have been slow to improve, and getting slower.

Howard-Vigorita wrote on 11/29/2025, 1:58 PM

@DMc One of the changes in Vegas between vp20 and vp23 is that video processing is now optimized by keeping as much activity as possible within an Nvidia gpu. So if your setup from vp20 is implemented on vp23, with decoding by an Intel igpu while other video processing is done by Nvidia, performance will suffer. If you haven't already, try leaving the decoding settings in I/O prefs at the vp23 default which should match the decoder and ai to the device selected in Video Prefs. And consider disabling the igpu in bios, which is usually possible except on laptops. For optimal ai performance, however, you'd be better off with a more current Nvidia gpu with more vram and ai support lacking in a 2060.

MikeS wrote on 11/29/2025, 2:12 PM

Has anyone figured out yet how to re-enable the Quicktime support for rendering? I have it enabled in the deprecated features list and have my render window set to show ALL formats but it is still missing.

Quicktime does not seem to work in Vegas 23 as of yet. No word from the developers so far so we just have to be patient unfortunately...

https://www.vegascreativesoftware.info/us/forum/where-did-the-quicktime-rendering-option-go--150299/#ca945765

Vegas Pro Suite 22.0 Build 250
Boris FX Continuum for OFX 2025 Build 18.5.0.441 - 113
Boris FX Mocha Pro Plug-in 2025 v12.0.1 build 46
Windows 11 Pro - 64-Bit
ASUS PRIME Z390-P motherboard
Intel Core i7-97000K @ 3.6GHz
RAM 32GB (2x 16GB) 2666MHz DDR4
GeForce RTX 2070 SUPER

TAGyerit wrote on 12/1/2025, 5:12 PM

Longtime Vegas Pro user, currently using v20. I just installed v23 (Build 302) as a trial, opened up my first simple v20 project file and clicked play and the project crashed within seconds, likely due to a very simple nested .veg file that is a Lower Third name display I purchased from Vegasaur.

Crashes happen, but it's my understanding that build 302 is a BETA version which is the version I was forced to download as trial. If that's correct, forcing a Beta version as a trial version is a horrible idea, I can't justify "upgrading" now obviously. It's my understanding that build 278 is stable, but I don't have the time or interest to uninstall 302 then figure out how to download build 278 on the off chance it might not crash. (I may be incorrect about the 302 being Beta, but that's my understanding.)

Anyway, frustrating. I'm running NVIDIA RTX 4080 and I think v23 is supposed to take better advantage of it's power (?) but I don't really know the benefits to know why I should try harder to get v23 to work. Maybe v23 is NOT crash-prone and all I need to do is open the v20 .veg lower third file and re-save it as a v23 file, but again I don't know.

I'm not asking for specific help, just documenting the issue I had, and if anyone has advise or workarounds I'd certainly be interested, thanks.

Here's the error info given:

   File:                C:\Users\User\AppData\Local\VEGAS Pro\23.0\gpu_video_x64.log
   File:                C:\Users\User\AppData\Local\VEGAS Pro\23.0\fileio_x64.log
   File:                C:\Users\User\AppData\Local\VEGAS Pro\23.0\persist.prefs
   File:                C:\Users\User\AppData\Local\VEGAS Pro\23.0\fileio_x64.log
   File:                C:\Users\User\AppData\Local\VEGAS Pro\23.0\dx_video_grovel_x64.log
   File:                C:\Users\User\AppData\Local\VEGAS Pro\23.0\svfx_video_grovel_x64.log
   File:                C:\Users\User\AppData\Local\VEGAS Pro\23.0\ocio_x64.log
   File:                C:\Users\User\AppData\Local\VEGAS Pro\23.0\dx_grovel_x64.log
   File:                C:\Users\User\AppData\Local\VEGAS Pro\23.0\vst_grovel.log
   File:                C:\Users\User\AppData\Local\VEGAS Pro\23.0\vegas_script_x64.log
   File:                C:\Users\User\AppData\Local\VEGAS Pro\23.0\hub.log
   File:                D:Project\VideoProduction\2025_Sept-Dec\Welcome_1a.veg
   File:                D:Project\Vegasaur Titles4\Title_06_LowerThirdsTitle_Red_v20.veg

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 23.0 (Build 302)
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\Program Files\VEGAS\VEGAS Pro 23.0\sharedk.dll
   Fault Address:       0x00007FF83B877930
   Fault Offset:        0x00000000005A7930

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) 09:42:20

 

RogerS wrote on 12/1/2025, 7:28 PM

@TAGyerit 302 was a beta build but I believe at this point it is the standard release build for 23. It's basically 278 with bugfixes: https://www.vegascreativesoftware.info/us/forum/patch-vegas-pro-23-build-302--149832/

I have some Vegasaur templates (not sure if it is the same as yours) and would be willing to privately test your project and nests. I added the ones I had as nests in a VP 23 project and it didn't crash on my RTX 4060 mobile system.

TAGyerit wrote on 12/1/2025, 8:04 PM

OK thanks @RogerS, that makes sense regarding Build 302 originally being Beta and now being the standard release. And that's extremely useful info that you used Vegasaur Templates as nested .veg files and that it didn't crash your similar system, so that makes it sound like it's worth experimenting a little to see if there's an easy fix. Thanks again.

Sadlylate wrote on 12/2/2025, 1:44 PM

Has anyone figured out yet how to re-enable the Quicktime support for rendering? I have it enabled in the deprecated features list and have my render window set to show ALL formats but it is still missing.

Quicktime does not seem to work in Vegas 23 as of yet. No word from the developers so far so we just have to be patient unfortunately...

https://www.vegascreativesoftware.info/us/forum/where-did-the-quicktime-rendering-option-go--150299/#ca945765

That's very unfortunate; especially considering majority of alpha channeled video footage will no longer be supported. It's perhaps time for me to look beyond Vegas's limitations as we're now making the box even smaller. And with support dropping from almost all the 3rd parties, it's evident they're no longer confident in the future of the program either.

Thank you Magix for the many years of service, it has served me very well and it's going to be painful moving my workflow elsewhere

EricLNZ wrote on 12/2/2025, 4:03 PM

majority of alpha channeled video footage will no longer be supported

I was under the impression that only QT rendering had been dropped.

With VP23 is the decoding of mov QT files also affected when they require QT due to JPEG or PNG encoded video?

TAGyerit wrote on 12/2/2025, 5:30 PM

I have some Vegasaur templates (not sure if it is the same as yours) and would be willing to privately test your project and nests. I added the ones I had as nests in a VP 23 project and it didn't crash on my RTX 4060 mobile system.

My workaround for now was to takethe Vegasaur Titles lower-third that is crashing as a nested .veg and export it as a .png animation and bring back into the project that way, that was new to me but was pretty easy to do, so at least I can put it on the back burner for now. Thanks for your generous offer though.