Known issue only with ProRes4444 that should be fixed soon.

Well, to me looks like not only ProRes is affected but also decoding old simple x-avc and avc-aac h.264 as the source media is also affected - the entire color engine might be broken. There is no difference in color range if and when switching between 8-bit legacy, 8-bit full range, 32-bit etc. in project properties. Every option has contrast and color range like 8-bit full range. Win 11 Pro, NvidiaGTX 1070, newest studio driver, but even if GPU acceleration is entirely disabled (both in Video and File I/O tabs) nothing helps, no difference. No difference between legacy and non-legacy decoding either. Repeat: every option looks in preview window as/like 8-bit full range, and that way it is rendered to final file.

Update: the same with MJPEG videos (yes, now natively decoded by Vegas without need of external codec) and old DV files captured by firewire from DV tapes. Really, didn't You people notice all that?
BTW another small inconvenience, but really insignificant compared to the above, is as follows: if two clips originating from the same source video file are crossfaded, passing through the crossfade seems very hard to Vegas, both in playback from timeline and in rendering - video slows down and stutters. Final render is not affected, good and smooth, no dropped frames. It's just only the passing through the crossfade feels hard for the software. This can be remedied by switching "legacy decoding" on. The problem does not appear, if crossfaded clips originate from separate source files.
Other than the above, new Vegas 23 behaves light and fast. Render of 1080p50 is 2x faster than normal playback. And please, don't blame "old hardware". My hardware is enough for newest win 11 25H2 to run very smoothly, 100% compatible with no issues outside Vegas.

Known issue only with ProRes4444 that should be fixed soon.

Well, to me looks like not only ProRes is affected but also decoding old simple x-avc and avc-aac h.264 as the source media is also affected - the entire color engine might be broken. There is no difference in color range if and when switching between 8-bit legacy, 8-bit full range, 32-bit etc. in project properties. Every option has contrast and color range like 8-bit full range. Win 11 Pro, NvidiaGTX 1070, newest studio driver, but even if GPU acceleration is entirely disabled (both in Video and File I/O tabs) nothing helps, no difference. No difference between legacy and non-legacy decoding either. Repeat: every option looks in preview window as/like 8-bit full range, and that way it is rendered to final file.

@Ruprych The color engine isn't broken. The conversions of color matrices and spaces is now functional in VEGAS (before it didn't know what to do with non Rec709 and Rec2020 gamuts for example). However this means that in 8-bit video and 32-bit video mode the footage is getting expanded into full range, which may be intentional but breaks the legacy workflow.

You can restore the old behavior here in internal preferences (hold shift and go to the options menu and "internal" will appear at bottom). Change TRUE to FALSE in the highlighted cell.

Yes we noticed this and commented on it weeks ago.

For crossfades we also reported that VEGAS now seems slower if a single clip is crossfaded on itself. If it's two different pieces of media it's quite good performance. If you do a lot of this you could make duplicate media in Windows explorer (media a, media b) and just try to cross a over b instead of a over a and b over b. I hope this performance can be improved.

@Robert-Sanders @DANI-FELLA Be sure to check out the beta patch that addresses the ProRes4444 color issue here.

Known issue only with ProRes4444 that should be fixed soon.

Well, to me looks like not only ProRes is affected but also decoding old simple x-avc and avc-aac h.264 as the source media is also affected - the entire color engine might be broken. There is no difference in color range if and when switching between 8-bit legacy, 8-bit full range, 32-bit etc. in project properties. Every option has contrast and color range like 8-bit full range. Win 11 Pro, NvidiaGTX 1070, newest studio driver, but even if GPU acceleration is entirely disabled (both in Video and File I/O tabs) nothing helps, no difference. No difference between legacy and non-legacy decoding either. Repeat: every option looks in preview window as/like 8-bit full range, and that way it is rendered to final file.

