I've got a bug. Sometimes I can't add an FX Event, I have to add another FX, delete it and add the FX needed.
Please watch here: 
@Risi: The old Device Explorer is still available and needs to be enabled in the preferences > Deprecated Features.
Regarding VEGAS Capture - make sure that no other apps are using and blocking the capture devices. Close the browser etc. and try again.
@McRyanGold read this POST if you want help. Answer "B" and "C". Maybe you can not see the reason for adding your hardware, but if I were seeking help, and someone asked me a question seeking information to help, I'd answer.
And since you are the only one who as reported these issues, as much information is needed as possible. Create a new post so that any possible answer/solution won't get lost in this "general" discussion.
@Chris021 is this the French version? Is is possible to reinstall Vegas with the English language? I'm using the English language version and am able to add any FX without issues.
I have found the issue. I had Vegas 19 previsously, now with Vegas 23 it needs to make a double click on the FX event name before clicking OK. On V19 a simple click was enough.
Hi,
wie kann ich dem V23 installation-Programm sagen wo ich das Programm installiert haben möchte. Vegas will bei mir einfach C:\ benutzen, das LW ist ziemlich voll und Vegas soll auch garnicht dort hin.(?)
Danke für jede Antwort.
And then the bad one, really bad one: The way render functionality windows opens has been changed so that we can not minize Vegas when rendering? Usually minimizing it while also asking it not to show images along the way takes GPU- use from 50 percent to 90 percent on this box.
@digilyd That's an easy one. The way to minimize a Windows app with an open Modal Window is to click on the far right side of the Windows Task Bar where there is a vertical white line which is actually a Show Desktop button.
I wish you had tested this, but thanks for teaching me this, I didn't know that possibility. Logically it should not make Vegas stop drawing the screen, only stop showing it. So I tested and the result was at at glance an increase from 30 percent GPU use to 50 percent GPU use, I: got nowhere near the 90 percent GPU use of V22 with its window minimized. So patch this issue, instantly now, and change back to, the old way of opening render interface windows, please! - it is a dealbreaker that makes what looks like a very promising update with many things, I have been yearning for - when do we get the "lock in time" to prevent clips from accidentally moving in time when otherwise manipulated? - and that I really want to benefit from! - was no beta testing done, why does it take a humble user detecting this grave error after release?
Hi,
wie kann ich dem V23 installation-Programm sagen wo ich das Programm installiert haben möchte. Vegas will bei mir einfach C:\ benutzen, das LW ist ziemlich voll und Vegas soll auch garnicht dort hin.(?)
Danke für jede Antwort.
Mit viele programmen geht es gut aber mit Vegas sollte Du "system-rein" installieren, es ist möglich die %my programs% variable - kontrollieren das es die korrekte wörter sei - ändern und dadurch alle programinstallationen auf anderen platz machen, ABER Du will ja sicher das alle version-updates problemlös laufen, bitte hier windows reinheitsgebot folgen. Du sollte lieber daten relokieren, my documents, my images, spiele, my games, vegas prerender (!) etc.
Empfehlung: englisch schreiben damit das du besser verstanden wird.
Just tried the v23 trial, and there are two things that bug me...
I don’t know if it’s a feature or a bug, but when I try to select the pixel format "Legacy 8-bit (video levels)," it’s not working — it shows me 8-bit full range instead.
The videos are way too contrasted, and the shadows are blown out dark.
Highlights are gone too...
In the images I attached, you can see how v23 displays my videos compared to v21, where video levels are correct.
Oh — and it fucking crashes when I cancel rendering.
@BogdanRSC This is likely an unintended consequence of a new extended color space conversion feature. Hold shift and go to the options menu to access internal preferences and then search for this term and change true to false. Then 8 bit video will stop adjusting levels.
Render cancel crash is also on the list to fix.
@BogdanRSC This is likely an unintended consequence of a new extended color space conversion feature. Hold shift and go to the options menu to access internal preferences and then search for this term and change true to false. Then 8 bit video will stop adjusting levels.
OMFG!!!!
you're a life savior
Thank You a million times!
I noticed 2 massive problems... I have Vegas Pro 21, 22 and now 23 as of 09/15/2025.
1: The external monitor feature keeps flashing when in use...
I currently have 21, 22 and now 23. Both 21 and 22 are functioning as it should after some fiddling around with the settings. But with 23... the previous fix isn't even an option.
As far as I know, everything is up to date, my cords are all fine and the feature works in the previous two versions.
Previous Fix (for those with the previous versions) who would like to know...
- Open Vegas 22 or below
- Hold shift and go to Options
- Click Internal
- Lookup "Enable OpenCL/GL Interop" using the search (Not found in 23)
- Change it from "True" to "False"
- Click apply, restart Vegas, and from there... it should hopefully work for you.
Note: I had previously hoped that maybe once I bought it instead of just using the trial version of 23... maybe I could apply the same fix. But nope. $199.99 CAD down the drain more or less. I'll likely continue using 22 until a fix can be found.
2: The on going problem of every time a video is rendered it gets darker... (Seems to have gotten a bit better with 23), But still a thing...
I have never been able to figure this out. Using this program for animation, I need it to be consistent. If I need to go back and edit a scene, like add more or take away from it, the new edits are going to be like a few shades lighter then thee old.
My current solution is just do it right the first time. But production is always changing... and things are left for days, weeks, months and or even years.
Extra Note: I have tried reaching out to the official support team a few days ago... but no response. So even they probably don't know.
And Extra Side Note: A special thanks to a RogerS reaching out and trying to help.
If official support doesn't know they will contact engineering so it's not over- I expect it will be fixed with your help diagnosing the issue.
@Risi: The old Device Explorer is still available and needs to be enabled in the preferences > Deprecated Features.
Regarding VEGAS Capture - make sure that no other apps are using and blocking the capture devices. Close the browser etc. and try again.
And in the new version this option are not available as default? Does it mean that if I upgrade in sometime this explorer would disappear and I won't be able to import my MTS AVCHD files?
Do you need that for MTS AVCHD? I just copy and paste them directly (maybe I used a different type of camera than you?)
So the first bugs start to appear:
V23 doesn't save some preferences, like double click goes to trimmer, sometimes the preview device etc.
It also doesn't seem to save some changes. There are 2 events it keeps asking me for as "missing" on open, although I repeatedly dletet them from the project.
And the search bar for video FX has disappeared.
Oh and I mentioned the render crashes in a separate post.
Do you need that for MTS AVCHD? I just copy and paste them directly (maybe I used a different type of camera than you?)
You can paste also direct the mts files, but when the video recorded is longer than 4gb the camera creates several files. For example, I record an audition of my students maybe 1 hour long. I have 3 diferent mts i.e MTS0001, MTS0002 AND MTS0003. If you copy directly the first one plays without problemas, but the other ones has sound sync issues. If you try to manually sync, what is a pain, you lose some frames and you see the jumps in the image. So for this files, camera generates also a structure files list, so with the proper program, such the deprecated function, the whole video si represented as one, not as three. And the best thing its when you import them, vegas 22 copies them as only one all three merged and in perfect sync. For me this is amazing. Really time saver. I hope I explained myself correctly.
PD. I attached some images. In the first you see if you open de sd card directly. You see that for one recording, my camera created 3 files. As you in second, with the importer in vegas, it reads the structure file info and it detects as a full long recording. And when you import, as you see in last image, i get only one mts merged and in sync.
Thank you.
I'd like to report a pretty program-breaking bug I've encountered in my color grading workflow.
When copying effects from one clip to another, specifically color grading, the color grading panel completely breaks making it so you cannot change the LUT or use the color wheels until resetting all color grading settings. This means instead of copying settings from one clip to another and making fine-tuned adjustments, you have to go through the entire color grading process from the beginning on each new clip.
I can not log into Vegas Hub with Vegas 23. I changed my password and it still does not allow me to login. How can I fix this? Thank you.
@jacknsb The few times in the past when I experienced the problem I found that as a workaround, I could go back to the fx chain of the clip I wanted to copy cgp settings from, and save cgp as a preset. Then go to the fx chain of another clip and select the saved preset.
Lately I haven't been putting cgp in the camera clip events at all... been putting them in adjustment events instead. Then all I need to do is copy the adjustment event or stretch it to cover multiple camera events. It's really sped up my multicam grading.
I'm trialing VP23 (build 278) and found that its render speed is only about 40% that of VP22, when using the same project, with the same render settings. For example, with a 1920x1080, 25fps project, VP22 renders at 124fps average, whereas VP23 only manages an average of 54fps. This is on the same project, which does not contain keyframe animated stills, which I understand is a known issue. I suspect that VP23 does not work well with my Intel GPU, which is an ARC A750. Like all Intel GPUs, it has built-in hardware codecs for rendering video.