Blackmagic Forum

I upgraded from 16 to 18 today. Renders in H.264 are fine. If I try to render in H.265 in either Quicktime or MP4 I get Cannot find appropriate codec for encoding the video frame. Does not matter if I use old projects or make a new project - same message.

GPU is an NVIDIA GE Force GT 710.

Any ideas? The graphics card is fairly low end so I'm wondering if that's the issue? What would happen if I remove the card entirely? I also have Premiere Pro and that renders in H.265 no problem.

Thanks all.

It's a weird glitch that happens every once and a while for me. What I did to fix it was switch the latency method of encoding. Play around with those settings and it might work. And even if you switch it back after changing it it might work—like I said, it's a weird inconsistent glitch.

Sent from my motorola razr using Tapatalk

Thanks Bryan - not sure what you mean exactly by switch the latency method of encoding?

Evidently it was my cheap graphics card that could not handle the codec. I removed it and can now render H.265 with the CPU. It is taking forever but at least I'll end up with much smaller files than with H.264.

Open to other ideas if anyone has any?

Try with your card again and render out of DR as Cineform or DNxHR.
Then do the final encoding with HandBrake.

Certainly seems like a lot of H.264/5 problems recently. Even more on the Subreddit.

I recommend using DNxHR HQ instead. It is clearly much better supported by BM.

tspence wrote:The graphics card is fairly low end so I'm wondering if that's the issue?

You should most definitely have a plan to upgrade ASAP.

For what it's worth, I am still encountering this bug. Saving the project and restarting Resolve fixes the problem and allows me to render with the same settings for which I get "Cannot find appropriate codec" before the restart. So if all else fails, turn it off and on again.

Ran into this bug. Deleted the export. Recreated it exactly the same using the same preset and it worked.

(RTX 3090 so definitely not low memory)

Hi there, running into the sam issue after switching from 18.6 to 19.03 and 19.1. aswell.
Using an RTX 4090.
Exporting to handbreak works, but it´s sometimes a pain if you just want to do a quick render.
Re installed Resolve but it did not change anything.
Realized that I alos can´t find resolve under supported programs at the nvidia app.
Any ideas?
Thanks and berst regards

Had the same problem. Switched encoder to native and all is well.

Has someone found an actual solution? Upgraded several machines, and just one has this problem. With any kind of H264 with any kind of source.
Obviously the native works, but the extra time is not acceptable in our production environment.
Upgraded, downgraded, sidegraded drivers, clean isntalled them, reinstalled davinci.
Failing both on 19.1.2 and 19.1.3.
Other softwares that use hardware accelelrated encoding have no problem.
Support has not answered my support request. (Sent 10 days ago)

Has someone found an actual solution? Upgraded several machines, and just one has this problem. With any kind of H264 with any kind of source.
Obviously the native works, but the extra time is not acceptable in our production environment.
Upgraded, downgraded, sidegraded drivers, clean isntalled them, reinstalled davinci.
Failing both on 19.1.2 and 19.1.3.
Other softwares that use hardware accelelrated encoding have no problem.
Support has not answered my support request. (Sent 10 days ago)

Could be this:
Timecode in MP4
MP4 is generally not safe for timecode (TC in short), since that is not cleanly standardised, while TC in MOV is.

The Issue:
Apple recommends that developers just borrow the concept from QuickTime clips (MOV). So there can be some sources which have it, but you should see that TC track then with tools like MediaInfo (free). It will be shown on the second tab as "Other", type "Time code" (scroll down), but this is rare. If that doesn't exist, you've already got a problem.

Some software may still show you one they got from the custom metadata, but then you should see something plausible for it. DR, for example, will show something different from all zeroes. If any program is showing all zeroes for TC, there is none and the software just starts counting. Very bad! You should never touch that clip again after editing it in, under all circumstances, and you can forget round tripping to other NLE software.

Solutions:
1) Our dear forum colleague Marc Wielage, who is a seasoned and very kind professional, recommends converting it into a high-quality mezzanine codec like ProRes, DNxHR, or Cineform. Converters like Shutter Encoder (donationware) can add TC in the process, derived from the creation time of the clip. That is very sane advice, since you won't only get TC that even roughly tells you the recording time, but also a clip that's easy on your machine.
2) This applies if you are storage space challenged, but your machine is good at decoding the respective GOP codec in that MP4. Then you can instead re-wrap the clip into MOV, while adding TC in the same way. Shutter Encoder is your friend for this too, and it's a fast and lossless process.

If neither of these has been done before starting to edit, good luck!

Hi!
I must be misunderstanding your message or there is a misunderstading.