@Ruprych The color engine isn't broken. The conversions of color matrices and spaces is now functional in VEGAS (before it didn't know what to do with non Rec709 and Rec2020 gamuts for example). However this means that in 8-bit video and 32-bit video mode the footage is getting expanded into full range, which may be intentional but breaks the legacy workflow.

You can restore the old behavior here in internal preferences (hold shift and go to the options menu and "internal" will appear at bottom). Change TRUE to FALSE in the highlighted cell.

Yes we noticed this and commented on it weeks ago.

For crossfades we also reported that VEGAS now seems slower if a single clip is crossfaded on itself. If it's two different pieces of media it's quite good performance. If you do a lot of this you could make duplicate media in Windows explorer (media a, media b) and just try to cross a over b instead of a over a and b over b. I hope this performance can be improved.

Thank you very much. Indeed the hidden setting fixes the issue. This changes things for me fundamentally. I would not expect this being not a bug but a hidden feature, so it haven't occured to me to browse the forum for this, because I wouldn't know what to search for. Thank you, and excuse me.
As for the stuttering transitions - it happens when one for example places a media from the explorer to the timeline, then splits it in two points, then removes the middle part, then slides the remaining parts to transition. Both originate from te same source file. As said before, if "AVC legacy decoding" is enabled in File I/O, then the issue does not occur.

No problem- I was surprised this feature had that unintended(?) result as well. Otherwise it's useful as my BT601 footage now has proper reds without doing any kind of fix (used to be orangish).

For the transitions yes, the current decoder has a bottleneck where it's processing two parts (fade, transition, etc.) from a single source file.

Vegas 23 Pro. Vegas Screen Capture is not working.
First time the Stop Button is not working.
Now i have now no screen is avaible to capture.

Same here. I can see the screens and window content when I am selecting the Capture Source. Then when selected, the source preview is blank/black and says "Not Available". Then when I start recording, the Stop Recording button does not respond.
 

Same here. I think my first version of Vegas was 15. I have updated several times and I don't think Screen Capture has ever worked well or even at all. I usually used OBS or NVIDIA screen record. Was hoping it would work this time but no. It shows the screen during selection and I can see the mouse moving around on it. Then, when I select the screen, it says, "Not available". If I "start recording" the only way to stop it is to close the vegas capture app. I do have built in intel graphics AND dedicated NVIDIA RTX 5070 card so maybe that has something to do with it.

green video envelopes (velocity or speed) are very unestable and sometimes don't even move, please fix

@EruDebu more information is needed in order to come up with a fix. It is working fine on my computer.

Start a new post, and include the information from this POST, especially "B" and "C" if you want help.

If someone has solution for Vegas Screen Capture? it make "Not Available" screen and windows capture, even my microphone.

A bug I found that is personally a dealbreaker is to do with preset chains. It doesn't save DirectX effects from third parties (AAV Colorlab, Dunaj Flip, Bororo) nor some first party effects itself (TV Simulator, Gradient Map, etc.). If you save it with a combo of non DirectX effects, the non DirectX effects are still there (but it doesn't let you drag the preset chain out of Plug-In Manager). Also, if you try to save a preset chain of only DirectX effects, it simply refuses to let you. I even have a whole thread dedicated to it too: https://www.vegascreativesoftware.info/us/forum/vegas-pro-23-visual-preset-chain-major-problem--149905/

When importing graphics with ProRes 4444 alpha, incorrect colors are displayed. On the left is the original color, which appears correctly in Vegas Pro 22. On the right, in Vegas Pro 23, it appears overexposed or shows only white with no color information.

 

 

 

I have the very same color issue. Anybody solved this? The Magix support email/X won't answer me. I've been waiting for over 10 days now for a reply

@HiNO are you using the current build, 302? These issues should be fixed.

