@lan-mLMC please note that a user may notice your request better if tagged.

@lan-mLMC please note that a user may notice your request better if tagged.

Hi, thanks.

the color which VEGAS transmits to plugins is Studio RGB or Computer RGB?

Plugins get their input signal as-is, there is no transformation. If you've got Studio RGB on the timeline, the plugin will get Studio RGB as its input. If you've got Computer RGB on the timeline, the plugin will get Computer RGB.

The consequence for plugins that depend on the convention used is:

• Either the plugin tells you what it wants and you need to make sure it gets the correct format, or
• the plugin has an option for you to tell it what kind of input it gets.

Here's a configuration for Graide Color Curves to put some red into the low end. In Computer RGB mode, it acts on the superblack bar (because that's just black in Computer RGB) but not the "black" area (because that's dark gray in Computer RGB):

In Studio RGB mode, it acts on the "black" area but not on the superblack bar (because that's darker than black in Studio RGB):

@Satevis Hi, do you mean that : in common 8-bit project, the color which plugins receive from vegas is StudioRGB(16-235).

Afters plugin finishes adjustment, the plugin-adjusted color which it pass to vegas will be processed in StudioRGB(16-235) way again.

And then the processed-StudioRGB(16-235)-way-again color is what the vegas preview shows?

Summary:

Vegas sends the StudioRGB color to plugins;

Plugins adjust the StudioRGB color and get a adjusted color;

Plugins send the adjusted color to Vegas;

Vegas converts the adjusted color to a re-StudioRGB color and shows it in preview window?

I mean that VEGAS does not change* the pixel values at all, neither the plugin input nor the plugin output. If your input file says, a pixel has "value 18", then VEGAS will tell the plugin there's a pixel with a value of 18. If the plugin changes this to a value 20, then VEGAS will send a 20 on to the next plugin or whatever follows in your signal chain. What exactly 18 and 20 mean is a matter of interpretation. If you're rendering to WMV or JPG, that would be a very dark gray. When rendering to MP4, it would be near black.

The preview window just draws what it gets, but since it draws onto a Computer RGB display, what you see in the preview is a Computer RGB interpretation of the signal (very dark gray in this example). You can use the SeMW Extensions to switch to a Studio RGB interpretation (by inserting a signal transformation, which clips the high and low ends). Then the preview would draw a 5 when it gets a 20, which is similar to what you would see when you would render a 20 to MP4.

* As one exception to this general rule, in 32 bit full range mode, VEGAS does an internal Studio RGB->Computer RGB conversion when reading certain input formats and a Computer RGB->Studio RGB conversion when rendering to certain output formats. This may be closer to the workflow you expect. I suspect a similar option is not available for 8 bit because many users in VEGAS' target audience would have concerns about unnecessary signal transformations back and forth in the limited 8 bit value space. This is less of a problem with 32 bits, of course.

@Satevis Probably understand what you say. You mean that it is just display resault looks different between ComputerRGB and StudioRGB, but their real pixel values are the same.

Hope VEGAS team does an internal Studio RGB->Computer RGB conversion in 8-bit project. I have seen a great many newbies turn to other NLEs because of the 8-bit project's problem: "original clip's color ≠ Vegas preview ≠ rendered video".

Imaging you droped on time-line JPG and MP4.

In JPG: 0 -- black. 16 -- dark grey.

In MP4: 16 -- black.

VP will show you differences in preview. JPG's black will be black. MP4's black will be dark grey.

Then it is up to you what to do. And only you know what would you like to have at the end.

Usually, as you are editing video and working in video editor you should follow standards where 16 should be black. So you have to correct your JPS's levels so 16 will be black by applying Computer RGB to Studio RGB and then you will see slightly washed out picture in preview (as already explained, preview is in Computer RGB). In scopes everything would be fine: black will be 16. When you render this to MP4, video players will correctly display 16 as black.

However, you may decide to adjust MP4's levels as Studio RGB to Computer RGB and then render this as a set of TIFFs! All these TIFFs will look similar -- 0 will be black.

If you dropped Mp4 on time-line, render it into MP4 without correction, you will see the same levels. VP will not do anything!

If you start to edit using preview (but not scopes) without understanding the things above then you will get into trouble. Unfortunately, you need to learn how tool works.

P.S. This is simplified version. There are some caveats. Like some camcorders may provide 16-255 instead of 16-235. In some containers no meta and video content could have unusual "meaning". Etc.

It sure would be nice if Vegas could do all of this by default? 😅

It sure would be nice if Vegas could do all of this by default? 😅

@wwjd … that is inspired. Thank you very Munch.

@wwjd … that is inspired. Thank you very Munch.

well played! :D

We should also add to this FAQ that certain .photos .jpgs .etc. with ICC flags will NOT render will the appropriate levels until you convert that photo into another jpg/png.etc. Removing the ICC flag. All iphone photos use a ICC flag.

https://www.vegascreativesoftware.info/us/forum/vegas-changing-colors-of-my-photos-with-levels-fix--120727/

Such photo ICC profiles are meant to adopt your display with your print results, they are not meant and not usefull for video editing.

Here's another good reference for tackling this issue https://www.vegascreativesoftware.info/us/forum/vegas-pro-levels-last-and-final-1--120319/

With the new Version of Vegas 18 the levels FIX is IN! Simply put your project on 8 Bit Full Range and you are good to go!