1) I have absolutely no problem at reading any kind of file that Resolve usually supports.
2) I am aware of the possibility or rendering and intermediate master file and then use a third party software to convert to the intended codec

but!

a) I am unable to render H265 or H264 files, no matter the wrapper, using the hardware encoding. Being it faster, and to be honest much better picture quality, and vastly more available settings than the native option. Also due to the sometimes considerable amount of files we generate the added time of using the native encoding, and lowered quality is not an option
b) No, for time reason, for workflow reason, and storage reasons (we would end up creating TB and TB of mezzanines) going through a mezzanine to another software is not an option
c) Doesn't seems like too much to ask from Resolve to be able to render out the most commonly used codec.

I was assuming MP4 as a source too, with which I have seen that message when rendering.
If that's not the case, I have no solution. Both codecs encode without a problem and very fast here.

No, the source is of any type you can imagine.

For me it works fine on 11 computers out of 12.

Sounds like number 12 needs a fresh install, or it has defective hardware.

Just encountered the same problem.
Source: Pocket 6K braw
Export: NVIDIA h.264

I don't think the GPU is the problem (4090).
Restarting Resolve and re-queueing the render jobs solved it for me. Strange.

Hi i have the same problem... but not with all resolutions.

Footage shot with cinema camera 6k | Open Gate | Braw.

I wanted to export it at 6048x2520 h.264 and i get the message, "Cannot Find Appropriate Codec" etc.

When exporting on anything lower it works fine.

graphics card 4090

That seems to be a VRAM overload. Try to observe with GPU-Z.

Uli Plank wrote:That seems to be a VRAM overload. Try to observe with GPU-Z.

On what page in GPU-Z should i look?

Hello,

I wanted to add something to this conversation.

I installed Davinci Resolve on a different PC that is Intel ARC based, alongside my usual workstation which is AMD Ryzen/NVIDIA based.

So here the exact same error appears. No H264 or H265 encoder works.

It seems there is a bug in the Intel based encoders. So Intel QuickSync. Or also a bug with OpenCL.
The VP1, though, works perfectly and also very fast on the ARC 770 card.

It seems like Blackmagic is so focused on Mac/ARM now...

I really would appreciate that this is getting fixed, because i have a very small Dell Optiplex that could be used for Davinci Resolve then....

Regards!

GPU-Z is not part of Resolve. You will find it here. https://www.techpowerup.com/download/techpowerup-gpu-z/

I double checked the log files:

Clearly supports all codecs:

Code: Select all

[0x0000153c] | IO                   | INFO  | 2025-02-14 17:51:42,455 | Intel QuickSync decodes AV1 up to profile 2 level 6.3 [16384 x 16384]
[0x0000153c] | IO                   | INFO  | 2025-02-14 17:51:42,455 | Intel QuickSync encode supports AV1 10-bit
[0x0000153c] | IO                   | INFO  | 2025-02-14 17:51:42,455 | Intel QuickSync encode supports AV1 8-bit
[0x0000153c] | IO                   | INFO  | 2025-02-14 17:51:42,456 | Employing Intel Decoder: Intel(R) Arc(TM) A770 Graphics (7.9 GB)
[0x0000153c] | IO                   | INFO  | 2025-02-14 17:51:42,557 | Intel QuickSync decodes H264 up to profile 100 level 52
[0x0000153c] | IO                   | INFO  | 2025-02-14 17:51:42,589 | Intel QuickSync encode supports H264 420 8-bit
[0x0000153c] | IO                   | INFO  | 2025-02-14 17:51:42,591 | Intel QuickSync decodes HEVC up to profile 4 level 62 [8192 x 4320] 12-bit 444-chroma
[0x0000153c] | IO                   | INFO  | 2025-02-14 17:51:42,615 | Intel QuickSync encode supports HEVC 420 8-bit
[0x0000153c] | IO                   | INFO  | 2025-02-14 17:51:42,634 | Intel QuickSync encode supports HEVC 420 10-bit
[0x0000153c] | IO                   | INFO  | 2025-02-14 17:51:42,653 | Intel QuickSync encode supports HEVC 422 8-bit
[0x0000153c] | IO                   | INFO  | 2025-02-14 17:51:42,671 | Intel QuickSync encode supports HEVC 422 10-bit
[0x0000153c] | IO                   | INFO  | 2025-02-14 17:51:42,711 | Intel QuickSync encode supports HEVC 444 8-bit
[0x0000153c] | IO                   | INFO  | 2025-02-14 17:51:42,733 | Intel QuickSync encode supports HEVC 444 10-bit
[0x0000153c] | IO                   | INFO  | 2025-02-14 17:51:42,808 | IO codec library load completed in 7354 ms.


