Bugs After Latest Version: Color Grading again, Auto Collapse, more...

Thomas97 wrote on 1/20/2026, 4:55 AM

Hello Vegas Community,

I searched for similar reported bugs but couldn't find any.

I'll start with the "cursor not moving" bug, but we already have a thread.

Another bug I found is with the color grading.
I'm not sure if you remember, but in the previous version, operating with the color grading curves created color holes.

Now, I tried to modify a clip in both v20 and v23 using the Utility panel, and the results are too broken to be used.
As you can see from the videos below, Saturation, Contrast, and Brightness are just examples of how everything is modified to a point where everything is black or white.

Saturation --

Contrast and Brightness --

If this is based on settings, please let me know any suggestions. However, this issue also occurs when opening a v20 project in the v23 version.

Now, in these videos, I tried using a gameplay capture, but when using clips recorded with a camera (Sony, your phone, ...) it's much more noticeable, and you can even see the same color-holes appearing in the inspector.

Indeed, in one example, I had to color grade a tiny bit of a scene where there was also a black leather glove appearing in the scene. I noticed this bug when I imported the project into v23 (from v20) and noticed that where the black leather was more reflecting a light glow/bloom, the color was not smoothly transitioning in the glove, but it was dividing the color in lines, as if there was no smooth light progression.

There's something off again with color grading, and V23 cannot be used for any professional editing at the moment, which is disappointing.

========
Another bug I don't know how to easily repro, are tracks auto-collapsing.
It happens after some clips are added to a group. I noticed this happening after working for some time in the program, and when it probably is either longer than X amount of minutes, or when too many clips/cuts are used/done?

You can also see how trying to make tracks bigger makes everything glitchy. Maybe it's the name next to them? The previous version was not causing this issue, so something changed with the latest release.

========
Another bug I also replied to in the thread: new files not really sticking to the cursor or markers when imported.

This is a bug that also happened in v21 (or v22, I don't remember) and never got fixed for 1 year at least, reason why I asked for a refund.

========

My question is, if we cannot properly color grade, drag and drop files on a timeline, or even scroll normally on a timeline without breaking the view, when can we expect to be able to use a program we paid for?

It's been a while now, and with every release, they fix many bugs (yay), but they add new and critical ones, making v23 unusable, again.

Comments

RogerS wrote on 1/20/2026, 5:09 AM

Are you testing build 356 or 302? 356 was withdrawn due to issues with envelope handling/cursor not moving/minimized tracks. I wouldn't bother testing this with 356.

Download 302 from here: https://www.vegascreativesoftware.info/us/forum/faq-where-can-i-download-vegas-pro-and-other-vegas-software--104782/

For color grading the last I checked the holes issue was fixed. Will test again once a new build is released.

 

Thomas97 wrote on 1/20/2026, 5:21 AM

Hey Roger, thanks for replying so quickly.

Yes, all these issues happened during 356. Here's a video I just recorded.

Seems it happens after a while working with Vegas23, not sure what triggers this, similar to the auto-track-collapse issue.

I would like to download 302, but it has previous issues that would make the version not usable for me anyway. So yeah, after months, I still cannot use V23 entirely, and I always have to go back and forth to v20.

Thomas M.

1. Custom PC, 4090RTX, i9 13900K, 64Gb RAM 6000MT, Win 11.
2. Custom PC, 4070RTX, i7 12700KF, 64Gb RAM 6000MT, Win 11.
3. Alienware Area51-m2, 2080Super Mobile, i9 10900K Desktop, 32Gb RAM 3600MT, Win 11.

RogerS wrote on 1/20/2026, 6:28 AM

Fair enough, 23 started well but has deteriorated in some respects. Were builds before 302 not usable for you either?

If not I'd stay on 20 until the next build is released and then check back. The cursor issue is known and will be fixed.

Thomas97 wrote on 1/20/2026, 6:40 AM

I've been waiting for v23 for a long time, and after the interviews and discussions about many new things coming, I immediately purchased it.

The first versions had that color grading issue I always reported, which forced me to go back to v20. Answering your question, yes, I was never able to use any V23 release.

I use it now for gameplay edits or trailers where no color grading is needed, but for professional cinematography, I can't.

Backstory...

I remember using V11, then V14, then V17, and now V20, and all of them (regardless of some crash issues) worked without all these bugs I am finding now.

I thought... "ok, so now V23 has to work for me, since it's every 3 versions that I felt like Vegas was good." But maybe it was just a coincidence... 😭

There's still another 'bug' which I think cannot be fixed, which is regarding how slow v23 is to render anything that has transitions in it. I reported this in the mega-thread I created 2 releases ago, issue number 6.

V23 is really good, considering the almost no crashes I get. Super fast at rendering, but not with fade or alpha effects.

Also, I still wish color grading were in its old version, since those curves all in one square are really annoying to use.

Thomas M.

1. Custom PC, 4090RTX, i9 13900K, 64Gb RAM 6000MT, Win 11.
2. Custom PC, 4070RTX, i7 12700KF, 64Gb RAM 6000MT, Win 11.
3. Alienware Area51-m2, 2080Super Mobile, i9 10900K Desktop, 32Gb RAM 3600MT, Win 11.