Slightly different colors from original media to imported media

Comments

sss-v wrote on 5/20/2021, 10:37 AM

@RogerS Don't you dare question the severity of my OCD!

This doesn't qualify as bang on? To my eyes, the WB effect is reducing the reds a tad. So I could dial back the amber from A2 to A1. I did consider that when I was testing, but I wasn't sure and I generally prefer be on the amber side than the blue side. I'll go back to A1 if you think that's better though. And in post I can use the WB effect to make it even more accurate. Although depending on where you click with the eye dropper, the effect does different things. So not sure how reliable that is.

Pre

Post

Didn't know what the 96% and 90% meant. I guessed it was referring to exposure. That's why I asked.

sss-v wrote on 5/20/2021, 10:43 AM

I'll work on the exposure stuff later today.

adis-a3097 wrote on 5/20/2021, 11:00 AM

Uncheck the "Studio RGB" box in Video Scope Settings as it scales differently when checked:

😉

RogerS wrote on 5/20/2021, 11:05 AM

If you want to make it in color correction you're going to have to ramp up the OCD a bit : ) Having a calibrated screen also helps for visual judgment.

Yes, I'd dial it back to A1 and test again. Such differences are 100% correctable in post (if you don't over-expose; biggest problem with incorrect white balance is that a channel will clip) but if you don't have to correct it's better.

I say get it to neutral first and you can warm it up with the temp/tint sliders under WB if you so choose. You can even save the final values as a preset and apply to every clip in the future if you always shoot the same way.

On the eyedropper don't click a single point. Click once, hold it down and drag until it turns into a rectangle. That should sample the entire area and give a more accurate reading.

96% or 90% is exposure though depending on the tool the scale is 0-255 instead of 0% to 100%. This is a minor difference and let's see where it falls after you reduce in-camera exposure.

Custom PC (2022) Intel i5-13600K with UHD 770 iGPU with latest driver, MSI z690 Tomahawk motherboard, 64GB Corsair DDR5 5200 ram, NVIDIA 2080 Super (8GB) with latest studio driver, 2TB Hynix P41 SSD, Windows 11 Pro 64 bit

Dell XPS 15 laptop (2017) 32GB ram, NVIDIA 1050 (4GB) with latest studio driver, Intel i7-7700HQ with Intel 630 iGPU (latest available driver), dual internal SSD (1TB; 1TB), Windows 10 64 bit

VEGAS Pro 19.651
VEGAS Pro 20.411
VEGAS Pro 21.208

Try the
VEGAS 4K "sample project" benchmark: https://forms.gle/ypyrrbUghEiaf2aC7
VEGAS Pro 20 "Ad" benchmark: https://forms.gle/eErJTR87K2bbJc4Q7

sss-v wrote on 5/20/2021, 11:07 AM

@adis-a3097

The white card is not where my face would be in that clip. In the clip I'm playing with the card is at 85%, and when I uncheck studio RGB it drops to 79-80%. So it's underexposed?

sss-v wrote on 5/20/2021, 11:09 AM

On the eyedropper don't click a single point. Click once, hold it down and drag until it turns into a rectangle. That should sample the entire area and give a more accurate reading.

Pro tip!

sss-v wrote on 5/20/2021, 11:23 AM

Yes, I'd dial it back to A1 and test again. Such differences are 100% correctable in post (if you don't over-expose; biggest problem with incorrect white balance is that a channel will clip) but if you don't have to correct it's better.

Sticking with A2. The WB effect seems to be making a smaller adjustment with A2 than with A1.

adis-a3097 wrote on 5/20/2021, 11:23 AM

@adis-a3097

The white card is not where my face would be in that clip. In the clip I'm playing with the card is at 85%, and when I uncheck studio RGB it drops to 79-80%. So it's underexposed?

Well, in the clip that ScrapyardFilms uploaded the white card is at 96. Different clips, different in camera settings maybe? :)

sss-v wrote on 5/20/2021, 11:26 AM

@adis-a3097

Same camera setting I believe, but maybe the soft box was more directly on the card in that position?

adis-a3097 wrote on 5/20/2021, 11:57 AM

Possibly. :)

sss-v wrote on 5/20/2021, 12:07 PM

Uncheck the "Studio RGB" box in Video Scope Settings as it scales differently when checked:

😉

@adis-a3097

btw, I should always keep that unchecked? Why? What's the difference?

