VP 17 452 - Color Curves BUG

pierre-k wrote on 5/27/2020, 10:54 AM

Sorry, but this really isn't a professional approach from the Vegas team!
You are testing the patience of loyal users again.


In version 387, a white balance error occurred in Color Curves and Color Grade.
The bug continued in version 421.

In the current version 452, the bug is finally fixed, but another bug has occurred in Color Curves.

Description:
If I Apply Color curves FX to an event and leave the Color Ballance option, it will switch to Color Levels when the calculation button is pressed. So I have to switch to Color Balance again and press the calculation again.

Similar contrast issue:


With this lax approach, you unnecessarily prolong the repair time.
Instead of such simple repairs lasting a month, they take years.


I repeat - The team needs more capable beta testers!

I also tried the fixed dropper in the White Balance plugin, which works again, but this plugin is still a mystery to me. I don't understand its purpose. I don't think anyone uses it.

I also remind you of an uncorrected bug with Warp Flow.

https://www.vegascreativesoftware.info/us/forum/vp17-421-warp-flow-transition-bug--120474/

 

 

Comments

michael-harrison wrote on 5/27/2020, 10:59 AM

@pierre-k

The dropper should allow you to select pixels in your image that are white IRL. Ideally you'd use a white balance target to make sure the balance is correct in post.

I'd used WB in VP 15 but found that it wasn't working correctly in 17. I haven't tested it in 452 yet.

System 1:

Windows 10
i9-10850K 10 Core
128.0G RAM
Nvidia GTX 1660 Studio [most likely latest]
Resolution        1920 x 1080 x 60 hertz
Video Memory 6G GDDR5

 

System 2:

Lenovo Yoga 720
Core i7-7700 2.8Ghz quad core, 8 logical
16G ram
Intel HD 630 gpu
Nvidia GTX 1050 gpu

 

Future System 3:

Processor        Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz, 3192 Mhz, 6 Core(s), 12 Logical Processor(s)
BaseBoard Product        ROG STRIX Z390-E GAMING
Installed Physical Memory (RAM)        48.0 GB

alifftudm95 wrote on 5/27/2020, 11:02 AM

The update notifier is also buggy. I downloaded all 3 VEGAS POST main component and it prompt back to download VP17 update all over again. wasted 30min waiting. Having this issue since VP16

Editor and Colorist (Kinda) from Malaysia

MYPOST Member

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)

 

 

 

RogerS wrote on 5/27/2020, 11:15 AM

What's your issue with the WB Fx? I use it. If you drag the mouse you can create a box in the preview window to average a neutral area. Colorfast Fx also has similar functionality. It does save between sessions now and no longer has 0 amount.

Custom PC (2022) Intel i5-13600K with UHD 770 iGPU with 31.0.101.4091 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 (driver 31.0.101.2115), dual internal SSD (256GB; 1TB), Windows 10 64 bit

Vegas 19.648
Vegas 20.270

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

Musicvid wrote on 5/27/2020, 11:21 AM

Pierre, can you try it without the judgment, please?

pierre-k wrote on 5/27/2020, 11:23 AM

What's your issue with the WB Fx? I use it. If you drag the mouse you can create a box in the preview window to average a neutral area. Colorfast Fx also has similar functionality. It does save between sessions now and no longer has 0 amount.

WB FX affects the whole image. The event has a red or blue tinge. Works differently than in Color Curves and Color Grade.

Original:

Color Curves FX:

WB FX

pierre-k wrote on 5/27/2020, 11:29 AM

Pierre, can you try it without the judgment, please?

Please believe me, I try hard.
But admit that such mistakes should not happen.
The team is unnecessarily busy. He must constantly return to the old mistakes and create new ones.

NickHope wrote on 5/27/2020, 3:40 PM

I see this behaviour also. Is the following accurate?

When a Color Curves FX is first added, or its Video Event FX window first opened, the Auto Mode always displays "Color Balance", despite a different Auto Mode being set.

RogerS wrote on 5/27/2020, 10:29 PM

For the white balance Fx it works (mostly)

Here's a X-Rite Colorchecker white balance patch shot in daylight with no in-camera WB adjustment


It's a bit off on the scopes

Then I opened White Balance Fx and on my primary monitor used the mouse to drag a rectangle on this patch (so it samples more than one pixel)

The resulting white balance is good. Note if you aren't happy with the WB and try again I recommend reverting the Fx to default between attempts- sometimes if you keep clicking the eyedropper it has wild color shifts.

With your image it's not trivial to select what's neutral. The paper and walls/ceiling are different hues. You can get the paper to look neutral in the scopes but then the image as a whole looks dead (esp. skin). I recommend augmenting, rather than fighting, the artificial lighting and leave some yellow/green of the room atmosphere. You can do this manually with the temp and tint slider in the Wb control or elsewhere.

Example:

or a bit more neutral- used curves auto levels and then tweaked it for lower contrast and more pleasing color balance.

Last changed by RogerS on 5/27/2020, 10:33 PM, changed a total of 1 times.

Custom PC (2022) Intel i5-13600K with UHD 770 iGPU with 31.0.101.4091 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 (driver 31.0.101.2115), dual internal SSD (256GB; 1TB), Windows 10 64 bit

Vegas 19.648
Vegas 20.270

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

NickHope wrote on 8/4/2020, 12:34 AM

This is fixed in VEGAS Pro 18 build 284.