Could you try the VP benchmark in my signature with the recommended render settings?

Thanks! I'll definitely try it this evening!

...and maybe create a short project that will demonstrate the issue? That really seems painfully slow. When you mention a "technical LUT", what is it?

Are you in 32-bit mode? I also use VEGAS with technical correction LUTs (Leeming LUT) with Sony X-AVC S UHD 24p footage and not that different system specs (Intel CPU, NVIDIA GPU).

Yes, 32-bit floating point, Cine S-gamut to rec lut. The problem is that the GPU can't handle rendering even with simple footage without LUT or color grading. But in the preview window, even in "Good" mode it works perfectly with LUTs and color grading. Only the rendering doesn't work. Any codecs, always 1-2 fps.

Technical LUT is the one that returns from LOG to the REC standard

I assume view transform is off for a lut and not ACES workflow. Let me test it later.

Are you rendering using NVENC?

@Igors-rop If you work in 32bit full and leave Aces turned on, you will experience pretty sever slowdowns if you also use cgp or load any 3D technical or look luts.

The way I work with log-to-rec709 luts with my Zcam and Canon cameras, using manufacturer supplied 64- and 65-point technical 3D luts, is to do my editing in 8bit full and switch to 32bit full for final render for delivery. When switching to 32bit full, I have to turn off Aces View Transform and set Gamma back to 2.222 in project properties.

I put the 3D luts in cgp and do all grading there. My footage is typically 3 cameras set to 4k 10bit hevc mp4 with 1 camera converted externally to 4k 8bit avc mp4. I don't need proxies at all for editing in either 8bit or 32bit mode with vp23 on an 11900k system with a high-end Nvidia gpu. But 8bit is a little brisker previewing and rendering. If you work in 8bit limited, you can switch to 32bit limited more easily, without dealing with turning off Aces. But Vegas previews will not match what YouTube does to uploads. Which is why I've switched to full in recent years.

I assume view transform is off for a lut and not ACES workflow. Let me test it later.

Are you rendering using NVENC?

Yes, I always use the NVENC codec.

@Igors-rop If you work in 32bit full and leave Aces turned on, you will experience pretty sever slowdowns if you also use cgp or load any 3D technical or look luts.

The way I work with log-to-rec709 luts with my Zcam and Canon cameras, using manufacturer supplied 64- and 65-point technical 3D luts, is to do my editing in 8bit full and switch to 32bit full for final render for delivery. When switching to 32bit full, I have to turn off Aces View Transform and set Gamma back to 2.222 in project properties.

I put the 3D luts in cgp and do all grading there. My footage is typically 3 cameras set to 4k 10bit hevc mp4 with 1 camera converted externally to 4k 8bit avc mp4. I don't need proxies at all for editing in either 8bit or 32bit mode with vp23 on an 11900k system with a high-end Nvidia gpu. But 8bit is a little brisker previewing and rendering. If you work in 8bit limited, you can switch to 32bit limited more easily, without dealing with turning off Aces. But Vegas previews will not match what YouTube does to uploads. Which is why I've switched to full in recent years.

Your footage processing technology is interesting, and I'll try to use the tips you gave. But first, I need to start rendering via the GPU. When I start the rendering and monitor the processes in the task manager's performance window, I see the CPU load at 20-30 percent, memory at 60-80, and no GPU load. So, it's not participating in the process, and I can't understand why or what else can be done.

If you click on the GPU you should see activity under encode.

Just to compare apples and apples can you try the VP benchmark in my signature with an 8 bit project, follow the render settings for NVENC and report your times? If the GPU isn't working at all that will quickly become clear.