Graide Color Curves

Comments

AlesCZ wrote on 6/8/2019, 12:07 PM

I found one interesting thing. If I edit in curves and the project is not saved, Vegas does not warn of unsaved changes when it is closed. Vegas does not register new changes (in curves) and simply closes :)

Satevis wrote on 6/8/2019, 1:01 PM

That is indeed interesting and can also be seen with the custom UI of the standard color corrector. Apparently, when an OFX plugin changes its parameters on its own, Vegas does not include that action in its undo history and does not consider the project changed. It may be possible to explicitly notify Vegas that there has been a relevant change. I'll look into that.

Former user wrote on 6/8/2019, 3:47 PM

In the end, it might make most sense to interpolate between the final effect results (much like the effect strength does), at which point you may just as well just split the event, have different color curves on both halfs, and then do a cross-fade between the two parts.

Thanks for the answer. I have done it that way and it works fine.

3POINT wrote on 6/9/2019, 12:43 AM

@Joelson-Forte

Maybe you could make a shortvideo tutorial how to use Graide Color Curves. I like your video tutorials, they simple show what to do and are straight to the point, without boring talk or annoying self expression like those many Vegas YouTubers.

AlesCZ wrote on 6/9/2019, 1:37 AM

Great for Color Grading :)
Quick test:

matthias-krutz wrote on 6/9/2019, 4:37 AM

Apparently, when an OFX plugin changes its parameters on its own, Vegas does not include that action in its undo history and does not consider the project changed.

There is a separate item in preferences > general. This should solve the issue. I could not test it with Graide Color Curves yet.

-> Create undos for FX parameter changes

 

Desktop: Ryzen R7 2700, RAM 32 GB, X470 Aorus Ultra Gaming, Radeon RX 5700 8GB, Win10 2004

Laptop: T420, W10, i5-2520M 4GB, SSD, HD Graphics 3000

VEGAS Pro 14-18, Movie Studio 12 Platinum, Vegasaur, HOS, HitfilmPro

Robbie wrote on 6/9/2019, 4:43 AM

@Satevis - I do a lot of restoration work so I’m really looking forward to downloading and trying both Color Match and Color Curves when I get back from a business trip next weekend.  I note though that compatibility is shown as VP 10 through to 16 and MSP only versions 12 and 13.  Will they not work with the newer Magix versions of MSP?  I have VP15 so all good, but it would be great if they also work in my various versions of MSP.

Cheers, Robbie

Marco. wrote on 6/9/2019, 5:02 AM

Graide Color Curves seems to work fine here in Movie Studio Platinum 16.

Graide Color Match work fine, too, with the exception I need to grab the reference image via the clipboard.

Satevis wrote on 6/9/2019, 7:18 AM

Yes, that's purely because I haven't personally tested it with any newer version of Movie Studio Platinum.

@AlesCZ Those are some great examples!

@matthias-krutz Thanks for pointing me to that option. It was already enabled, however, so I suppose I could only use it to turn off undo for all the other effects, too.

max8 wrote on 6/26/2019, 7:52 PM

Hello,

I just tested the trial version: great handling of the curves - things the "original" Vegas version lacks are finally very easy to do. And the added curves (Y-->S,...)!

But there are two things I stumbled upon (V15, build 321):

1. In 32 bit mode everything looks fine in the WFM - like it should. In 8 bit mode even slight changes of the Y curve generate comparatively obvious banding while the "same" curve done with the normal color curves plugin generates only a "normal" amount of banding so that you could use its result for a quick color correction with decent quality - if you wanted to. I can imagine that maybe a curve that looks the same in both plugins is not really the same. But I find it strange that so much banding happens. Best compared with the preset "studio RGB to computer RGB", the "same" preset ("PC") of the SeMW extensions seems to perform the same in the WFM - only with less banding (OK - it uses the levels plugins, but...). The "solution" to this comes with:

 

2. (independent of 32/8 bit - except the WFM/banding of course) The visual result of the "same" curve (again only Y/brightness) differs alot in the video preview, although the WFM seems very similar to the one with the Vegas color curves (assuming almost the same curve...). I am simply not able to get the effects/results I am used to when handling the Graide Y curve. In comparison the picture seems too bright/less saturated. I am comparing the "RGB" mode of the Vegas plugin with the Y curve. To my understanding that should technically be the same (Y = brightness = same changes to R, G and B). Am I wrong?

Results got much more like I expected them to be as I copied both nodes i changed (great that this is possible!) from the Y curve and pasted them to the R, G and B curves. I then deactivated the original Y curve and finally got as close to the Vegas plugin as it is possible by approximating the curves visually. And the banding was also gone! But shouldn't be RGB=Y? The Vectorscope shows that the Vegas plugin changes also the saturation when manipulating the RGB curve while the Graide color curves almost don't change it. That was probably the cause of the impression of a less saturated image.

 

So do I understand this plugin and its concept totally wrong? I always thought that raising the brightness means amplification of Y, which means amplification of RGB to equal parts and thus generates a higher "absolut" (measured) saturation, but staying the same visually and relatively to the Y component.

