HEVC Native Export uses NVIDIA Encoder / Codec not found

We are trying to export with the native Encoder in HEVC, but it seems that the NVIDIA Encoder still is used, which can be monitored with the Windows task manager. Using H264 in native mode works without the NVIDIA Encoder being used.

The question is, is "Native" is the same as "CPU" or can "Native" also use the hardware Encoder if available ? Is this a normal behavior ?

In addition to this switching between native and NVIDIA Encoder back and forth causes an error message to appear saying "Cannot find appropriate Codec" . This can be reproduced with the H265 Master Export preset. Export in Native first, then switch to NVIDIA and start encoding. After restart of Resolve NVIDIA Export works again.

The NVIDIA GPU is a RTX 5060 Ti 16GB using the 576.52 Studio Driver.

(I think I have this right.)

Native means CPU encoding.

Rendering is always done on the GPU.

(I think I have this right.)

Native means CPU encoding.

Rendering is always done on the GPU.

so the conclusion would be, that there is something wrong while using Native Encoding in H265, since the GPU Encoder is always used to some capacity, while in H264 no GPU Encoder is used.

I think the actual encoding is done with the CPU, but the CPU Encoder is somehow activated and not properly closed, which then causes any following NVIDIA Encoding processes to fail.

That's a good question. I'm seeing the same with Studio 20.0b4 (Build 48) for Windows using a 12 GB RTX 3060.

Native does use the GPU Encoder for H.265.

Weird.

That's a good question. I'm seeing the same with Studio 20.0b4 (Build 48) for Windows using a 12 GB RTX 3060.

Native does use the GPU Encoder for H.265.

Weird.

Can you check with the latest version, that once you've done an export with the Native settings, just switching back to NVDIA (not Auto) and then directly starting another export causes the export to fail ?

[Shrinivas Ramani]

Hi all

Native just means Resolve delegates to the operating system's native API. Depending on the OS, it may decide to implement a software-powered or hardware-accelerated version for different codecs. This is subject to licensing, performance limitations and hardware utilisation the operating system chooses to implement.

In the Studio version, DaVinci Resolve can additionally leverage the GPU's API to accelerate decodes and encodes.

Regards
Shrinivas

Thanks for the clarification, Shrinivas.

Hi all

Native just means Resolve delegates to the operating system's native API. Depending on the OS, it may decide to implement a software-powered or hardware-accelerated version for different codecs. This is subject to licensing, performance limitations and hardware utilisation the operating system chooses to implement.

In the Studio version, DaVinci Resolve can additionally leverage the GPU's API to accelerate decodes and encodes.

Regards
Shrinivas

thanks a lot for the clarification. Now the question would be, how to control the encoding method within Windows. I guess there must be some configuration or setup somewhere, how the OS decides which software or hardware codec is being used. Currently there are some restrictions in v19 or Resolve while exporting H265, since there is no 4:2:2 option, neither using Native or NVIDIA. The only way for us right now is using NVIDIA at 10 Bit 4:4:4 to preserve maximum quality with a reasonable file size.

Software encoding, e.g. using x265 is far superior in terms of quality compared to any NVIDIA hardware encoder, especially in dark grainy areas, where NVDIA almost everytime fails to encode without blocky artefacts.

The other issue / question is, if the reported bug "codec not found" after switching von Native to NVIDIA can be solved in v20 of Resolve.