Vegas 23 Build 356 Critical Issues

Thomas97 wrote on 12/17/2025, 7:42 PM

Hello Everyone.

Here's a list of bugs I've found with the latest build. Some of these are program-breaking, stopping key features I use. However, I am happy to see the color grading issue finally fixed.

1. SCRIPTING - Batch Render not working

2. Opening a file from Vegas 20 to Vegas 23 will cause the following problems:
A) Children Tracks will auto-collapse (make themselves small) every time they get out of view (hidden by menus or such).
B) The cursor in the timeline is not moving at all when pressing play.

3. I had several issues saving templates for "Video Properties". Apparently, modifying for example X and Y values and then saving a preset without applying first, will cause some problems when re-selecting that saved template. Sometimes saved templates have a name of other saved templates, changing every now and then when opening and closing the Video Properties menu, as if template values were mixing with custom template names saved.

This specific point needs more testing, also from other users. I'll provide a video when it happens again.

Comments

john_dennis wrote on 12/17/2025, 8:06 PM

1 Batch render script dead after upgrade

whoners wrote on 12/17/2025, 9:59 PM

After the update today, when I hit space, my timeline don't play, the video plays but the line don't. Really hard to edit like this. Is there a way to roll back to a prior version? Vegas Pro 23

RogerS wrote on 12/17/2025, 10:10 PM

@whoners Yes you can roll back. Uninstall from the control panel/ add remove programs and then reinstall an older build of your choice (302?) https://www.vegascreativesoftware.info/us/forum/faq-where-can-i-download-vegas-pro-and-other-vegas-software--104782/

whoners wrote on 12/17/2025, 10:18 PM

@whoners Yes you can roll back. Uninstall from the control panel/ add remove programs and then reinstall an older build of your choice (302?) https://www.vegascreativesoftware.info/us/forum/faq-where-can-i-download-vegas-pro-and-other-vegas-software--104782/

@RogerS Thanks so much! It's super annoying to try to edit with it not moving! Thanks again!

whoners wrote on 12/17/2025, 11:24 PM

I redownloaded the program and the scrubbing line still isn't moving when I play the video? Is there an option I might have hit to turn it off or stop it?

RogerS wrote on 12/17/2025, 11:45 PM

You installed 302? Please doublecheck the version.

Thomas97 wrote on 12/18/2025, 5:07 AM

1 Batch render script dead after upgrade

Thank you! Take this 🏅

Please let me know @whoners if rolling back works.

Also @RogerS, I noticed that hitting render, then cancel, then render again, will make the program to crash. Maybe it's only me?

whoners wrote on 12/18/2025, 5:28 AM

Ok @RogerS , @Thomas97 I rolled back to when I upgraded, so I used the store page download, the problem was the project was on 1440 and not 1080, not sure why that stopped it but once I went to my 1080 template, it worked again, then I went back over to the 1440 project and it wouldn't move when I played it. I don't use 1440 so I mean, it's fixed. Not sure if it's the project or the footage, but yeah I rolled back, and went to my main template (1080) and it worked. Thanks again for the help.

RogerS wrote on 12/18/2025, 8:03 AM

1 Batch render script dead after upgrade

Thank you! Take this 🏅

Please let me know @whoners if rolling back works.

Also @RogerS, I noticed that hitting render, then cancel, then render again, will make the program to crash. Maybe it's only me?

@Thomas97 I just took a clip, rendered part of it, cancelled, rendered again, cancelled, rendered again and no crash. It was AVC media rendered to MagixAVC with NVENC on my laptop. Is there something else I should try?

Steve_Rhoden wrote on 12/18/2025, 2:08 PM

I would suggest to you all who are having major issues to roll back to the previous version for now.

Thomas97 wrote on 12/18/2025, 3:02 PM

I would like to add that rendering a project where a clip is duplicated and playing twice in the video, is now suuuuper slow.

I used a h264 video from Twitch, a portion of the clip is the cam zoomed, and one is the gameplay.