Marco. wrote on 5/20/2021, 12:17 PM

If it is unchecked Vectorscope and Waveform would not correspond to the displayed levels. Check yourself via a standardized test pattern and gradient.

sss-v wrote on 5/20/2021, 12:20 PM

@Marco.

Not following, could you elaborate?

Marco. wrote on 5/20/2021, 12:25 PM

Test yourself. Put two generated media into your timeline, the default Color Gradient (which is a grayscale ranging from RGB 0 up to 255) and the Color Bar (PAL).

Now see what the waveform monitors shows for the gradient and what the vectorscopes shows for the single colors of the color bar. Now turn this videoscopes Studio RGB option on and off.

adis-a3097 wrote on 5/20/2021, 1:03 PM

Uncheck the "Studio RGB" box in Video Scope Settings as it scales differently when checked:

😉

@adis-a3097

btw, I should always keep that unchecked? Why? What's the difference?

Well, you have to know what you are measuring; your clip is "full range", so checking the Studio RGB box will show overs (>100%) and unders (<0%), since Studio RGB's 0%-100% scale is related to 16-235 level range, or "limited", and not to 0-255 level range or "full". It also depends on what Pixel format you choose (video levels or full range). Funny how your clip isn't affected by Pixel format flip though...

So, no, not always, just sometimes. :)

sss-v wrote on 5/20/2021, 1:04 PM

@Marco.

Either I can't follow the instructions properly, or don't know what I'm looking at. Can you dumb it down for me a bit? Or just tell what setting I should be using!

sss-v wrote on 5/20/2021, 1:07 PM

@adis-a3097

So if I leave the Studio RGB box checked, it may show certain things as clipped even though they are not?

Marco. wrote on 5/20/2021, 1:22 PM

I have this option (almost) always checked. It then shows the color saturation and video levels right as I see them in the preview.

Though both option would signal clipped levels (just at different positions).

adis-a3097 wrote on 5/20/2021, 1:22 PM

@adis-a3097

So if I leave the Studio RGB box checked, it may show certain things as clipped even though they are not?

Yes.

But do what Marco said: go to Media generator tab/test patern and drag/drop SMPTE Bar (PAL) into the Time line. Play with Video Scopes Settings, see what happens. :)

Marco. wrote on 5/20/2021, 1:29 PM

Or use same pattern I used (> download).

Apply the Level FX and use the preset "Studio RGB to Computer RGB" to see how clipping is shown in both videoscopes options.

adis-a3097 wrote on 5/20/2021, 1:31 PM

Here's some video test patterns:

https://drive.google.com/file/d/1piYIGaKamryy_DmKkVKEHwxywjzH5T7d/view?usp=sharing

Switching between full range and video levels under Pixel format does show different results in RGB parade and Waveform monitor, as opposed to SMPTE Bars from Media Generator.

Musicvid wrote on 5/20/2021, 4:14 PM

sss-v wrote on 5/19/2021, 4:52 PM

@Marco.

I didn't encode anything in HandBrake. I just imported the original camera file in HandBrake and used preview to see what it looked like since @Musicvid said that HandBrake gets both the levels and colors right.

The Straw Man says, "Musicvid said the file encoded in Handbrake gets both the levels and colors right." Musicvid posted a graphic of the Handbrake-encoded file showing the matching red vector. Musicvid said nothing about the Handbrake GUI or preview levels. Thanks for not putting words in Musicvid's mouth. Makes him touchy.

Post hoc ergo propter hoc

Musicvid wrote on 5/20/2021, 4:59 PM

@Marco.

Thank you for that test pattern! It's a keeper; wish I'd thought of it.

It told me straightaway I had the waveform levels set to Studio, although I use the histo for my leveling.

sss-v wrote on 5/20/2021, 5:55 PM

@Musicvid

Not so sure about people who talk about themselves in third person! ;-P

I didn't mean to put words in your mouth. Put it down to my lack of video knowledge and lack of sleep from spending too much time on this issue.

You made me doubt my solution again though. It seems everyone agreed that Vegas was getting the levels right and VLC was getting the levels wrong. In HandBrake (preview) the levels were similar to Vegas. So me using HandBrake (and Vegas) as reference for the levels was correct?

I just went a couple of rounds with some kind of food poisoning, got knocked down but made it through. I think I'll investigate the exposure stuff tomorrow.

Thanks again everyone. I wasn't expecting this much help!