Vibrance FX Tips

ALO wrote on 6/15/2021, 10:05 PM

I'm working a lot with GoPro footage these days, which is fairly neutral but also pretty lifeless in native/flat mode, and a big challenge is getting the colors to look rich and properly saturated. Vegas doesn't have a vibrance plugin, so the goal here would be to duplicate the effect of something like Photoshop's vibrance slider in Camera Raw -- basically something that enhances non-skin tone colors without making everything look blown out or neon-candyish.

For starters I use color curves to just draw a contrast-enhancing curve over the clip. This on its own helps bring up the colors. Then I turn to the Color Corrector Secondary, and use that plugin to modestly boost overall saturation.

Then I add another CCS instance, and this time target a specific color using the "select range" tool. For example, going after the blue in a blue sky. When I've got the color appropriately targeted, I might try adjusting it's hue a little, and then dialing up saturation. Maybe next I'll go after greens and to the same thing with another instance of CCS.

You can also come at this from the opposite direction and target skin tones, and then invert the mask.

Either way works, and has the advantage of staying entirely within Vegas' stock tool set. Especially with GoPro footage there is the danger of banding starting to appear in skies when you push up the vibrance this way. You may find the banding gets a little better if you switch to 32-bit video levels in project properties before rendering out. Or not.

I definitely can't match the quality of Photoshop's adaptive algorithms (esp. DeHaze!) using this stacked Color Corrector (secondary) technique, but this works a lot better than just a basic saturation boost--and it gives some control over individual color hues (for example, if your forest trees look a little too yellow but you don't want to touch anything else)

One other technique I've played around with is using the Unsharp Mask fx to boost local contrast (using larger radiuses). But I eventually gave up on that because it was too hard to predict/control the results.

If anyone else has vibrance tips (working within Vegas' stock set of fx) and you're willing to share, please let me know.

Comments

monoparadox wrote on 6/15/2021, 11:08 PM

You don't mention which version of Vegas you're using, but as a general approach I almost always start with the levels adjustment. With the use of scopes one can achieve a lot just using the levels adjustment. The latest color correction module in Vegas can get you down the road with automatic color levels.

RogerS wrote on 6/15/2021, 11:28 PM

Graide Color Curves provides a much faster way to alter saturation by range or even luminance. I stopped using color corrector secondary as it took too much time.

Alternatively, Leeming LUT has GoPro technical LUTs to give a better starting point.

Last changed by RogerS on 6/16/2021, 12:18 AM, changed a total of 1 times.

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 and 2TB Samsung 980 Pro cache drive, Windows 11 Pro 64 bit https://pcpartpicker.com/b/rZ9NnQ

ASUS Zenbook Pro 14 Intel i9-13900H with Intel graphics iGPU with latest ASUS driver, NVIDIA 4060 (8GB) with latest studio driver, 48GB system ram, Windows 11 Home, 1TB Samsung SSD.

VEGAS Pro 21.208
VEGAS Pro 22.239

Try the
VEGAS 4K "sample project" benchmark (works with VP 16+): https://forms.gle/ypyrrbUghEiaf2aC7
VEGAS Pro 20 "Ad" benchmark (works with VP 20+): https://forms.gle/eErJTR87K2bbJc4Q7

RogerS wrote on 6/16/2021, 12:18 AM

AAV Color Lab is free and still works in Vegas: http://aav6cc.blogspot.com/

It's usable to change hue or saturation of the 6 main colors it has. I'd still recommend Graide for precise control.

ALO wrote on 6/16/2021, 8:50 AM

You don't mention which version of Vegas you're using, but as a general approach I almost always start with the levels adjustment. With the use of scopes one can achieve a lot just using the levels adjustment. The latest color correction module in Vegas can get you down the road with automatic color levels.

Yes color correction and then levels always come first. The Graide plugin looks very nice! But I am trying to stay within Vegas' current stock fx set. Figuring out new ways to use the existing native fx is kind of like solving a puzzle. :)

RogerS wrote on 6/16/2021, 9:04 AM

Hi Alo, in addition to the color correction secondary, you should have selective hue by NewBlue. It has similar functionality but I found the interface to be quicker to deal with. I used to stack a few of these to do selective hue and saturation tweaks.

For what you're doing I think that's about it. The native Fx aren't really well suited for this.
You can also use Bezier masking to mask Fx and limit your corrections to one place in the image.

I do recommend AAV for quick fixes and it's free.

If it weren't for Graide I'd be using Resolve- having the hue-hue curves, etc. is just so time-efficient.

ALO wrote on 6/19/2021, 10:15 PM

 

If it weren't for Graide I'd be using Resolve- having the hue-hue curves, etc. is just so time-efficient.

 

Thank you for letting me know about this plugin! It is immensely useful.

RogerS wrote on 6/19/2021, 11:49 PM

Of course. My only regret is that I didn't realize its value earlier! (I thought "Curves- I already have color curves!") Enjoy.

alifftudm95 wrote on 6/20/2021, 4:06 AM

VEGAS Pro only have the basic saturation slider, but not vibrance. You will need plugins for this.

 

Can try Graide plugin as @RogerS mentioned.

Or use 3DLuTCreator plugin which allow you to make extreme hue modifications without introducing color banding, even with 8 bit color profile.

Editor and Colorist (Kinda) from Malaysia

MYPOST Member

Laptop

MacBook Pro M4 Max

16 Core CPU and 40 Core GPU

64GB Memory

2TB Internal SSD Storage

Anti-Glare 4K HDR Screen

 

PC DEKSTOP

CPU: Ryzen 9 5900x

GPU: RTX3090 24GB

RAM: 64GB 3200MHZ

MOBO: X570-E

Storage:

C DRIVE NVME M.2 1TB SSD GEN 4

D DRIVE NVME M.2 2TB SSD GEN 4

E DRIVE SATA SSD 2TB

F DRIVE SATA SSD 2TB

G DRIVE HDD 1TB

Monitor: Asus ProArt PA279CV 4K HDR (Bought on 30 August 2023)

Monitor: BenQ PD2700U 4K HDR (RIP on 30 August 2023)

 

 

 

D7K wrote on 6/20/2021, 8:11 AM

Have you tried saving a frame, taking it into photoshop and correcting it and then export a LUT so you only do it once a project?

ALO wrote on 6/20/2021, 11:11 AM

Have you tried saving a frame, taking it into photoshop and correcting it and then export a LUT so you only do it once a project?

This is a totally viable solution -- thanks for mentioning. PS is a little wonky when it comes to creating LUT's and you can't access the full power of the app, so another strategy would be to work on a frame in PS, save it, import back into Vegas, and use Vegas Color Match which seems to have gotten better since its earlier editions.

You could also do the same with Resolve, which is very good if you can stand working with it.

Roger, you've broken my heart (and on father's day no less!). After further testing, it seems the Graide plugin's most useful tools (the hue/brightness/saturation dependency curves) all bleed like crazy when you try to isolate. I guess it's back to the hit-or-miss alchemy/voodoo of the CC (secondary) for me. :(

RogerS wrote on 6/20/2021, 12:12 PM

What do you mean bleed? You control that by using eyedroppers to set the range and then manually add points outside it to eliminate bleed. The distance you choose between the selection and outside points determines the severity of the transition and lets you give it a bit of roll-off.

ALO wrote on 6/24/2021, 2:13 PM

What do you mean bleed? You control that by using eyedroppers to set the range and then manually add points outside it to eliminate bleed. The distance you choose between the selection and outside points determines the severity of the transition and lets you give it a bit of roll-off.

Attempting to isolate a range in Graide via this method results in hues/saturations/luminances across the entire image being affected, even for narrow targets. Huge difference compared to same targets/methods in Resolve.

It may be that Graide is correctly but dumbly applying the effect to all pixels that meet the criteria (ie, including color noise scattered about the image). Regardless, the quality of the algorithm is about what you'd expect for the price. It's a shame. This is otherwise one of the key color tools that Vegas is missing.

RogerS wrote on 6/24/2021, 8:40 PM

Are you sure you are using it right? Feel free to post a screenshot.

Working from a color chart and isolating individual and groups of colors to standardize cameras, I didn't see that. I did have to be careful with the selections but the eyedroppers gave good insight into where the colors were I wanted to affect. Similar issue to selecting the range in color corrector secondary, but faster to apply.

Color noise shouldn't be noticeable - who cares if a green pixel in the shadow is slightly yellowish or bluish due to a hue change? You could also desaturate shadows with saturation over luminance if you are having issues with shadow color casts.

ALO wrote on 6/25/2021, 10:56 AM

Roger I tried switching to footage from a different (much cleaner) camera. Then I targeted skin tones in both Vegas via Graide, and Resolve via its native curve tools.

Simple hue correction to bring skin inline with vectorscope target -- both apps' results look very close.

Switch to sat dependent on hue and target the skin tones, and Resolve alters skin tones but leaves everything else in the scene (person standing in front of a mountain on a sunny day) alone.

Graide pumps up saturation in scattered points and splotches around the image -- very noticeable. I tried narrowing the selection range to the point where the skin started to look splotchy. The bleed into the background continued.

It looks like either the Resolve algorithm is far more intelligent, or something is going wrong in Graide's selection/adjustment scheme (or both).

ALO wrote on 6/30/2021, 4:10 PM

Have you tried saving a frame, taking it into photoshop and correcting it and then export a LUT so you only do it once a project?

After much experimentation, I think D7K has by far the most useful advice in this thread. I have tried all of Vegas' saturation tools; it is clear they indiscriminately target saturation across the entire image, resulting in a progressively more cartoonish and less contrasty look. In comparison, Photoshop's saturation intelligently augments saturation depending on pixel brightness, resulting in a more natural, punchier image.

I have tried to replicate the effect using Vegas' CC (Secondary) fx, which takes a lot of time and gives at best erratic results. My strong preference is to stay within Vegas' native toolset, but at some point you just have to stop trying to pound nails with a screwdriver.

If you have access to PS, note that you can create a set of generic LUTs that apply saturation and/or vibrance in whatever increments you desire, giving you in effect access to these two PS algorithms entirely within Vegas.

This should be especially useful for those working with GoPro footage shot in native/flat mode, but is certainly worth a look for any of you who regularly use Vegas' native fx to enhance saturation.

RogerS wrote on 6/30/2021, 8:36 PM

Roger I tried switching to footage from a different (much cleaner) camera. Then I targeted skin tones in both Vegas via Graide, and Resolve via its native curve tools.

Simple hue correction to bring skin inline with vectorscope target -- both apps' results look very close.

Switch to sat dependent on hue and target the skin tones, and Resolve alters skin tones but leaves everything else in the scene (person standing in front of a mountain on a sunny day) alone.

Graide pumps up saturation in scattered points and splotches around the image -- very noticeable. I tried narrowing the selection range to the point where the skin started to look splotchy. The bleed into the background continued.

It looks like either the Resolve algorithm is far more intelligent, or something is going wrong in Graide's selection/adjustment scheme (or both).

I did a similar test between the two programs and couldn't really see a difference in functionality. Selections take more time in Graide as you have to make multiple points to limit the range affected. However, I do like that you can select and manipulate multiple points on the curve at once and copy from one curve to another (hue vs hue to hue vs sat, for example). In Resolve you can use the spline feature to quickly set the width of the affected area. I don't normally like splines on curves (just give me more points) but for this it's helpful. I see spill into the background in Resolve as well if there are overlapping tones. In both you can limit that with masking.

Personally, for time efficiency reasons I'd go with a technical correction LUT to get the GoPro into a better place to start grading from. The one I use is here.

ALO wrote on 7/1/2021, 10:45 AM

Roger thanks for the link! Learning how to work with GoPro footage within Vegas has been a long, long road but I'm finally starting to be pleased with the results.

I'll try to post a screenshot of my Resolve-Graide curves comparisons. For me it wasn't a subtle difference.