@RogerS I'll try again, and I'll update you if I find more info.

@whoners I had that issue working with 1080p projects. So it's not related to resolution, I suppose.

I have a prepared empty template, and if I open it, it works fine. The moment I start working on it, adding clips and such, at some point, will cause the cursor to not work properly anymore. I need to test more...

thesammy58 wrote on 12/18/2025, 3:21 PM

It seems the discussion thread for the new build, as well as the announcement for it, has been deleted.

RogerS wrote on 12/18/2025, 4:43 PM

Oh that's good. I'm going back to 302.

paul-marshall wrote on 12/18/2025, 5:24 PM

Is it necessary to roll back the updated VEGAS_Pro_23_DLM_Smart_Mask_2_23.1.0.2 as well as going back to 302?

Steve_Rhoden wrote on 12/18/2025, 6:04 PM

Yes, the discussion thread for the new build, as well as the announcements has been removed.... And as advised above, try rolling back to build 302 lncluding the DLM versions.

RogerS wrote on 12/18/2025, 6:26 PM

I think old VEGAS would likely work with the new Smart Mask DLM. I'd test it before reverting.

Rahul-Harit wrote on 2/5/2026, 1:45 PM

Problems with Vegas Pro 23 build 356 :-

1. Cursor doesn't move whereas video moves.

2. Major Playback lag even in Preview Auto mode.

3. Late response in commands like Space Bar or Enter.

4. Sometimes unstable even though all updates including Nvidia graphic cards are correct.

What has been done in build 356? It's very unstable and headache while editing. How come suddenly it has become slow?

Earlier nothing like this happened.

3POINT wrote on 2/5/2026, 1:50 PM

@Rahul-Harit you probably missed that build 356 was withdrawn 3 days after it's release, due to the bugs you described. Better reinstall build 302 or wait till next build is released.

Rahul-Harit wrote on 2/5/2026, 1:55 PM

3point: yes I think I missed that info. I ll roll back to 302 build and hope it will get fine. Thank you for your reply.

3POINT wrote on 2/5/2026, 1:58 PM

@Rahul-Harit build 302 has also some issues but you can at least work/edit with it.

Rahul-Harit wrote on 2/5/2026, 2:06 PM

@3POINT ok. What about the Pro Res render issues? Have tried many settings, but taking out Pro Res 422 hq or normal, the colors change and sometimes overexposed. What could be the reason?

3POINT wrote on 2/5/2026, 3:15 PM

@3POINT ok. What about the Pro Res render issues? Have tried many settings, but taking out Pro Res 422 hq or normal, the colors change and sometimes overexposed. What could be the reason?

That's one of the known issues with build 302, but I'm not sure that the ProRes issue was already solved in build 356...

I hardly use Prores, so I don't have an issue and experience with it.

RogerS wrote on 2/5/2026, 5:31 PM

ProRes render issues were listed as a known issue with 356.

KNOWN ISSUES:

ProRes may not render with the correct color space

RedRob-CandlelightProdctns wrote on 2/5/2026, 11:06 PM

2. Opening a file from Vegas 20 to Vegas 23 will cause the following problems:
A) Children Tracks will auto-collapse (make themselves small) every time they get out of view (hidden by menus or such).
B) The cursor in the timeline is not moving at all when pressing play.

Not just a 20 to 23 issue.

I'm working on a newly created 23 project and have been noticing the auto-collapsing track problem -- SUPER annoying and I thought I was losing my mind at first. (well, Ok.. no comment on my mind ;-) )

Also started seeing delayed or not responsiveness with enter key for playback today.

I thought the problems were related to my video driver but now I'm thinking it's just Vegas. I've been seeing "jank" between my windows, and tool-tips not working. Is this all related to Vegas or should I be exploring different video drivers for my new 5070ti? (I'm using the one @RogerS has been using)

UPDATE: I just rolled back to 302 and I'm still seeing those weird intra-window janks, so I guess maybe my problems are a combo of build 356 and video driver :-( or something totally else?!