VisionColor LUT Plugin NOT loading in VEGAS Pro 21 (Build 208)

TonyWDA wrote on 1/5/2024, 10:44 AM

I keep getting this error every time I try loading VisionColor's LUT plugin:

Problem Description
Application Name: VEGAS Pro
Application Version: Version 21.0 (Build 208)
Problem: Unmanaged Exception (0xc00000fd)
Fault Module: C:\WINDOWS\SYSTEM32\ntdll.dll
Fault Address: 0x00007FFD36CCC69E
Fault Offset: 0x000000000003C69E

Fault Process Details
Process Path: C:\Program Files\VEGAS\VEGAS Pro 21.0\vegas210.exe
Process Version: Version 21.0 (Build 208)
Process Description: VEGAS Pro
Process Image Date: 2023-11-30 (Thu Nov 30) 11:19:46

I've tried everything I thought might be the culprit. Rolling back the NVIDIA Studio Driver, turning off GPU acceleration, turning down Dynamic RAM Preview Max— nothing's worked.

Here's the funny thing: I can access the plugin with no issues when I open projects I've edited in VEGAS Pro 19— that use the VisionColor LUT plugin— in VEGAS Pro 21. It's when I try applying the plugin to an event in a new project created in VEGAS Pro 21 that the software crashes on me.

And yes, before anyone says it, I know VEGAS Pro comes with its own LUT Filter, but VisionColor's almost always gives me more accurate results with LUTs I create myself, so I kind of need this plugin to work for my new projects to move forward.

Any ideas as to what might be causing this error?

-------------------------------------------------------------------

Machine Specs:

CPU: Intel(R) Core(TM) i9-10900K CPU @ 3.70GHz
GPU: NVIDIA GeForce RTX 3080 (10GB)
RAM: 64.0 GB
OS: Windows 11 Pro (64 bit)

Comments

andyrpsmith wrote on 1/5/2024, 11:34 AM

You probably need to contact Vision Colour support.

mark-y wrote on 1/5/2024, 1:09 PM

By typing Visioncolor into a forum search, you will get 104 results, some of them applicable to your question.

TonyWDA wrote on 1/5/2024, 3:14 PM

By typing Visioncolor into a forum search, you will get 104 results, some of them applicable to your question.

I combed through every one of those posts before making mine, and not one of them had a solution to my problem. I promise you, I would not have made this post otherwise.

Howard-Vigorita wrote on 1/5/2024, 5:49 PM

I can confirm getting the same error with vp21 on my laptop. But not with vp19 or vp20 on the same machine. Also got the same behavior of getting no error from vp21 if the project was created by vp19 or vp20 with the fx applied there. When I got the vp21 crash, I filled out the crash screen to report it to developers.

Btw, out of curiosity, I took a Canon xf605 clog3 test clip and made a 133 mbps reference clip applying the 65-point official Canon LUT with ffmpeg using tetrahedral interp. Then did ffmpeg quality analysis on 25 mbps hevc clips rendered from Vegas 20 and Vegas 21 alternately using the Vegas Lut Fx and the ColorVision Fx. I had to change the Vegas default to tetrahedral. ColorVision defaults to tetrahedral. Analysis reports all the renders as identical. Oddly, I got lower ssim and psnr readings applying the same Lut in the Color Grading Panel. Not sure what to make of that.

Howard-Vigorita wrote on 1/5/2024, 6:15 PM

Found a workaround to add ColorVision Fx to projects with vp21. Just load the fx with vp19 and then save it as a Filter Package. Thereafter, you can load the saved Filter Package to other versions of Vegas, including vp21, present on the same machine.

Steve_Rhoden wrote on 1/8/2024, 2:17 PM

@TonyWDA The Vegas built in Lut filter is the same implemented version of VisionColor's LUT plugin, with even more added feature..... So to achieve the more accurate result you are speaking of, you however just change the interpolation to Tetrahedral (best).

TonyWDA wrote on 1/8/2024, 9:45 PM

@TonyWDA The Vegas built in Lut filter is the same implemented version of VisionColor's LUT plugin, with even more added feature..... So to achieve the more accurate result you are speaking of, you however just change the interpolation to Tetrahedral (best).

I tried my LUTs through both VC's plugin and the built-in one from VEGAS again, and I've found what you said to be true.

Found a workaround to add ColorVision Fx to projects with vp21. Just load the fx with vp19 and then save it as a Filter Package. Thereafter, you can load the saved Filter Package to other versions of Vegas, including vp21, present on the same machine.

What worked for me was applying the effect to an event in VEGAS Pro 19 first, saving the project, opening it in Pro 21, then copying the event attributes and pasting it to the video(s) in the timeline.