Bug Report Unable to use AMD encoder after upgrading to 19.0.2

[ddribin]

Hello,

I was using the AMD hardware encoder on version 18.0.1. When the auto-updater offered to update to 19.0.2, I upgraded, and now I am no longer able to use the AMD hardware encoding. Using the software encoder, my machine cannot encode fast enough, even at 100% CPU, whereas the hardware encoder kept CPU usage around 20%.

Logs are here and attached as a zip:

https://gist.github.com/ddribin/cccfac42c5e630f0f4464c05e3a58625

I successfully used the HW encoder in 2017-05-21 10-53-29.txt. On 5-22, I upgraded to 19.0.2, and in 2017-05-22 22-42-23.txt, I was unable to use the AMD encoder, and tried to use the software encoder. There'a a couple of logs in between those, too.

Any help would be appreciated.

Thanks,

-Dave

 

[Lain]

Hey there, just wanted to check before anything else -- have you updated your drivers recently? If you haven't, could you try with the latest drivers? The AMF plugin author upgraded the AMF SDK, so it might require the latest drivers to function properly.

 

[ddribin]

Looks look I'm using Software Version 16.6, and it's all up-to-date, according to their updater. See attached screen shots. One possible wrinkle is that I'm using a Apple Mac Book Pro (15-inch, 2016) running Windows 10 under Boot Camp.

 

[Xaymar]

The one log where AMF is missing is the log where it can't find the enc-amf.dll. Make sure that you actually have an enc-amf.dll in the obs-plugins directory, aside from that there's not much I can really do.

 

[ddribin]

In that run, I may have tried to explicitly install the plugin explicitly from:

https://github.com/Xaymar/obs-studio_amf-encoder-plugin

Previous logs, like 2017-05-22 21-55-36.txt, show enc-amf.dll being loaded, but it's still not available:

22:39:40.319:   Loaded Modules:
22:39:40.319:     enc-amf.dll
22:39:40.319: ==== Startup complete ===============================================
22:39:40.319: Encoder ID 'amd_amf_h264' not found
22:39:40.320: Encoder ID 'amd_amf_h264' not found

The problematic bits look earlier in the log:

22:39:40.133: [AMF] Version 2.1.5 loaded (Compiled: 1.4.2.0, Runtime: 1.3.0.5, Library: 1;3;0;5;16.40;201609142243).
22:39:40.158: [AMF] [H264]<Id: 1> Failed to set encoder color range, error AMF_INVALID_ARG (code 4)
22:39:40.176: [AMF] <Id: 2> <Plugin::AMD::EncoderH265::SetUsage> Failed to set to Transcoding, error AMF_INVALID_ARG (code 4)
22:39:40.193: [AMF] [H264]<Id: 3> Failed to set encoder color range, error AMF_INVALID_ARG (code 4)
22:39:40.211: [AMF] <Id: 4> <Plugin::AMD::EncoderH265::SetUsage> Failed to set to Transcoding, error AMF_INVALID_ARG (code 4)
22:39:40.211: [AMF] [H264/AVC] Not supported by any GPU, disabling...
22:39:40.211: [AMF] [H265/HEVC] Not supported by any GPU, disabling...

Are you saying this will not work until I can somehow get updated drivers? What's the minimum AMD version required?

 

[Xaymar]

Starting with Version 2.x, the minimum driver is always the latest AMD Driver. Your drivers don't even seem to understand the first parameter of AMF...

 

[ddribin]

That's a bummer.... Looks like I need to downgrade back to version 18.0.x, as software encoding isn't good enough for my use. Hopefully you can find some backwards compatible way to support older drivers in future versions of the plugin. I had no problems on 18.0.1. It all worked great!

Thanks for the replies,

-Dave

 

[Xaymar]

That's a bummer.... Looks like I need to downgrade back to version 18.0.x, as software encoding isn't good enough for my use. Hopefully you can find some backwards compatible way to support older drivers in future versions of the plugin. I had no problems on 18.0.1. It all worked great!

Thanks for the replies,

-Dave

The issue isn't backwards compatibility here, its that the driver/GPU you have doesn't understand the parameter i gave it. You can always downgrade the enc-amf plugin to 1.4.3.x if that somehow worked out. :/