I'm sure this is a bug in vegas pro 23,
the normal editing tool (timeline cursor) which is the tool you go back and forth with,
In all the versions I had never failed in Vegas Pro 23, yes, before I always edited very quickly and I moved from one side to the other in the timeline, it instantly played in the place where I positioned the cursor, and so super fast, but now this doesn't work for me, it is impossible for me to edit like that, now it can't be done, you have to stop, put the cursor in another position and press play again with the space bar to make it play again, and sometimes it doesn't even work like that, you have to be stopping the playback of the video in the timeline, to go and position the cursor at another point and so everything is very bad
I have realized that when you start editing and you have a few clips it doesn't happen, but when you already have several channels, one on top of the other, it gets stuck, and you can't easily scroll through the timeline, you have to pause and position yourself in the place you want and then press play again, this is very slow, and it's a total failure for me, please a solution

I have found a bug in VP23. The latest build (302) did not fix it.

- Start with the standard Windows layout,
- Under preview video, click on the 3-dot "More Buttons" icon, and edit the "visible buttons". It will add the requested buttons (such as Go to Start, Previous/Next frame, etc.) 
- Go to Color Grading windows layout (ALT+D, C)
- Come back to default windows layout (ALT+D, D)
- The preview video buttons have reverted to the default setting.

The same thing happens if you go to other windows layouts (such as mixing), and also if you edit the tracks' visible button set (to add Track Motion, or Track FX, for instance).

This happened with Vegas Pro Build 278, and it also happens with the latest build 302.

i know ignite pro plugin has been outdated for a while but theyve always worked on the previous version. one thast i use particulalryt ignite cine bars just stopps working because of this i have to downgrade to 22 for the time being. 23 is not worth using at this point in time

@ansonmccosh what is the actual name of the plugin? I have Ignite Pro in VP23. Most of the effects work, but some don't, like Lightning. But I think that is because of the GPU driver if I remember. I'd rather have an up to date GPU driver than Lightning.

@ansonmccosh what is the actual name of the plugin? I have Ignite Pro in VP23. Most of the effects work, but some don't, like Lightning. But I think that is because of the GPU driver if I remember. I'd rather have an up to date GPU driver than Lightning.

Its ignite Cine Style. Preview window just turns black

It is working here just fine. What version of Ignite do you have?

What are your computer specs? Your User Profile is blank. Add them to your Signature like I have below. Also are your GPU drivers up to date?

It is working here just fine. What version of Ignite do you have?

What are your computer specs? Your User Profile is blank. Add them to your Signature like I have below. Also are your GPU drivers up to date?

i added my signature and i currently have ignite v4 and yes my gpu drivers are all up to date...is it even possible to upgrade to v5 at this point? maybe thats the issue?

Thanks for adding your computer specs to your Signature.

Ignite version 4.1 (I believe) is the one that works with Vegas, but I have Ignite V5 installed so really can't speak on Ignite 4 working in VP23.

Since I see you have listed that you have NBFX TotalFX 360, in Essentials, have you looked at Aspect Ratio? Then you can easily add a vignette to it.

Honestly, while there are a couple of Ignite plugins I like, BorisFX and NBFX have replaced Ignite in my computer editing.

Hmm, I think I can see what's going on... I am surprised you had Ignite Pro 4.1.1 working on Vegas Pro 22 (I couldn't get that version to work past like 16 or 17, which I use 19 on a regular basis), I recommend using Ignite Pro 2021.1 if you can. Luckily for us, I have all the Ignite Pro/Express installers archived here: https://jimmyhogs.com/plugins/ignite/

@Jimmyhogs I miss typed. I have Ignite Pro 5 installed. I believe that further back, you needed Ignite 4.2 to work IIRC.

While I like Ignite, some of the features Lights & Flares are problematic and do not work with my AMD GPU and the latest drivers. If I revert back to very old drivers, everything is fine. Not worth it for me to do that. Besides, Boris FX Continuum Complete 2026 duplicates and improves upon all the old Ignite plugins. Even NBFX TotalFX 360 works. It was a sad day when Artlist took over and made outlandish promises on the "wait till you see what will be coming in Ignite Pro....." I am still waiting.

Ignite Pro Lightning on video with text that is under the video and should not be shown.