Weird behavior after updating my Windows 10 to "Creators Update"

Cosmin_Gurau wrote on 5/14/2017, 11:14 PM

I also just installed Windows 10 "Creators Update". I'm reading here that there are others with various problems with the same windows update, but I just had to update to the latest version, I can't risk running into the now rampant ransomware... 😅

Well, although VEGAS 14 (252) seems to work, I came upon a very weird situation. For now, the main thing that seems to be affected is the LEVELS module in conjunction with BORIS FX (the latest version), which seems to give off a different result than before the update. I basically used a Linear Luma Key with a post blur of 12.5 to separate the highlights and then superimposed them on my already graded and contrasty footage, in order to bring back a very controlled amount of highlight detail back. A very uncommon and probably stupid method (it certainly is computationally expensive), but it is what it is. I would also use a LEVELS module after the BORIS FX one, to make the details more contrasty.

But basically this http://i.pi.gy/NQlE.png became this http://i.pi.gy/P8l5.png, upon opening the unchanged project after the aforementioned big ass Windows update. I repeat. I did not change A THING. Now, I'm not even sure if things were operating normally BEFORE or NOW. I remember that turning up the Input start over 0.700 would induce a similar effect to the now ruined image. But keeping it at 0.600 provided just the right amount of contrast in the highlight detail. Now, 0.600 is WAY too much, and it only looks acceptable at 0.100, or even less. And they are nowhere near as contrasty... Interestingly enough, if I set the Vegas project pixel format to 32bit (video levels/full range with 2.222 gamma), I get very close results to the initial image... ever slightly less contrasty than the original result - so not identical, but still - a huge difference. I also noticed -omg- that my GTX1080 is missing from the GPU acceletation dropdown menu, along with my GTX680. Now I simply have "None"...

I know this is a lot to wrap one's head around, but do you guys have any idea why this might be happening? What exactly could have changed in the Windows update to create this difference? I am so very pressed to finish this project...😟

Comments

NickHope wrote on 5/15/2017, 12:17 AM

I suggest you uninstall your display driver with this: http://www.guru3d.com/files-details/display-driver-uninstaller-download.html

Then install the latest driver from here: http://www.nvidia.com/Download/index.aspx

Then check your video color settings in the Nvidia control panel. You'll probably have a choice of dynamic range, either 0-155 or 16-235.

If you can't get it working right, and you have an image of Windows before the Creators update, you could install that and manually install the Microsoft patches to protect you from WannaCrypt. But you'd probably have to turn the Windows Update service off to stop the Creators update being installed again automatically afterwards. In my opinion it's better to keep the Creators update, keep Windows Updates on, and do everything you can to get it working right.

Cosmin_Gurau wrote on 5/15/2017, 12:27 AM

Haha, thanks Nick, I was just writing this:

UPDATE: I have actually found the culprit. It seems that the latest Windows update messed with the Nvidia driver really bad. I actually did install the latest driver, but it seems it was not enough. Only upon doing a CLEAN installation of the driver, the GPU acceleration of effects came back to life, and both my cards were recognized by VEGAS once more. And now my project looks correct. And now for the really-really interesting part. It seems that enabling GPU acceleration changes the way VEGAS does its compositing, making it look like the pixel format was changed to 32 (video levels). Did you guys know this?