HW transcoding stopped working after 4.9.3.0 update

[Luke 42884]

Hi, are you still having an issue with this?

[CFC 31]

On 3/24/2026 at 12:20 PM, solidsnakex37 said:

After days of troubleshooting, I can confirm that downgrading from 4.9.3 to 4.9.1.90 resolved this issue for me. 

My Arc A380 wasn't tone mapping, I was getting: 
 

WARNING: Small BAR detected for device 0000:83:00.0
Failed to get number of OpenCL platforms: -1001.
Failed to created derived device context: -19.
Conversion failed!
→ Falling back to software transcoding.

I am no longer getting these errors after a rollback and tone mapping is fixed. 

 

On 5/19/2026 at 8:28 PM, jhoff80 said:

Nothing in the changelog, but anyone planning on being the guinea pig to see if 4.9.5 fixes these issues?  I'll be sticking on 4.9.1.90 for a while.

 

On 5/31/2026 at 3:27 PM, Luke said:

Hi, are you still having an issue with this?

@LukeThis still seems to be an issue on 4.9.5.

Do we know what the latest stable version that correctly handles hardware tonemapping? is it in fact 4.9.1.90?

 

Thanks,
CFC

[Q-Droid 1047]

1 hour ago, CFC said:

Do we know what the latest stable version that correctly handles hardware tonemapping? is it in fact 4.9.1.90?

Yes. That's the latest that isn't broken.

 

[Luke 42884]

HI, we'll have the new ffmpeg build on the server beta channel very soon, so stay tuned for that. Thanks.

[lebowski 2]

I just installed a A380 GPU via unraid, was able to get it working with Tone Mapping under 4.9.1.90 only. Took me hours to figure it all out, and I'm watching this thread for updates. Thank you.

Edited August 3 by lebowski

[jhoff80 94]

Been broken (in the 'stable' build no less) literally for 8 months now.  Can't imagine why people would be more interested in the open-source fork.

[Wynter 3]

There cannot possibly be any acceptable reason of any kind for breaking a feature like this and not fixing it at this point.

[Q-Droid 1047]

Patience grasshopper. It's only been eight months.