"Cannot find appropriate codec" - h265 8k

Hi all,
I've been trying to render out an h265 8k HDR file (for playback on a TV). I can render the file to MXF or DNxHR and to (8bit) h264 at the full 8k resolution, but obviously none of those directly suit my requirements.
When I try to export to h265 (in either MP4 or QT wrapper) it consistently comes up with an error: "Render failed as the current clip cannot be processed: Cannot find appropriate codec for encoding the video frame".
This is regardless if I'm rendering from the original timeline (either off the original HEVC files or full-resolution optimized media) or if I'm trying to render off the MXF file.
I can render the same clip to 4K with otherwise identical settings.
The PC is not super-powered but should be up to it: 32GB RAM, 8GB RX5700XT GPU, Windows 10, Resolve studio 17.1 build 24. I've also manually tried setting it to render at 1fps.
Would love to hear a solution (current one is a very slow work around of rendering to DNxHR and then transcoding in Adobe Media Encoder
Thanks

...just a follow up. Tried uninstalling 17 and installing 16.2.8 - still getting an error (this one is "failed to encode the video frame"). Super annoying - would love to get this resolved (excuse the pun!)

I’m afraid your hardware with only 8 GB VRAM doesn’t support the format. You can try and switch off hardware encoding, but it’ll take very long. 8K is quadrupling the needs, definitely comes at a price. Hardware manufacturers love it.
You may need to wait until the miners leave one of the 24 GB GPUs for you to buy.

Thanks Uli,
Is there actually a way to switch 'off' the hardware encoding in Resolve? I'd be happy to wait (at the moment I'm having to render it as an intermediate then re-encode in Adobe ME so render time is not really a concern.
If I select h265 as the format, I'm only given 'AMD' in the encoding drop down - no software/native option?

Thanks Uli,
Is there actually a way to switch 'off' the hardware encoding in Resolve? I'd be happy to wait (at the moment I'm having to render it as an intermediate then re-encode in Adobe ME so render time is not really a concern.
If I select h265 as the format, I'm only given 'AMD' in the encoding drop down - no software/native option?

No.

However there is this confusing slide:

https://i.redd.it/rbko8acbev331.png

It say 8K encode is supported on the left but it's not listed on the right i.e. max is 4K60?

Well, your approach is not that bad, AME is doing decent encodings and DR will not be blocked by the lengthy process.

On the Mac I see this field to switch hardware acceleration off, but that might be different under Windows:

Bildschirmfoto 2021-03-24 um 08.12.25.png

Yep, unfortunately on my PC I don't have the option to turn off hardware encoding so I guess 8k h265 from Resolve is just not going to be an option in the short term for me (until GPU prices come down a bit at least!)
All good, I guess I'll stick with the roundtrip - fortunately 8K HDR in H.265 is a pretty niche client requirement for the moment
Thanks for all your help

I've been working on some high res VR footage in Resolve and trying to get a workflow going. Running into similar issues at the time of render as the footage is 8K non-stereo. I'm using dual 3080 cards on this machine. Hoping to get a stereo workflow at some point but then the footage is 8k x 8k lol.

I'm on a PC, what worked for me was selecting custom under render settings, then MP4 as the format, H.264 as the codec, and then I get the option for Native as the encoder. Any combination with H.265 forced NVIDIA as the only Encoder option and then I get the same error.

Surprisingly, when rendering, the CPU and GPU was all utilized about the same % as a NVIDIA render. Maybe wince my timeline has effects (noise reduction) some loads are still placed on the GPU, not sure.

That's said, I wish the render used more CPU cores. I'm running a 32 core Threadripper and many cores are sitting idle. Maybe Blackmagic will improve that in the future. Ideally I would hit render and 100% of the CPU and GPU would get used.

Well my GPU was working fine on 4k h265 but is messing up with new gpu driver and DR

Well my GPU was working fine on 4k h265 but is messing up with new gpu driver and DR

I often test the "game ready" drivers and the "studio" drivers against each other. Some swear by the studio drivers, I find the game ready to be faster most of the time and stable.

But if you are running into an issue try which ever one you're not currently using as a test. Easy enough to switch back and forth in the GeForce Experience app.

I wish the render used more CPU cores.

Image processing occurs exclusively on the GPU. The CPU is used in some cases for decoding and encoding, but on a Windows system, H.265 is only handled by the GPU.

H.264 can be either.

I wish the render used more CPU cores.

Image processing occurs exclusively on the GPU. The CPU is used in some cases for decoding and encoding, but on a Windows system, H.265 is only handled by the GPU.

H.264 can be either.

Good to know!

Hi,
I am working with 8K on Resolve Studio with sometimes your "GPU Memory is full" Message.
I have 64GB RAM and 8GB VRAM.
If Resolve is "bitchy" I am using Edius X with no problems what so ever for 8K.

No Problem with codec see attached:

Resolve H265 8K.PNG (77.26 KiB) Viewed 20431 times

I just upgraded to 3090's with 24 gigs of VRAM, hoping that solves my memory issues.

Ha, did it solve the issues?

Ha, did it solve the issues?

Yes lol.

…but on a Windows system, H.265 is only handled by the GPU.

The newer Intel CPUs with an iGPU can support that task. Admitted, it's a GPU too, but you should not try to use it for DR's other processes.

I'm posting on this thread because I am getting the same error message after upgrading to DVR Studio 18.6.4. I'm only on a 1920x1080 timeline at 24fps and getting the same error message (see attached). This happened with the H.264 and H.265 codecs. DNxHD and other codecs are working. Is there a big change that 18.6.4 does not support older GPUs? If not, how do I fix this without downgrading DVR Studio to a previous version or getting a new GPU card?

Resolve error-job failed.JPG (31.71 KiB) Viewed 9331 times

You can't fix it any other way than you already found out. Render DNxHR and then encode to your final version. If you send your films to YT and they are short enough, you can leave the transcode to them, they re-compress anyway.

I have had the same issue since I upgraded DR to 18.16.4.
Mac m1pro, 32ram.
But it happens only when I try to "Export Alpha" for QuickTime H265, 4k, 29.97. Everything works without the "Export Alpha" checkbox, but I need this.
IDK how to fix it.

You can't fix it any other way than you already found out. Render DNxHR and then encode to your final version. If you send your films to YT and they are short enough, you can leave the transcode to them, they re-compress anyway.

So they are no longer supporting older GPU? Is that the case? Or is this a bug that will be fixed in future updates? I didn’t find anything about unsupported GPUs for h.264/256 from BMD or here in the forum.

Some older GPUs seem to get stressed when doing rendering and GOP compression at the same time.

So, they are not exactly unsupported, but the software is getting more demanding with every iteration. There's nothing wrong with using an older version of DR. Other than many other manufacturers, BM is not forcing the newest one on you.

Some older GPUs seem to get stressed when doing rendering and GOP compression at the same time.

Thanks Uli. I’m hoping to keep current but budget had me put off some spending. My friend in Northern California has a couple of AMD Radeon RX 6750 XT that he’s not using and will ship them to me when he gets back from the holidays. I hope that will be sufficient and won’t fail to work for the next couple of years more.

I got this problem after updating to 19.0.1!

I have a 4090 video card!

I got this problem after updating to 19.0.1!

I have a 4090 video card!

Same happend to me! Also by uprading to 19.0.1
Simple FHD timeline with FHD footage. --> "Cannot find appropriate codec"
It worked all the time before DR19.0.1

By the way: Intel Quick Sync Renderer in the settings, does the job.

[Dwaine Maggart]

@Nicola: Can you provide more details on exactly what issue you have? And have you updated the NVIDIA driver?

@Nicola: Can you provide more details on exactly what issue you have? And have you updated the NVIDIA driver?

Hi Dwaine,
thanks for taking care. Actually I cannot really give you more details. All of a sudden installing DR 19.0.1, I can't export anything where the NVidia Encoder is involved, whether the output is mp4 or Quicktime.
My installed MainConcept Plugin does the job, no matter what codec - H265, H264, although using the NVidia GPU.

Latest NVidia driver is installed (553.09)
I cannot address the problem to my hardware. Should be on NVidias side or DR.

[Dwaine Maggart]

@Nicola: Please provide a screen shot of the Deliver page Video render settings you are trying to use.

Then also provide the following info:

With a project loaded, so you can access the Resolve Help menu, select the Resolve Help menu, select "Create Diagnostics Log on Desktop"

This will place a Resolve log file named similar to this on your Windows desktop: DaVinci-Resolve-logs-20181228_140434.zip (You may not see the .zip extension if your system is set to hide known extensions).

Then open the Windows System Information app and do a File - Save (Not a File Export), which will generate a .NFO file.

Place both those files on a file sharing site and provide links to the files here. Make sure the links don't require access credentials.

@Nicola: Please provide a screen shot of the Deliver page Video render settings you are trying to use.

Hi Dwaine,

good news! I updated to DR 19.0.3 and the whole issue is completely gone. All codecs and NVidia encoder are working again.

So I asume that the issue was on DR side, since I have nothing else changed.

@Nicola: Please provide a screen shot of the Deliver page Video render settings you are trying to use.

Hi Dwaine,
with DR 20b the above described bug starts all over again.

Just want to let you (BMD) know.

Delete the MainConcept Codec Plugin and the problem resolve.