![]() ![]() I've tried searching around, but it seems to be such a niche issue no one is talking about it. But I only see ~25% utilization by anything using AMF, but relive sees a cool ~45%. The card has 5 different dedicated encoding cores, it shouldn't be so difficult to utilize it. Is anyone aware of this issue? Is it in theory fixable in software? Is it just bad implementations in every other application but relive? ![]() Both modes work flawlessly without dropping any frames.īut every app I've tested with AMF/VCE support (Playclaw 5 & 6, OBS Studio + AMF plugin, Action!, MSI Afterburner, Microsoft Game Bar) all exhibit the same issue of not actually recording at anything usable (usually around 2-10fps). I am able to encode 30mbit HEVC with my Vega card through relive in 1440p just fine while sitting at 100% gpu usage. And Relive is very limited in it's capability, so it isn't fit for purpose. I really like the interface and usability playclaw 5 offers me, but given the issue with AMF encoding, it seems it's not a real option anymore. ![]() This means I cannot record using my software anymore. I just upgraded to 1440p144hz, and while beautiful, this means I'm hitting 99-100% gpu usage in most every game I play. I use Playclaw 5 & 6 to record gameplay very often, and until recently I hadn't ran into this issue because I had a 1080p60 monitor and a vega 56, more than enough to have headroom on the GPU. Hardware unboxed found the same thing I did here:
0 Comments
Leave a Reply. |