[VP17] New Colour Correction toolset

AVsupport wrote on 8/15/2019, 1:09 AM

Gratulations on VP17, there's definitely a lot of new updates and improvements under the hood, and I'm sure those pesky bugs will get ironed out during the course of time!

The new Colour Wheels remind a lot of what one sees to 'Resolve' colour grading issues elsewhere. And I'm sure it's a good start to unify all the different plugins into one meaningful spot. however:

I see CPU eating performance only when the tool is used extensively:

pushing my i5-8600 @3.6 from 27% to about 95% load (when correcting 4K XAVC-S on a 1080 timeline) - compare this with ColorFast2 which I can run with nVidia acceleration, which loads the CPU to 55% only, and there's plenty more room to add more FX.

No Input / Output transform options:

These days there's a lot of shooters shooting in various Gamma and Gamut combinations, like CINE and LOG curves. It would be nice to have those options as preset definitions for [Brand] [Gamma] [Gamut] for both Input (shot as) and output (delivery option) available .."see elsewhere".

Currently, I have to use FilmConvertPro to make these conversions happening, but this also forces to a particular Film Color Look that is not always wanted where a 'neutral' conversion is desired. Using CPU intensive LUTs is not always the answer for what could perhaps be a simple choice on a drop-down menu

LOG-behaviour correction

would be nice to expand the toolkit with an ability to make those corrections in a logarithmic manner, to suit a workflow where CINE or LOG source material is used without an input transform option as above..; seen elsewhere as a 'flip switch'

Import / Export option for Colour Curves

take your time making one, and save it for a rainy day ;-) - self explanatory.

Auto-Button for The Lazy

Always a nice starting point when you're rushed for time. For Exposure, Contrast, White Balance. All inclusive. Bang.

Keep up the good work Team!

Comments

fr0sty wrote on 8/15/2019, 1:26 AM

"These days there's a lot of shooters shooting in various Gamma and Gamut combinations, like CINE and LOG curves. It would be nice to have those options as preset definitions for [Brand] [Gamma] [Gamut] for both Input (shot as) and output (delivery option) available .."see elsewhere".

Currently, I have to use FilmConvertPro to make these conversions happening, but this also forces to a particular Film Color Look that is not always wanted where a 'neutral' conversion is desired. Using CPU intensive LUTs is not always the answer for what could perhaps be a simple choice on a drop-down menu"

Right click on media, go to color space, there's a ton of input view transforms there, and the same can be found in render settings when outputting. View transforms at the project level are available in project settings for the preview monitor.

AVsupport wrote on 8/15/2019, 2:25 AM

there's a ton of input view transforms there..

thanks for pointing that our @fr0sty shows how little I know about the intricate functions of VP ;-)

However, I shoot Cine4/ProColour on my A7iii. There's no such view transform, as Gamut and Gamma seem to be coupled in one transform. Also: Is it actually possible to copy/past those transforms to a whole section of clips?

Again, I think these items might be better placed at the 'unified colour grading window'. What's my next best option I wonder? Please do not suggest SLOG on an 8Bit camera. I'm still waiting for A7sIII to solve that pain ..!

Wolfgang S. wrote on 8/15/2019, 4:16 AM

You should try to explore the ACES workflow. Frosty gave you a first hint that you have to tell the system the input color space. The second step is to enable the ACES 1 workflow in the project settings. Including the transformation you go for. Then to adjust the luminance and color settings with the new grading tool. And then to render to your final output format.

Sure, you can copy paste the color settings like other event attributes.

Wolfgang S. wrote on 8/15/2019, 4:22 AM

However, I think that there is no transformation for your Cine profiles. If you have LUTs for them (for example to bring that more in line to rec709, then this could be used as an input LUT in the new grading tool. And then do all the adjustments in the new tool what looks more intuitive then Filmconvert too me. Could be done in 8bit too

I would agree with you that slog and 8bit are not a great idea. But that is a limitation of your A7 iii but not of Vegas.

Marco. wrote on 8/15/2019, 4:27 AM

"There's no such view transform"

The "View transform" selection is for adopting your project to your display, not for adopting your source media to your project.
See if there is a "Colorspace" option in the clip properties which fits your needs. But maybe this is what you've already done as you ask for a way to copy this to multiple events. I'm not aware of a given way to do so but it should be possible by scripting.

Wolfgang S. wrote on 8/15/2019, 4:47 AM

For the Cine-profiles you will not find anything in the colorspace settings. Filmconvert may have that very likely, as I know that from other cameras. That is why I would go for a LUT thst could be used as input LUT in the new color grading tool.

Marco. wrote on 8/15/2019, 4:52 AM

So doesn't "Sony - linear - S-Gamut3.Cine" work for the A7iii?

If not I'd also recommend using a LUT instead. A LUT must not be CPU intensive, it depends on the LUT size. In the end the editing performance using a LUT even could better then using an appropriate ACES color space. The LUT can be used in an 8 bit project while the color space adaption needs a float point project.

Wolfgang S. wrote on 8/15/2019, 7:26 AM

Is that really the Cine4 profile of this camera? I do not know that.

AVsupport wrote on 8/15/2019, 7:35 AM

Thanks gents for the contributions, so far I couldn't find a suitable VP transform to deal with Sony Cine4/Pro Colour, whilst Filmconvert does:

And Yes @Marco. I should have said colourspace conversion since it is the input clips that are meant to be converted -in my situation- to 709. And No, I don't think S-Gamut3.Cine is the suitable answer, sorry.

And No @Wolfgang S. ACES workflow in my situation makes no sense, 8 Bit camera with 709 output, I'll just be burning 32bit float data and thus CPU GPU power unnecessarily. Since I should be able to do all I want in standard settings (see: Filmconvert)

Do the LUT conversions use CPU also or are those GPU accelerated..?

further reading re Sony Mirrorless picture profiles:

https://helpguide.sony.net/ilc/1720/v1/en/contents/TP0001661955.html

Wolfgang S. wrote on 8/15/2019, 8:28 AM

The LUT plugin is GPU accelerated too now for a long time. Right, ACES does not allow an 8bit workflow. So maybe Filmconvert is the better choice, especially if you run 8bit footage only.