then later when trying to encode:

Code: Select all

[0x0000278c] | IO                   | ERROR | 2025-02-14 17:58:56,389 | IOAMFCodec cannot be initialized with property successfully
[0x000022d4] | IO                   | ERROR | 2025-02-14 17:59:02,050 | QuickSyncEnc EncodeInit failed: -15
[0x000022d4] | IO                   | ERROR | 2025-02-14 17:59:02,186 | Failed to create encoder
[0x000022d4] | Task                 | ERROR | 2025-02-14 17:59:02,186 | Error occured during recording of C:\Users\admin\Videos\H264_ARC_Test_UHD1.mp4 : Cannot find appropriate codec for encoding the video frame.



So it seems to be a QuickSync issue.

I've been a long time lurker and joined because of this very issue. What I found worked for me was switching from H.264 to H.265. This is because I was trying to render a 6K video and, according to Google, ...

"The maximum resolution for H.264 video is 4096 x 2160, or 2160 x 4096 pixels. This makes it possible to use H.264 for HD, Full HD, and Ultra High Definition (UHD) video."

"The maximum resolution for H.265 (High Efficiency Video Coding) is 8192 x 4320 pixels, which is 8K UHD. H.265 is a video compression standard that's designed to handle higher resolutions more efficiently than H.264."

I hope this helps fix the issue for others.
Cheers!

Correct. You can go higher with ffmpeg, but that outside of spec, and not supported by hardware.

Hello, I was able to fix this issue!

According to this article:
https://www.intel.com/content/www/us/en ... phics.html

The graphics driver needs to be removed in safe mode with the utility "DDU".
Then installed fresh and after reboot I was able to use all hardware accelerated H265 codecs!
(H264 still does not work with Quick Sync)

AV1 works too.

Hope this is helpful to some others.

Best Regards!

I tried deleting the graphics card driver (RTX 4090) and reinstalling it, also just about everything else, using Native for rendering seems to make larger video files than needed.

I've got this problem as well after moving up to v20 Build 38. I had to upgrade the NVidia Driver to 576.02 on my 2080Ti.
Now I can't export any H264 or H265 using the NVidia encoder.
Works OK if set to Native.

The log says:
[0x00002d34] | IO | ERROR | 2025-05-23 12:38:41,164 | NVENC m_EncodeAPI.nvEncOpenEncodeSessionEx(&encodeSessionExParams, &m_pEncodeSession) return: 15 => EncodeAPI Internal Error.
[0x00002d34] | IO | ERROR | 2025-05-23 12:38:41,164 | Nvidia codec cannot be initialized with property successfully
[0x00002d34] | IO | ERROR | 2025-05-23 12:38:41,164 | Failed to create encoder
[0x00002d34] | Task | ERROR | 2025-05-23 12:38:41,164 | Error occured during recording of H:\EXPORTS\Ep1 Prores Synced Cut 1.mov : Cannot find appropriate codec for encoding the video frame.

Ignore this post

Here's another good reason not to use "Native" encoder in Davinci when rendering:
When choosing "Native" encoding, the CPU handles the encoding process, which can be advantageous for certain codecs and file formats. However, this can sometimes lead to longer render times compared to using a dedicated GPU encoder (like NVENC or AMD hardware acceleration).

@Nick: What's the resolution and frame rate selected on the Deliver page settings?

Standard HD 1080 25p
Either QT H264 or just MP4 H264 both cause the error.
Was fine on the same machine with v19 and the older NVidia driver.

For the record, my computer,
CPU = AMD Ryzen 9 9950X 16-Core Processor 4.30 GHz
DDR5 RAM - 64.0 GB (61.6 GB usable)
Mother Board – Gigabyte X870E AORUS ELITE
GPU = NVIDIA GeForce RTX 4090

Also, Davinci allowed rendering with my Graphics card until I updated to V20, now it would appear that I'm only able to render using my CPU.

Here's my final fix after trying several other solutions, I purchased codecs from Main Concept. After installation the codecs appear in Davinci Resolve and by using the Main Concept MP4 codec, the first image shows the graphics card working instead of the CPU while using H.265. The second image shows the Main concept codec selected and the GPU at rest.
I hope this helps someone who needs a fix. (At a price)

https://www.mainconcept.com/blackmagic-plugins

@Nick: Testing with an RTX 2070 Super and NVIDIA driver 576.02, I have no issues rendering H.264 1080/25P QuickTime and MP4 files, using both Auto and NVIDIA modes, using Resolve Studio 20 beta 3.

