Disabling GPU Aceleration is worth a try.

Maybe this helps (Thread about LUT not working in VP16 in 2019)

Marco. wrote on 8/13/2019, 11:59 AM

Meanwhile what I found out:

Your LUT which doesn't work in VP17 seems to be a 256x256x256 3D LUT. This LUT size usually is not used in video production but is meant for either calibration of digital to film conversion or for highest quality large size photo prints.
For video production with the use of interpolated 3D LUTs, sizes between 17x17x17 and 64x64x64 are common while the 64 flavor of it should be more than enough for 12 bit video used in float point projects with high quality demands. But even 128x128x128 3D LUTs work fine in Vegas Pro 17. This (128) then might be the limit in Vegas Pro 17.

For your particular case it means you should either select a different LUT size for your LUT export out of Photoshop where I'd go for something between 32 and 64 (my guess is the Vegas Pro exported LUTs are 36x36x36). Or use a LUT converter to shrink your given 256 LUT to something between 32 and 64.
Even size values below 32 should be fine if you like the result. The lower the LUT size is, the better the playback and render performance in Vegas Pro will be (and another reason I would not use LUT sizes above 64).

Last changed by Marco. on 8/13/2019, 1:22 PM, changed a total of 4 times.

J-V I have a Studio laptop. So the drivers "supposed" to be a studio version. At least that's what it was when I opened the box about 6 months ago. The current driver is 425.45. The Nvidia control panel does not indicate Gaming or studio. So I'm now wondering if there's an update that would have altered my settings toward gaming. I don't game on my workstation. Strictly video editing. How can I dig deeper into what you're suggesting? Thanks

Disabling GPU Aceleration is worth a try.

Maybe this helps (Thread about LUT not working in VP16 in 2019)

Marco. wrote on 8/13/2019, 11:59 AM

Meanwhile what I found out:

Your LUT which doesn't work in VP17 seems to be a 256x256x256 3D LUT. This LUT size usually is not used in video production but is meant for either calibration of digital to film conversion or for highest quality large size photo prints.
For video production with the use of interpolated 3D LUTs, sizes between 17x17x17 and 64x64x64 are common while the 64 flavor of it should be more than enough for 12 bit video used in float point projects with high quality demands. But even 128x128x128 3D LUTs work fine in Vegas Pro 17. This (128) then might be the limit in Vegas Pro 17.

For your particular case it means you should either select a different LUT size for your LUT export out of Photoshop where I'd go for something between 32 and 64 (my guess is the Vegas Pro exported LUTs are 36x36x36). Or use a LUT converter to shrink your given 256 LUT to something between 32 and 64.
Even size values below 32 should be fine if you like the result. The lower the LUT size is, the better the playback and render performance in Vegas Pro will be (and another reason I would not use LUT sizes above 64).

Last changed by Marco. on 8/13/2019, 1:22 PM, changed a total of 4 times.

I'm going to try that. But I hope I can back to its original performance. Something changed. The 8/13 post is a nugget I'm going to look into. The LUT's I'm using, is derived directly from Canon for my camera, but I never explored the details highlighted, to see how's it's impacting my system's performance.

J-V I have a Studio laptop. So the drivers "supposed" to be a studio version. At least that's what it was when I opened the box about 6 months ago. The current driver is 425.45. The Nvidia control panel does not indicate Gaming or studio

Not true and you are using a gamedriver, not the best for the use with Vegas software

How can I dig deeper into what you're suggesting? Thanks

I did it already for you. This is what you have to search for

and this is the result

 

If you want to use it do a "clean install".

 

Wow! Thanks!

Could this have changed with regular updates?

I've had to do a lot of streaming from my laptop for meetings. Maybe the new streaming software pulled the gaming driver into play?

As I mentioned, The LUT's package is not a new thing for me or my machine. But the sudden performance issues this past month were catching my attention, and now when I had a project scheduled to render is when I noticed the plugin was crashing Vegas.

I've already downloaded the driver. I'll get under the hood of this thing later this eve. I'll send an update when I have one.

I just wanted to leave an update. The missing or mysteriously replaced Studio driver was the fix. My workflow is somewhat back to normal. I deliberately left using the LUT approach out of this week's production. Still encountering instability overall. It's like walking on ice while in post. The rendering crashes were resolved with the proper drivers in place. I believe the culprit was the "Nvidia Gforce Experience" application which is a separate application to the Nvidia Control Panel. It needs to be left offline completely. It's constantly trying to push gaming updates and drivers.

I'll be digging deeper into the instability issue. The system froze at least 8 times in my last project. It's forced me to be extremely disciplined with my workflow. But it's not what I expected from this new set up.

Pro 17 appears to be hypersensitive. I did not have these challenges with older computers and software combinations.