obs-StreamFX VS AMF

Are you using the blur plugin from here, because there are different types of mask modes https://github.com/Xaymar/obs-StreamFX/wiki/Filter-Blur

StreamFX is not paywalled off, they had an issue with non-GPL code in the repo with the GPL-licensed code. They just updated the Wiki with build instructions. I have to get this built today, it's messing everything up not to have StreamFX in OBS 29. https://github.com/Xaymar/obs-StreamFX/wiki/Building

Yes, it's this one: https://github.com/Xaymar/obs-StreamFX/wiki/Filter-Dynamic-Mask

https://www.xaymar.com/guides/obs/high-quality-recording/ https://www.xaymar.com/guides/obs/high-quality-recording/nvenc/ https://github.com/Xaymar/obs-StreamFX/wiki/Encoder-FFmpeg-NVENC

I downloaded the newest beta of StreamFX for OBS, installed it exactly as they said on my Windows 10 machine, and OBS refuses to recognize the plugin when I open it. No additional filters, no StreamFX tab in the top toolbar, nothing. I've tried downloading for all users and just me. I've tried manually moving the installed plugin from /ProgramData/ to /Program Files(x86). OBS just does not acknowledge that any plugin is present. Using OBS 29.0 and the beta that's supposed to run on 29.0.

If you're technically adept enough to know what NVENC and HEVC are, then it's not too difficult to understand and setup OBS with StreamFX and follow the guide.

for obs 28 you'll need the beta: https://github.com/Xaymar/obs-StreamFX/releases

VA-API is used to access fixed-function hardware on the GPU to encode/decode various media formats. New software can result in small quality improvements, like we saw in last year's AMF update, but it can only add new formats if said hardware was already on your chip. The RX 6600+ have hardware for AV1 decode only. Users of RDNA1 and older, as well as the 6400/6500 XT, will forever be completely SOL.

This has been a long running discussion over on github and has finally been addressed by both AMD and Meta. You need to run at least 23.2.2 and Oculus V53 Desktop app (currently only in Public Test Channel, but you can enroll in the app).

By the way you can check the progress of this bug performance here: https://github.com/GPUOpen-LibrariesAndSDKs/AMF/issues/384

If you had issues on the latest 23.4.1 driver, I recommend going all the way back to 22.2.3 as that's the best driver for Oculus (doesn't enforce bitrate limits, more info https://github.com/GPUOpen-LibrariesAndSDKs/AMF/issues/364).

AMD finally acknowledged and fixed the 100Mbps encoder cap bug in 23.2.2. Now, it's up to Meta to update the Oculus desktop app. For those familiar, there have been multiple threads on the internet plaguing the encoder quality and stability for all 3 VR software (AirLink, VD, ALVR), but as of now, it is in the best state.

Meta/Quest VR headsets had even more issues since they depended on hardware video encoding, and for the longest time many had to stick to a certain version for the encoders to even work. AMD's HEVC encoder is still broken on Oculus Link and there was an artificial bitrate cap added as they try to fix the driver.