Please send a Resolve diagnostics log and a Windows System Information .NFO file, generated after a render failure. And a project export .drp of the project.

Thanks Dwaine will get those to you asap. I've just upgraded to v20 build 49 and getting the same issue.

Dwaine Maggart wrote:@Nick: Testing with an RTX 2070 Super and NVIDIA driver 576.02, I have no issues rendering H.264 1080/25P QuickTime and MP4 files, using both Auto and NVIDIA modes, using Resolve Studio 20 beta 3.

Please send a Resolve diagnostics log and a Windows System Information .NFO file, generated after a render failure. And a project export .drp of the project.

Hi @Dwaine Here are the logs + NFO + a Test project I created new in v20 + my Export pre-set.
https://drive.google.com/file/d/1Je3k08FBI-tP5KIU3wfLIUgRbIaNkfhD/view?usp=sharing

I created a new project in v20 and got the same problem using my preset. Also tried the Default YouTube, Vimeo or any of the Defaults that use H264.

Thanks for looking into this.
Nick

Your project renders H.264 and H.265 using the NVIDIA encoder on my RTX2070 Super system with Resolve 20.

Your log shows that the NVENC encoder is not happy with what it's seeing, but I don't know why.

I need to see your System Information in the form of a .NFO file, not a .TXT file. Open System Information and do a File - Save, not a File - Export. A File - Save should create a .NFO file.

Another suggestion: Since this seems like it has to be an NVIDIA driver related issue (unless your GPU has some weird hardware issue), reinstall the 576.52 driver, but when you run the driver installer, instead of Express install, select Custom, then select to do a Clean install. See if that changes anything.

And if that doesn't change anything, then use the DDU app to totally remove all the NVIDIA driver components, and then run the driver installer again.

This link describes how to get and use DDU. This was in reference to removing an Intel GPU driver, but the process is the same. Just select NVIDIA GPU instead of Intel:

viewtopic.php?f=21&t=119852&hilit=%2Bddu#p659861

Thanks @Dwaine I will try that.
In the mean time here is the NFO file.
https://drive.google.com/file/d/1bNXZEg ... sp=sharing

Did a full DDU uninstall of the NVIdia Driver and then reinstalled the NVidia Studio v 576.52
plus I did a clean reinstall of Resolve 20 but I am still getting the same error.

Seen in another thread that installed MainConcept plugins could be the problem.
I had MainConcept codecs installed. So uninstalled them.

Problem solved.

It seems these mainconcept plugins have caused problems before.
viewtopic.php?f=21&t=206148

Ah, Main Concept. Good to know. Thanks for the update!

Your Main Concept .dll's are dated 03/09/2024. I wonder if there is a newer version that does not cause this issue? Do you know what version of Main Concept you had installed?

Looking at the other thread you linked to (which i see I was involved with) that users logs had lots of Main Concept errors in them. Your logs had none of that, or it might have provided a clue sooner. I don't know if the difference relates to v19 vs v20, or maybe it depends on the Main Concept version.

Hello i am having the same issue and i don't have the Main Concept plugin and i have DDU'd and clean installed my drivers and davinci twice already and still no solution.

These are the logs+NFO+project file

https://drive.google.com/file/d/1GyGVHp ... sp=sharing, https://drive.google.com/file/d/1LVnxvG ... sp=sharing, https://drive.google.com/file/d/1QAr8SJ ... sp=sharing

Your Google Drive links require access credentials. Make them open links and I'll take a look on Monday.

Done thanks in advance see you Monday

Dwaine Maggart wrote:Ah, Main Concept. Good to know. Thanks for the update!

Your Main Concept .dll's are dated 03/09/2024. I wonder if there is a newer version that does not cause this issue? Do you know what version of Main Concept you had installed?

Looking at the other thread you linked to (which i see I was involved with) that users logs had lots of Main Concept errors in them. Your logs had none of that, or it might have provided a clue sooner. I don't know if the difference relates to v19 vs v20, or maybe it depends on the Main Concept version.

Can't remember which version and have deleted now but the Main Concept site has a v19 and a v20beta version of the plugin so I suspect the 19 version causes the problems with v20. I don't need it ant the moment so am not going to tempt fate by installing the new version!

Thanks for your help @Dwaine

@Michael: I've tested your project on an RTX3000 equipped Win11 PC in free Resolve 20 with the NVIDIA 576.52 driver and no issues rendering with the Deliver page settings in your project.

Your NFO file indicates you've got an HD display connected to the onboard graphics port, in addition to the 2560x1440 display connected to the RTX4080.

Resolve does not like having displays on multiple GPUs. If you disconnect the display from the onboard graphics port, does that make the issue go away?