Updated english locale text for Pre-Pass to include encoding cost.Fixed a bug with automatic Profile Level which sometimes caused an unsupported Profile Level to be selected.Fixed error during initialization for H264 and H265 on Driver 19.x and above.Additionally a bug was fixed for Automatic Profile Level which caused it to occasionally select an unsupported Profile Level. The encoder options are now applied correctly and should no longer cause any issues. With this patch, this is no longer necessary. Due to this, the plugin would fail to properly initialize the encoder and users would have to manually set some options. The 19.x Driver started enforcing additional restrictions, which seem to only apply to AMD Vega GPUs and APUs. Users on Windows 8 are urged to upgrade to Windows 10. The Video API option will now only show the most modern supported API on the platform, which is Direct3D 11 on Windows 10 and Direct3D 9 on Windows 7.Fixed automatic VBV Buffer calculation with values close or above 50%.Added the new "High Motion Quality Boost" option which seems to be exclusive to the Navi (RDNA) series of AMD GPUs.This also includes dropping support for unmodified Windows 8 systems as AMD has stopped providing driver updates to Windows 8. You will now need a minimum Driver version of 19.7.1, however the recommended minimum is 19.9.2 which contains a lot of fixes compared to 19.7.1. Removed support for older drivers that ship an AMF Runtime older than version 1.4.14.With the fix applied, values above 50% correctly approach the strictest possible buffer size again, allowing tighter control over bitrate. The incorrect behavior before was that all values above 50% would act like 50%. You will now need to have an up-to-date driver, at minimum 19.7.1 though the recommended minimum is 19.9.2, otherwise the plugin will refuse to load and does not add any encoders for use.Īdditionally jpark37/rcdrone also fixed the VBV Buffer Strictness option. However due to that the new feature, the plugin now finally dropped support for ancient drivers. This option should allow you to get higher quality streams at the exact same bitrate, resolution and framerate, given that you own and use an AMD RX 5700 (XT/XT Anniversary). ^ this makes my Plays.With their new Navi GPU series AMD added a new feature to the hardware encoders: High Motion Quality Boost. ^ this makes my Plays.TV recordings end result ~60fps (normal) ^ this makes my Plays.TV recordings end result ~40fpsĪMD ReLive using AVC / 720p / 3.5 Mbps bitrate / 60fps Preset: Twitch / Quality Preset: Quality / Target Bitrate 3500 / Scaled output: 720p / 60fps ![]() OBS using H264 Encoder (AMD Advanced Media Framework) / Plays.TV recording at 1080p / 60fps / 15mbps bitrate. ![]() Using latest AMD Crimson ReLive drivers, latest AMF plugin from github, R9 200 series graphics card. I'm not sure if it's just my system or if someone else can reproduce this. Shouldn't ReLive and AMF plugin be using similar techonology (VCE), so why does it affect my locally recorded clips with Plays.TV that differently (~20 fps change?) Supposedly this plugin + OBS Studio is better performance wise in-game than ReLive, but I don't understand why it's making my Plays.TV recordings come out at 40fps instead of 60fps. However, using the built-in AMD ReLive tool to stream to twitch, the Plays.TV clips come out at their regular 60fps. I'm not sure if it's a bug with the OBS Studio or this plugin, but if I auto-record Overwatch gameplay using the Plays.TV client, and at the same time stream with OBS Studio using this AMD hardware encoding instead of x264 software encoding, I will get 40fps recorded video when I watch the recorded clips. (didn't realize there was an AMF plugin for OBS.welp)Īnd I came into a weird problem. Hey, so I was testing different GPU encoding options for streaming after the ReLive driver came out.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |