VEGAS Pro brightness darker than original file on preview and render

jetdv wrote on 9/11/2025, 3:16 PM

@Chris021 There is no difference between the "trial" and the "release". Why would they "apply a filter" in the trial? Sort of defeats the purpose of testing. But it looks like you'll need to provide a lot more information about the video file you're looking at as well as project settings, render options, etc...

Chris021 wrote on 9/11/2025, 3:31 PM

I've tried by opening a V19 project. Both preview in time line and render are darker or too much contrasted. No effects applied to original file

RogerS wrote on 9/11/2025, 5:01 PM

Are you using 32 bit ACES mode? Please share your project properties.

Here they match.

Chris021 wrote on 9/12/2025, 1:43 AM

I have this problem when opening some old V19 projects, not all.
I've tried to open my V19 empty project file (containing some files I always use for each video) and add new files, it's OK.
All my videos were done starting by the same empty project, so I don't understand why this affects some projects not all.

Here are my project properties

PS : Is there a way to change language without installing Vegas again ?
I would like to switch betxeen french and english when needed.

RogerS wrote on 9/12/2025, 6:32 PM

I think I might have the answer. The new version of VEGAS has an automatic color space correction function that is overriding the "do nothing" approach that 8-bit video levels had. If you hold shift and go to options and enter internal preferences, search "enable extended color format conversion" and change true to FALSE.

If you were working in the automated 8-bit full mode you wouldn't see a difference.

For languages you used to be able to change it in the registry. This tool had an interface for it. Not sure if that still works. https://www.semw-software.com/en/extensions/

Chris021 wrote on 9/13/2025, 6:06 AM

Thanks for this information.
Though, I'm not able today to reproduce this issue with the same file... that's strange
So I can't confirm if this parameter was the cause.
"enable extended color format conversion" is set to TRUE

RogerS wrote on 9/13/2025, 7:47 AM

If you want to use legacy 8-bit video or 32-bit video projects it needs to be set to false (or you need to re color correct it).

Chris021 wrote on 9/13/2025, 9:00 AM

Thanks, I will change it

Chris021 wrote on 9/14/2025, 9:13 AM

Again today, I have a similar problem but now the Vegas file is brighter than original file, with "enable extended color format conversion" is set to FALSE. I really do not understand the issue. mp4 files always comes from my Panasonic G9

Original :

Vegas :

RogerS wrote on 9/14/2025, 10:45 AM

It's probably limited video range? If you work in video range you have to manually adjust it to 0-255 for viewing (studio to computer RGB Levels Fx preset).

Or use full range mode which maps it automatically.

Chris021 wrote on 9/14/2025, 12:31 PM

Thanks for reply but I'm not a pro and I don't understand where to adjust video range.
I haven't applied any FX effect to the video, it happens on a nex video track.

RogerS wrote on 9/14/2025, 9:17 PM

If you don't understand video levels and don't want to learn you should never use 8-bit video or 32-bit video. Use 8-bit full or 32-bit full (view transform off).

Old versions of VEGAS just showed you the image as it was. So the washed out looking version is actually what your video looks like (the player is doing a conversion). To see what it should look like you need to map a brightness of 16 darker, to 0, and a brightness of 235 lighter to 255. The levels Fx can do this with the preset that I stated. If you do edit in full range (0-255) you still need to render to video range (16-235) or the player may cut off whites and blacks.

In VP 18 VEGAS introduced 8-bit full mode which handles these conversions automatically.

Chris021 wrote on 9/16/2025, 5:57 AM

Thanks Roger
So, if my understanding is good, I should use 8-bit Full in project properties. I've tried and yes now it's OK.
But I don't understand what I should do for render. I don't see where I can set 16-235 video range.

RogerS wrote on 9/16/2025, 5:58 AM

For render you don't have to do anything : ) It automatically renders to video levels with most templates including to the one you chose.

Chris021 wrote on 9/16/2025, 6:30 AM

OK perfect, thanks again, your help is precious here 😊

RogerS wrote on 9/16/2025, 6:45 AM

No problem, it took me so long to understand it myself.

andyrpsmith wrote on 9/16/2025, 8:04 AM

Yes I too find all the technical details regarding video levels, colour mapping, colour space confusing. I only take serious video via a Sony AX700 4K camcorder and off the cuff video from an iphone SE. I decided to buy the excellent video master class for my AX700 from Doug Jensen which over 16 chapters explains all the options and gives suggestions on how to use the camera to achieve what you are looking for. I really liked the fork in the road analogy, you can set up your camera to take video which either requires significant post editing or set it to produce WYSIWYG - What You See Is What You Get. which does not require the same amount of correction in post and is likely to allow faster completion of your project. I chose WYSIWYG and have never regretted it. I dump the clips on the time line and use the video scope RGB Parade to confirm the video levels (ie how the pixels are distributed for Red Green and Blue over the 0-255 scale). I always set the project template to 8 bit full range since Vegas first offered this setting. Before V23, changing the project setting from 8 bit full range to Legacy Limited range was reflected by a visible change in levels in the preview window - great just what I like. To get this you now have to disable the new extended colour format conversion - glad it is an option but a shame is requires you to go into the internal options menu. With WYSIWYG I only have to tweak a few clips to adjust 0-255 levels and I tend to use the simple FX - Levels Filter (or if you wish the colour grading panel via an s curve. As my OLED 4K TV is not phased by 0-255 video level span my video generally covers the full span. On export I set the colour range to full in the render template project tab. Doing this always gives me a rendered video that perfectly matches what is displayed on the Vegas preview screen. This works for me and everyone will have their own way of reaching the output they desire.

RogerS wrote on 9/16/2025, 8:26 AM

Just a word of warning- most players expect video levels and ignore the range flag. Even uploading such a video to YouTube results in blown out highlights and crushed blacks doesn't it? If the only screen you'll view the file on is your TV and it honors the range flag then 0-255 (or even 10-bit 0-1024) is fine. I hope this archaic video levels standard goes away before long and HDR should hasten that.