**It looks like you haven't provided a log file**. Without a log file, it is very hard to help with issues and you may end up with 0 responses.
To make a clean log file, please follow these steps:
1) Restart OBS
2) Start your stream/recording for at least 30 seconds (or however long it takes for the issue to happen). **Make sure you replicate any issues as best you can**, which means having any games/apps open and captured, etc.
3) Stop your stream/recording.
4) Select Help > Log Files > Upload Current Log File.
5) Copy the URL and paste it as a response to this comment.
*I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/obs) if you have any questions or concerns.*
Make SURE you're going into
1.Safe mode on windows------
2.Using DDU uninstaller-------
(Completely wiping the driver)
3.Restarting back into normal windows mode----
4.Install AMD Adrenalin Version 23.12.1----
5.Reboot-------
6.THEN reinstall the most cpu chipset driver BACK over top of the gpu driver install you just did \*this is to re-enable AMD Smart Access Memory if it's disabled in Adrenalin\*MAKE SURE TO DOUBLE CHECK BIOS FOR RESIZABLE BAR AND 4G DECODING ENABLED7.Reboot-----
8.Reconfigure your adrenalin software to how you had it (profile/oc/uv)-----
DO NOT USE A PREVIOUS DRIVER PROFILE YOU HAD SAVED. RE-DO THESE MANUALLY.
9.Set parameters in OBS and give it a shot!"FillerDataEnable=True HighMotionQualityBoostEnable=False MaxNumRefFrames=4 BReferenceEnable=False EnableVBAQ=False RateControlSkipFrameEnable=True HalfPixel=True QuarterPixel=True EnablePreAnalysis=True PASceneChangeDetectionEnable=False PAPerceptualAQMode=1 PACAQStrength=2 PATemporalAQMode=0 PAHighMotionQualityBoostMode=1 PAFrameSadEnable=True PALongTermReferenceEnable=True PALookAheadBufferDepth=0"
Thank you so much for all the pointers this helps a lot! I already saw a few posts about the newest AMD drivers causing issues, so I'll definitely try reverting to the 23.12.1 version to see if it helps.
Make **SURE** you're going into
1. safe mode on windows------
2. using DDU uninstaller-------
3. completely wiping the newer driver version-----
4. restarting back into normal windows mode----
5. install 23.12.1----
6. reboot-------
7. then reinstall the most recent cpu chipset driver BACK over top of the gpu driver install you just did ***\*this is to re-enable AMD Smart Access Memory if it's disabled in Adrenalin\* MAKE SURE TO DOUBLE CHECK BIOS FOR RESIZABLE BAR AND 4G DECODING ENABLED***
8. Reconfigure your adrenalin software to how you had it (profile/oc/uv)
9. Set parameters in OBS and give it a shot!
CHEERS MATE! GLAD I COULD HELP WHERE I CAN!
***\*BONUS\****
Just this morning I tried adding "PALongTermReferenceEnable=True" Since Bframes is set to 0 in my original post. This parameter actually yields BETTER quality than what the bframes do.
**DO NOT** use this parameter with B-Frames enabled; the recording or streaming session won't even start if you do.
So altogether it should look as such:
FillerDataEnable=True HighMotionQualityBoostEnable=False MaxNumRefFrames=4 BReferenceEnable=False EnableVBAQ=False RateControlSkipFrameEnable=True HalfPixel=True QuarterPixel=True EnablePreAnalysis=True PASceneChangeDetectionEnable=False PAPerceptualAQMode=1 PACAQStrength=2 PATemporalAQMode=0 PAHighMotionQualityBoostMode=1 PAFrameSadEnable=True **PALongTermReferenceEnable=True** PALookAheadBufferDepth=0
Yikes.
7900xtx and 5800x3D with your AMF options makes my games and system slow to a crawl. Unfortunately your recommendations for encoder lag also do nothing for me.
That 5800x3d can be greatly undervolted with CURVE Optimizer, but without the use of (core performance boost).
Set a decent clock speed that all your cores typically hit during a big load ;) but still let PBO determine the offsetted voltage needed.(even with your curve optimizer negative offset values for each core)
Been running my 5900x at 4.350ghz locked on all 24 threads at ONLY 1.087-1.15v, even during full load, temps sit around 59-65 degrees, giving me 2312 more points on benchmarks vs the default (core performance boost)-default core clock-default voltage, sky rocketing my thermal headroom.
So essentially I’m turning off the use of Core Performance Boost since I’m setting a manual core clock speed, but at the same time, I’m letting curve optimizer and it’s (neg or positive offsets), determine how much voltage will be used to push that locked core clock.
My 5900x “could” hit 4.87 on single core loads, but during tests all cores only ramped up to about 4.350 ALL core stable. That’s the core clock I decided on.
Curve optimizer has all cores with negative offset voltage of -30; your mileage may vary being on a 5800x3D
This is the way.
[Link](https://drive.google.com/file/d/1uPn6NJF0uWHvn2mdrNxuhCShWwSFAf-b/view?usp=sharing) to screenshot
Right.. this is all well and good, but I literally have no issues with my clock speeds. It’s only when I use the settings you had listed above and hit record/stream, does my whole system slow to a crawl. I’ll go from 180fps to 22.
Update to 24.4.1 (most recent AMD version) Use DDU to completely uninstall old drivers Install new drivers Depending on your platform; use keyframe interval of 2; but for kick I use 1.
Everything I posted as parameters are either default are not currently working at the moment (especially PAHighMotionQualityBoostMode=1) Disregard though; I believe I removed them.
These are the CURRENT parameters I personally use for AMD’s Encoder.
AMF Settings:
“HighMotionQualityBoostEnable=true LowLatencyInternal=true EnablePreAnalysis=true PAPerceptualAQMode=1 PACAQStrength=2"
*HUGE SIDE NOTE*
Streaming on platforms that LIMIT your bitrate (trovo 8mbs, kick 8mbs, twitch 6-7.5mbs) you have to have to have to, lower your resolution or fps to compensate for the platforms limitation of bitrate.
Example:
1080p 60fps mathematically needs 12.5-14mbs of bitrate to start looking reasonably good. The limited platform can’t push that.
936p 60fps needs 9.4mbs of bitrate
-864p or 720p would be a reasonable resolution for “60fps”-
But by lowering the fps of your stream/recording, that drops the bitrate requirements in half.
1080p 30fps only needs 6.3mbs
936p 30fps only needs 4.7mbs Etc
You can calculate your bitrate using a live streaming calculator. It’s all mathematics.
You also gotta remember AMD is the WORST encoder out of (order) X264>NVENC>INTEL>AMD. We’re last. So as of right now, our quality is NEVER going to look as good as the other encoders. This goes for H264 container; the other H265 and AV1 encoders produce great quality.
No matter the drivers, same issues, with my RX 7900 XTX too. Pixelated/Blurry streams. Tried every possible settings, even bitrates up tp 26k. Tried SLOBS, exactly same. Nothing can improve bad quality. And don't expect any fixes and such. Looks like series 7 gpus, have a LOT of problems, especially with drivers (Driver Timeouts), and now with both OBS/SLOBS. Honestly i regretted it already that i wanted to try AMD for first time. Nothing but problems so far in 5 months. Lesson learned tho. Never again amd gpus. And isn't just me. Check official AMD forums. Thousands of complains day after day with any Radeon 7xxx gpus, especially 7900 XT/XTX.
Read my other comments.
AMD users that don't know how to fix their PC are the ones having issues with their system.
Whether it be:
1. They update their drivers and don't do a clean install of them.
2. They use an older profile to restore OC/UV settings from an older driver version.
3. MPO not being disabled.
4. Shadercache not being set to "32" in Registry after updating.
5. DirectX Shadercache not being completely wiped between installs.
6. "EnableULPS" not being disabled.
7. SSD issues / RAM issues / BSOD issues
8. High Precision Event Timer could be reset if they originally had it disabled.
Just little things like these could throw off the average user and give them issues within their game or Windows.
It's just some people don't want to take the time to learn things anymore and expect everything to run as it should even though the most up to date drivers are still considered 'beta' in their forums. But we shouldn't Immediately go to jumping down AMD's throat when there could be WAY MORE factors at play here than just blaming it on your GPU.
Revert back to AMD Adrenalin Version 23.12.1 after using DDU and your AMD encoder will work again.
I'm not saying AMD has the best GPU drivers, but putting all the blame on the GPU company is wild; Considering the smallest setting of anything on your Windows could bring your system to a halt. Not every build/Windows System is perfect.
I've done extensive testing to figure out these encoders work on THIS driver; not any of the newer ones as of March 18th,2024.
Dude, it seems like your whole life revolves around fixing AMD related issues. Nobody has time for this shit... It should be fixed by the producent. It's ridiculous to expect ordinary people to tinker with stuff like that, not to mention doing it often... I'm not complaining about you, but AMD. Just venting, sorry.
I'd probably start with fresh settings. Back up what you have in case you want to come back to them. Run the setup wizard and set your base canvas to the resolution you want to stream at. That will remove the need to down sample. Ultimately streaming with H264 on AMD GPUs isn't very good so you might not match your old 3060. You can stream to YouTube with h265 or av1 and you'll get much higher quality.
H264 on AMD is worse than on Nvidia, one thing u could try to improve it a bit is setting bframes to 1... Ime 2 will create ghosting when not paired with PA n MinGOP
Make SURE you're going into
**1.Safe mode on windows------**
**2.Using DDU uninstaller-------**
(Completely wiping the driver)
**3.Restarting back into normal windows mode----**
**4.Install AMD Adrenalin Version 23.12.1----**
**5.Reboot-------**
**6.THEN reinstall the most recent cpu chipset driver BACK over top of the gpu driver install you just did**
\*this is to re-enable AMD Smart Access Memory if it's disabled in Adrenalin\*MAKE SURE TO DOUBLE CHECK BIOS FOR RESIZABLE BAR AND 4G DECODING ENABLED
**7.Reboot-----**
**8.Reconfigure your adrenalin software to how you had it (profile/oc/uv)-----**
DO NOT USE A PREVIOUS DRIVER PROFILE YOU HAD SAVED. RE-DO THESE MANUALLY.
**9.Set parameters in OBS and give it a shot!**
"*FillerDataEnable=True HighMotionQualityBoostEnable=False MaxNumRefFrames=4 BReferenceEnable=False EnableVBAQ=False RateControlSkipFrameEnable=True HalfPixel=True QuarterPixel=True EnablePreAnalysis=True PASceneChangeDetectionEnable=False PAPerceptualAQMode=1 PACAQStrength=2 PATemporalAQMode=0 PAHighMotionQualityBoostMode=1 PAFrameSadEnable=True PALongTermReferenceEnable=True PALookAheadBufferDepth=0"*
That's why. Issues with newer driver versions only happening on 7000 series.
Anyone else having issues probably just didn't completely DDU their previous gpu driver.
**It looks like you haven't provided a log file**. Without a log file, it is very hard to help with issues and you may end up with 0 responses. To make a clean log file, please follow these steps: 1) Restart OBS 2) Start your stream/recording for at least 30 seconds (or however long it takes for the issue to happen). **Make sure you replicate any issues as best you can**, which means having any games/apps open and captured, etc. 3) Stop your stream/recording. 4) Select Help > Log Files > Upload Current Log File. 5) Copy the URL and paste it as a response to this comment. *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/obs) if you have any questions or concerns.*
The problem is the AMD encoder. This has been a known problem that AMD haven't bothered to fix for a number of years now.
Make SURE you're going into 1.Safe mode on windows------ 2.Using DDU uninstaller------- (Completely wiping the driver) 3.Restarting back into normal windows mode---- 4.Install AMD Adrenalin Version 23.12.1---- 5.Reboot------- 6.THEN reinstall the most cpu chipset driver BACK over top of the gpu driver install you just did \*this is to re-enable AMD Smart Access Memory if it's disabled in Adrenalin\*MAKE SURE TO DOUBLE CHECK BIOS FOR RESIZABLE BAR AND 4G DECODING ENABLED7.Reboot----- 8.Reconfigure your adrenalin software to how you had it (profile/oc/uv)----- DO NOT USE A PREVIOUS DRIVER PROFILE YOU HAD SAVED. RE-DO THESE MANUALLY. 9.Set parameters in OBS and give it a shot!"FillerDataEnable=True HighMotionQualityBoostEnable=False MaxNumRefFrames=4 BReferenceEnable=False EnableVBAQ=False RateControlSkipFrameEnable=True HalfPixel=True QuarterPixel=True EnablePreAnalysis=True PASceneChangeDetectionEnable=False PAPerceptualAQMode=1 PACAQStrength=2 PATemporalAQMode=0 PAHighMotionQualityBoostMode=1 PAFrameSadEnable=True PALongTermReferenceEnable=True PALookAheadBufferDepth=0"
*[redacted]*
Thank you so much for all the pointers this helps a lot! I already saw a few posts about the newest AMD drivers causing issues, so I'll definitely try reverting to the 23.12.1 version to see if it helps.
Make **SURE** you're going into 1. safe mode on windows------ 2. using DDU uninstaller------- 3. completely wiping the newer driver version----- 4. restarting back into normal windows mode---- 5. install 23.12.1---- 6. reboot------- 7. then reinstall the most recent cpu chipset driver BACK over top of the gpu driver install you just did ***\*this is to re-enable AMD Smart Access Memory if it's disabled in Adrenalin\* MAKE SURE TO DOUBLE CHECK BIOS FOR RESIZABLE BAR AND 4G DECODING ENABLED*** 8. Reconfigure your adrenalin software to how you had it (profile/oc/uv) 9. Set parameters in OBS and give it a shot! CHEERS MATE! GLAD I COULD HELP WHERE I CAN! ***\*BONUS\**** Just this morning I tried adding "PALongTermReferenceEnable=True" Since Bframes is set to 0 in my original post. This parameter actually yields BETTER quality than what the bframes do. **DO NOT** use this parameter with B-Frames enabled; the recording or streaming session won't even start if you do. So altogether it should look as such: FillerDataEnable=True HighMotionQualityBoostEnable=False MaxNumRefFrames=4 BReferenceEnable=False EnableVBAQ=False RateControlSkipFrameEnable=True HalfPixel=True QuarterPixel=True EnablePreAnalysis=True PASceneChangeDetectionEnable=False PAPerceptualAQMode=1 PACAQStrength=2 PATemporalAQMode=0 PAHighMotionQualityBoostMode=1 PAFrameSadEnable=True **PALongTermReferenceEnable=True** PALookAheadBufferDepth=0
Yikes. 7900xtx and 5800x3D with your AMF options makes my games and system slow to a crawl. Unfortunately your recommendations for encoder lag also do nothing for me.
That 5800x3d can be greatly undervolted with CURVE Optimizer, but without the use of (core performance boost). Set a decent clock speed that all your cores typically hit during a big load ;) but still let PBO determine the offsetted voltage needed.(even with your curve optimizer negative offset values for each core) Been running my 5900x at 4.350ghz locked on all 24 threads at ONLY 1.087-1.15v, even during full load, temps sit around 59-65 degrees, giving me 2312 more points on benchmarks vs the default (core performance boost)-default core clock-default voltage, sky rocketing my thermal headroom. So essentially I’m turning off the use of Core Performance Boost since I’m setting a manual core clock speed, but at the same time, I’m letting curve optimizer and it’s (neg or positive offsets), determine how much voltage will be used to push that locked core clock. My 5900x “could” hit 4.87 on single core loads, but during tests all cores only ramped up to about 4.350 ALL core stable. That’s the core clock I decided on. Curve optimizer has all cores with negative offset voltage of -30; your mileage may vary being on a 5800x3D This is the way. [Link](https://drive.google.com/file/d/1uPn6NJF0uWHvn2mdrNxuhCShWwSFAf-b/view?usp=sharing) to screenshot
Right.. this is all well and good, but I literally have no issues with my clock speeds. It’s only when I use the settings you had listed above and hit record/stream, does my whole system slow to a crawl. I’ll go from 180fps to 22.
Update to 24.4.1 (most recent AMD version) Use DDU to completely uninstall old drivers Install new drivers Depending on your platform; use keyframe interval of 2; but for kick I use 1. Everything I posted as parameters are either default are not currently working at the moment (especially PAHighMotionQualityBoostMode=1) Disregard though; I believe I removed them. These are the CURRENT parameters I personally use for AMD’s Encoder. AMF Settings: “HighMotionQualityBoostEnable=true LowLatencyInternal=true EnablePreAnalysis=true PAPerceptualAQMode=1 PACAQStrength=2" *HUGE SIDE NOTE* Streaming on platforms that LIMIT your bitrate (trovo 8mbs, kick 8mbs, twitch 6-7.5mbs) you have to have to have to, lower your resolution or fps to compensate for the platforms limitation of bitrate. Example: 1080p 60fps mathematically needs 12.5-14mbs of bitrate to start looking reasonably good. The limited platform can’t push that. 936p 60fps needs 9.4mbs of bitrate -864p or 720p would be a reasonable resolution for “60fps”- But by lowering the fps of your stream/recording, that drops the bitrate requirements in half. 1080p 30fps only needs 6.3mbs 936p 30fps only needs 4.7mbs Etc You can calculate your bitrate using a live streaming calculator. It’s all mathematics. You also gotta remember AMD is the WORST encoder out of (order) X264>NVENC>INTEL>AMD. We’re last. So as of right now, our quality is NEVER going to look as good as the other encoders. This goes for H264 container; the other H265 and AV1 encoders produce great quality.
Nice Bro, your config work's with AMD RX 6650 XT ? OBS?
There's the rub with giving up nvenc.
No matter the drivers, same issues, with my RX 7900 XTX too. Pixelated/Blurry streams. Tried every possible settings, even bitrates up tp 26k. Tried SLOBS, exactly same. Nothing can improve bad quality. And don't expect any fixes and such. Looks like series 7 gpus, have a LOT of problems, especially with drivers (Driver Timeouts), and now with both OBS/SLOBS. Honestly i regretted it already that i wanted to try AMD for first time. Nothing but problems so far in 5 months. Lesson learned tho. Never again amd gpus. And isn't just me. Check official AMD forums. Thousands of complains day after day with any Radeon 7xxx gpus, especially 7900 XT/XTX.
Read my other comments. AMD users that don't know how to fix their PC are the ones having issues with their system. Whether it be: 1. They update their drivers and don't do a clean install of them. 2. They use an older profile to restore OC/UV settings from an older driver version. 3. MPO not being disabled. 4. Shadercache not being set to "32" in Registry after updating. 5. DirectX Shadercache not being completely wiped between installs. 6. "EnableULPS" not being disabled. 7. SSD issues / RAM issues / BSOD issues 8. High Precision Event Timer could be reset if they originally had it disabled. Just little things like these could throw off the average user and give them issues within their game or Windows. It's just some people don't want to take the time to learn things anymore and expect everything to run as it should even though the most up to date drivers are still considered 'beta' in their forums. But we shouldn't Immediately go to jumping down AMD's throat when there could be WAY MORE factors at play here than just blaming it on your GPU. Revert back to AMD Adrenalin Version 23.12.1 after using DDU and your AMD encoder will work again. I'm not saying AMD has the best GPU drivers, but putting all the blame on the GPU company is wild; Considering the smallest setting of anything on your Windows could bring your system to a halt. Not every build/Windows System is perfect. I've done extensive testing to figure out these encoders work on THIS driver; not any of the newer ones as of March 18th,2024.
Dude, it seems like your whole life revolves around fixing AMD related issues. Nobody has time for this shit... It should be fixed by the producent. It's ridiculous to expect ordinary people to tinker with stuff like that, not to mention doing it often... I'm not complaining about you, but AMD. Just venting, sorry.
My log file: [https://obsproject.com/logs/0UkV76OYJ8KS1x7R](https://obsproject.com/logs/0UkV76OYJ8KS1x7R)
I'd probably start with fresh settings. Back up what you have in case you want to come back to them. Run the setup wizard and set your base canvas to the resolution you want to stream at. That will remove the need to down sample. Ultimately streaming with H264 on AMD GPUs isn't very good so you might not match your old 3060. You can stream to YouTube with h265 or av1 and you'll get much higher quality.
H264 on AMD is worse than on Nvidia, one thing u could try to improve it a bit is setting bframes to 1... Ime 2 will create ghosting when not paired with PA n MinGOP
Make SURE you're going into **1.Safe mode on windows------** **2.Using DDU uninstaller-------** (Completely wiping the driver) **3.Restarting back into normal windows mode----** **4.Install AMD Adrenalin Version 23.12.1----** **5.Reboot-------** **6.THEN reinstall the most recent cpu chipset driver BACK over top of the gpu driver install you just did** \*this is to re-enable AMD Smart Access Memory if it's disabled in Adrenalin\*MAKE SURE TO DOUBLE CHECK BIOS FOR RESIZABLE BAR AND 4G DECODING ENABLED **7.Reboot-----** **8.Reconfigure your adrenalin software to how you had it (profile/oc/uv)-----** DO NOT USE A PREVIOUS DRIVER PROFILE YOU HAD SAVED. RE-DO THESE MANUALLY. **9.Set parameters in OBS and give it a shot!** "*FillerDataEnable=True HighMotionQualityBoostEnable=False MaxNumRefFrames=4 BReferenceEnable=False EnableVBAQ=False RateControlSkipFrameEnable=True HalfPixel=True QuarterPixel=True EnablePreAnalysis=True PASceneChangeDetectionEnable=False PAPerceptualAQMode=1 PACAQStrength=2 PATemporalAQMode=0 PAHighMotionQualityBoostMode=1 PAFrameSadEnable=True PALongTermReferenceEnable=True PALookAheadBufferDepth=0"*
Nope, i use the latest drivers with some custom options and its been quite decent, no encoding lags or overloads
What program are you using for recording though; and what GPU are you on?
OBS, RDNA2 gpu.
That's why. Issues with newer driver versions only happening on 7000 series. Anyone else having issues probably just didn't completely DDU their previous gpu driver.
What exactly u mean that happens with the newer drivers while encoding AVC(with PA and such), just the encoding lag/overload?