AMD Is Hiring To Improve Its Linux Graphics Driver Installation Experience

[Quackdoc]

I see, thanks. For some reason on my system all uvd values seem to be stuck at 0. I encountered the same issue when trying to read video decode activity stats using another script a couple months ago, probably a firmware issue.

what graphics card is it? im using a rx 580 polaris myself

[Mystro256]

- AMF not fully working with linux (and quality needs to get fundamentally better with RDNA3 or Zen4-APUs)

Any reason you don't use mesa's VAAPI support? This is officially supported by AMD and is a more mature stack. As well it's open source and default provided by distros.

[Quackdoc]

Any reason you don't use mesa's VAAPI support? This is officially supported by AMD and is a more mature stack. As well it's open source and default provided by distros.

vaapi encoding is dogcrap compared to amf.

[osw89]

what graphics card is it? im using a rx 580 polaris myself

It's a rx 6800, I wouldn't be surprised if AMD hasn't bothered to update their tools yet.

[Quackdoc]

It's a rx 6800, I wouldn't be surprised if AMD hasn't bothered to update their tools yet.

Can't check right now but is there a VCN tab? UVD and VCN might be different things in the program?

[osw89]

Can't check right now but is there a VCN tab? UVD and VCN might be different things in the program?

There's only a UVD tab and no mention of VCN which is interesting because RDNA2 has VCN3.0 and not UVD. There are options to show stats for UVD and VCE but I can't get umr to display anything related to VCN. This is what it looks like after pressing a to make it display everything.

[osw89]

This is what it looks like

For some reason the site doesn't let me edit so here's a link https://imgur.com/a/NJYCSKW

[photom]

Any reason you don't use mesa's VAAPI support? This is officially supported by AMD and is a more mature stack. As well it's open source and default provided by distros.

yes I use vaapi for all my AMD vaapi needs atm - it has a working decoder/encoder - amf is more like unfinished business - no hardware context - I already created a support ticket (github-issue) in the past - but even vaapi differs between between team green/red/blue - some allow hwcontext switching, some do not - AMD doesn't work at all talking about switching between vulkan<>opencl<>vaapi.... sad story, they're waiting for ffmpeg devs to allow their patches for ages