Could someone explain that further, please? Thanks! ;-)

Satevis wrote on 6/27/2019, 3:08 AM

Thanks for the great feedback!

Strictly speaking, there is no Y' in the RGB color space: An RGB color only has an R, a G, and a B value, wheras Y' is a value from color spaces such as Y'CbCr. But because you can, of course, transform an RGB color to the Y'CbCr space, you can clearly state a Y' value for any given RGB color.

A bit less clear, however, is what "changing the Y'" means in RGB terms. There are at least two ways to do it:

  • Multiplying the RGB values by a common factor changes the Y' of the color, but as you correctly observed, also changes its saturation. This is neither good nor bad, just something to be aware of.
  • Transforming the color to Y'CbCr, changing the Y', and transforming it back does not affect its saturation and keeps it on the same place in the vectorscope, but stretching the contrast will result in a more washed-out look of the image (because mathematical and perceived saturation are two different things here). Again, this may or may not be desired.

Some color grading tools give you control over which method is used. In Resolve, for instance, there is a "Y" slider for "Y-only adjustments" next to the RGB controls. In Graide Color Curves, you've got the Y' curve, which (clipping aside) really only affects Y'. In both cases, changing Y' only is not the same thing as changing all three RGB channels by common factor.

max8 wrote on 7/5/2019, 8:08 AM

You explained that a lot better than I did - thanks!

But would it be possible to add this feature? I can't really get used to the way the Y'-control affects the image. Or is there a different approach? Mainly I have to match different (or poorly matched) cameras. When I'm trying to correct the "exposure" I don't want to change the perceived saturation or get a washed-out look because that also wouldn't happen when closing or opening the camera's iris.

Satevis wrote on 7/5/2019, 8:27 AM

If the Y' curve bothers you, you can always hide it with the "Y'" button in the lower left corner and forget about it. Then, if you want to edit the three RGB curves in unison, enable "Overlay curves" and select points by dragging a rectangle around them (selecting the corresponding points on all three curves). When adding new points, add a point to one of the curves, then use Ctrl+C, Ctrl+V to copy it onto the others.

karma17 wrote on 7/6/2019, 2:28 AM

This is very informative. I will have to ck this out. It has always been my dream to keep everything in Vegas and no round tripping. So it is nice to see these advancements.

Satevis wrote on 8/7/2019, 5:23 PM

I've just uploaded a new version that now uses a slightly different approach for the smooth control points. This should prevent the curve from bending too much when control points are close together.

Also, this new version fixes a compatibility problem that would prevent the plugin from appearing in Vegas 17.

https://www.semw-software.com/colorcurves/

Marco. wrote on 8/7/2019, 5:29 PM

Much appreciated!

NickHope wrote on 10/16/2019, 11:48 AM

@Satevis I started a trial of this. Is there any way to unlock/split tangents of a node so I can make a curve equivalent to this?

Points are at 0/16, 16/16 and 255/235. The bottom left section should be linear and horizontal then I would like to adjust the tangents at each end of the long section of the curve.

Marco. wrote on 10/16/2019, 11:58 AM

Hold the Ctrl. key pressed while adjusting one of the tangents.

NickHope wrote on 10/16/2019, 12:31 PM

Thanks. That works. But thereafter it would be nice to be able to keep the tangents unlocked without having to hold down CTRL each time a further adjustment is made.

frmax wrote on 10/16/2019, 12:35 PM

Please excuse my intrusion, but I'm curious:

In what way does this tool differ from Vegas color corrector and color grading?
What are the advantages for the user, or are there only a few special cases?

I9900K, RTX 2080, 32GB RAM, 512Mb M2, 1TB SSD, VEGAS Pro 14-20 (Post), Magix ProX, HitfilmPro
AMD 5900, RTX 3090 TI, 64GB RAM, 1 TB M2 SSD, 4 TB HD, VP 21 Post, VP22

Monitor LG 32UN880; Camera Sony FDR-AX53; Photo Canon EOS, Samsung S22 Ultra

Marco. wrote on 10/16/2019, 12:43 PM

@frmax
If you read all the given posts of this discussion you find what you asked for.

Satevis wrote on 10/16/2019, 1:49 PM

Thanks for answering all this, Marco!

@NickHope I see that Vegas' Bézier editor keeps tangents unlocked after having unlocked them once, so yes, I suppose it would make sense to mimic that behavior.

@frmax If you're looking for a quick summary, there's also the website.

NickHope wrote on 10/16/2019, 11:14 PM

@Satevis Thanks for your reply.

Another thing I am struggling with is simply seeing the curves. It's just much more difficult for me to see them compared to VEGAS' color curves, especially when they are overlayed. Everything is just too dark and similar for my eyes:

So I would like to suggest an alternative white or very pale grey color scheme.

And thirdly, could the tangent handles be colored to match the channel so that we can more easily see which curve they belong to? Or maybe a better solution would be for the tangent lines to be grey, so they don't match the color of the curve itself, but the color of the circles at the end of the tangents could match the curve color.