Studio 17.3 H.265 AMD Codec not found

Hello,

I updated from Studio 17.2 to 17.3 and Delivery is not working anymore.
"Cannot find appropriate codec for encoding the video frame."

- Settings: MP4, H.265, AMD, 1920x1080 HD, 29.97 fps.
- Windows 10 Pro.
- Video card: Radeon VII 16 GB

Thank you for any help or hints to fix this.

[Dwaine Maggart]

Works for me.

These same settings worked for you in 17.2.2?

Send a screen shot of your Deliver page settings.

Then right click on the Windows Desktop and select AMD Radon Software and grab a screen shot of the System tab settings and send that. It should open on the System tab.

And also send a Resolve log, created from the Resolve Help menu: Create Diagnostics Log on Desktop.

Hello Dwaine,

Yes, this is the same settings because I saved a custom delivery profile which I always use without changes. It worked in the previous version.

As for the AMD drivers, I am using stock AMD drivers published by Microsoft. Using the newest drivers was making DR Studio crash very often when delivering and sometimes while working. Going with the AMD drivers from MS fixed all issues and it now works flawlessly since about a year. So, no drivers were updated since that time. A bit slower but stable to work with.

Requested files in attachment. (The error is visible in the log without much detail.)

Thank you very much and best regards.
Alexandre

Hello,

I just installed 17.3.2 and the problem is still there when delivering a project.

“Render Job failed as the current clip could not be processed.”
“Cannot find appropriate codec for encoding the video frame.”

I will install 17.2.2 which can deliver (pun intended).

Thank you for your time and kind help.
Alexandre

[Dwaine Maggart]

On the Deliver page, select the Audio or File tab, instead of the Video tab. Will the render work then?

- Anything that is not H.265 (AMD) will render no problems.
- The moment I select H.265 (AMD) it will not deliver but display the failed message, whatever I try to do, or panel I select (like Audio or File).

Just a post to validate this. I have exact same OS and exact same graphics card and this exact same issue comes and goes for me. I remember that I was able to render successfully H265 .mov after adjusting the latency settings, but like I said, the issue comes and goes, so I am at a lost.

Sent from my motorola razr using Tapatalk

[Dwaine Maggart]

@Alexandre: Did you perform my requested test?

Yes.
- I went to the delivery pane
- I loaded my custom setting
- I then clicked on the “Audio” sub pane
- It failed.

I tested all the other delivery presets (YouTube, Vimeo, Audio only, etc.) and they all work.
- Then I used YouTube (which worked), changed the H.264 to H.265, and it fails.
- I even tried to add to queue, and before rendering change the render setting tab to Audio, and it failed.

Thank you for your kind help looking into this.
Alexandre

[Dwaine Maggart]

As best I can tell, you do not have a current AMD graphics driver installed.

Download the current 21.8.2 Radeon driver from the AMD site Driver Downloads area.

When you run the installer, select the Additional Options menu, then check the Factory Reset option, so it does a clean driver install.

That's the driver I'm using, and your Deliver page settings work for me in 17.3.2.

I installed the latest drivers (only) for the Win10-Radeon-PRO-Software-21.Q3.

D R Studio is now able to deliver in H.265 as in previous versions. Thank you very much for pointing that out, it solved the problem.

Time will tell if D R Studio is stable with these drivers. Over a year ago I had a bad experience, crashing quite often, but it was not the “PRO” version of the drivers. We will see.

Kind regards.

While I hope you get h.265 fixed in Resolve, are you actually happy with the results you got with it before?

I have studio and choose to use Nvenc in Handbrake instead.

Quality presets for h.265 are basically worthless, best is like 20 mbit for 4k, which is not usable.
For h.264 best gives absurdly large files.

Of course with Constant Bitrate you can get whatever bitrate you want. But VBR is really a much better tech. Resolve has VBR, but tBM have chose to give no documentation of how to use it or what the settings are, so unless you want to spend 2 hrs guessing and checking, it is again unusable.


So I export from Resolve in DNxHR and use handbrake. It actually has documentation of what its settings are, a novel concept.

Second that (well, using ProRes on the Mac).
This way you have a good master for any future changes and you get better encoding quality and far more control over the settings.