Recording is fine for a few minutes, and then FPS tank significantly, up to single digits.

[Franciscop98]

Yes, I know this must be one of the most repeated threads ever, but I'm really struggling with this. I tried admin, having only 1 source in the scene, game capture vs window capture (window capture actually made it significantly worse, with a still frame lasting up to 5 minutes). The game I'm trying to capture is vanilla Doom, with no mods, through GZDoom. I don't think such a game would hog GPU resources like that.

I attached my last 2 logs. I'm hoping there's something there that can help me. And yeah, I'm very new to recording videos, and I can't figure this out for the life of me. I just want the recording to look watchable.

 

[rockbottom]

There's a touch of rendering lag so your GPU is slightly overloaded. I also noticed your AMD driver looks like it's stale/from 2023. AMD drivers are hit or miss, no recommendation here.

To clear the encoding lag, try using either the Balanced or Speed preset, Quality is clearly too slow. No idea what is causing the GL error at the end.

22:45:46.388: [texture-amf-h264: 'advanced_video_stream'] B-Frames set to 3 but b-frames are not supported by this device
22:45:46.388: [texture-amf-h264: 'advanced_video_stream'] Failed to set property 'HighMotionQualityBoostEnable': AMF_INVALID_ARG
22:45:46.388: [texture-amf-h264: 'advanced_video_stream'] settings:
22:45:46.388: rate_control: CBR
22:45:46.388: bitrate: 6000
22:45:46.388: cqp: 20
22:45:46.388: keyint: 120
22:45:46.388: preset: quality
22:45:46.388: profile: high
22:45:46.388: b-frames: 0
22:45:46.388: width: 1360
22:45:46.388: height: 768
22:45:46.388: params: (none)
22:45:46.408: ---------------------------------
22:45:46.409: [FFmpeg aac encoder: 'Track1'] bitrate: 160, channels: 2, channel_layout: stereo

23:17:45.939: Output 'adv_file_output': Total frames output: 102649
23:17:45.939: Output 'adv_file_output': Total drawn frames: 102842 (102866 attempted)
23:17:45.939: Output 'adv_file_output': Number of lagged frames due to rendering lag/stalls: 24 (0.0%)
23:17:45.940: ==== Recording Stop ================================================
23:17:45.940: Video stopped, number of skipped frames due to encoding lag: 58355/102864 (56.7%)
23:25:42.018: [game-capture: 'Doom Classic'] gl_free: GL error occurred on free: 1282

 

[Franciscop98]

There's a touch of rendering lag so your GPU is slightly overloaded. I also noticed your AMD driver looks like it's stale/from 2023. AMD drivers are hit or miss, no recommendation here.

To clear the encoding lag, try using either the Balanced or Speed preset, Quality is clearly too slow. No idea what is causing the GL error at the end.

22:45:46.388: [texture-amf-h264: 'advanced_video_stream'] B-Frames set to 3 but b-frames are not supported by this device
22:45:46.388: [texture-amf-h264: 'advanced_video_stream'] Failed to set property 'HighMotionQualityBoostEnable': AMF_INVALID_ARG
22:45:46.388: [texture-amf-h264: 'advanced_video_stream'] settings:
22:45:46.388: rate_control: CBR
22:45:46.388: bitrate: 6000
22:45:46.388: cqp: 20
22:45:46.388: keyint: 120
22:45:46.388: preset: quality
22:45:46.388: profile: high
22:45:46.388: b-frames: 0
22:45:46.388: width: 1360
22:45:46.388: height: 768
22:45:46.388: params: (none)
22:45:46.408: ---------------------------------
22:45:46.409: [FFmpeg aac encoder: 'Track1'] bitrate: 160, channels: 2, channel_layout: stereo

23:17:45.939: Output 'adv_file_output': Total frames output: 102649
23:17:45.939: Output 'adv_file_output': Total drawn frames: 102842 (102866 attempted)
23:17:45.939: Output 'adv_file_output': Number of lagged frames due to rendering lag/stalls: 24 (0.0%)
23:17:45.940: ==== Recording Stop ================================================
23:17:45.940: Video stopped, number of skipped frames due to encoding lag: 58355/102864 (56.7%)
23:25:42.018: [game-capture: 'Doom Classic'] gl_free: GL error occurred on free: 1282

Thank you for the reply!

I will try the speed preset tonight, but that is still very confusing to me. We're talking about Doom here, that should take a miniscule amount of GPU, how is that overloading the GPU? If I can't record Classic Doom, at 60 FPS, and have it look good, then there's something seriously wrong with the set up. And I'm not running integrated graphics or something like that, it's an RX580, which I know isn't brand new, but classic Doom? Really?

It honestly feels like there's a memory leak. I'm not saying that's what's happening, but that's what it feels like. Everything runs and records perfectly fine, a smooth 60 FPS, and then suddenly, after a couple of minutes, I'm getting 10 FPS or less.

 

[rockbottom]

Test with the faster Presets & post the new log.

Log 1 is incomplete but log 2 shows a mem leak. I already mentioned your driver is stale & there is a GL error. I don't run AMD for a reason. Do some legwork to see what newer driver is working for people & update if things don't improve.

Audio could be improved too.
Select the actual Desktop Audio device.
I would avoid using Global & Source Audio concurrently. Pick one or the other.

22:46:39.477: [win-wasapi: 'Desktop Audio'] update settings:
22:46:39.477: device id: default
22:46:39.477: use device timing: 1
22:46:39.477: [Loaded global audio device]: 'Desktop Audio'
22:46:39.477: [win-wasapi: 'Mic/Aux'] update settings:
22:46:39.477: device id: default
22:46:39.477: use device timing: 0
22:46:39.478: [noise suppress: 'Noise Suppression'] NVAFX redist is not installed.
22:46:39.478: [Loaded global audio device]: 'Mic/Aux'
22:46:39.478: - filter: 'Noise Suppression' (noise_suppress_filter_v2)
22:46:39.496: WASAPI: Device 'Microphone (DRELANMIC)' [48000 Hz] initialized (source: Mic/Aux)
22:46:39.505: WASAPI: Device 'Speakers (Realtek(R) Audio)' [48000 Hz] initialized (source: Desktop Audio)
22:46:39.535: adding 42 milliseconds of audio buffering, total audio buffering is now 42 milliseconds (source: Mic/Aux)
22:46:39.535:
22:46:39.600: [win-wasapi: 'The Messenger (Audio)'] update settings:
22:46:39.600: executable: TheMessenger.exe
22:46:39.600: title: The Messenger
22:46:39.600: class: UnityWndClass
22:46:39.600: priority: 0
22:46:39.601: [win-wasapi: 'Audio Output Capture'] update settings:
22:46:39.601: device id: default
22:46:39.601: use device timing: 1
22:46:39.601: [win-wasapi: 'Doom Classic (Audio)'] update settings:
22:46:39.601: executable: gzdoom.exe
22:46:39.601: title: Halls of the Damned - The Ultimate DOOM
22:46:39.601: class: MainWindow
22:46:39.601: priority: 2
22:46:39.603: Switched to scene 'Streaming'
22:46:39.603: ------------------------------------------------
22:46:39.603: Loaded scenes:
22:46:39.603: - scene 'Scene':
22:46:39.603: - source: 'The Messenger' (game_capture)
22:46:39.603: - source: 'The Messenger (Audio)' (wasapi_process_output_capture)
22:46:39.603: - scene 'Streaming':
22:46:39.603: - source: 'Doom Classic' (game_capture)
22:46:39.603: - scene 'Test':
22:46:39.603: - source: 'Audio Output Capture' (wasapi_output_capture)

L2?
19:47:56.866: Loaded scenes:
19:47:56.866: - scene 'Scene':
19:47:56.866: - source: 'The Messenger' (game_capture)
19:47:56.866: - source: 'The Messenger (Audio)' (wasapi_process_output_capture)
19:47:56.866: - scene 'Streaming':
19:47:56.866: - source: 'Dusk' (game_capture)
19:47:56.866: - source: 'Lethal Company' (game_capture)
19:47:56.866: - source: 'Doom (2016)' (game_capture)
19:47:56.866: - source: 'Doom Eternal' (game_capture)
19:47:56.866: - scene 'Test':
19:47:56.866: - source: 'Audio Output Capture' (wasapi_output_capture)

 

[Franciscop98]

Test with the faster Presets & post the new log.

Log 1 is incomplete but log 2 shows a mem leak. I already mentioned your driver is stale & there is a GL error. I don't run AMD for a reason. Do some legwork to see what newer driver is working for people & update if things don't improve.

Audio could be improved too.
Select the actual Desktop Audio device.
I would avoid using Global & Source Audio concurrently. Pick one or the other.

22:46:39.477: [win-wasapi: 'Desktop Audio'] update settings:
22:46:39.477: device id: default
22:46:39.477: use device timing: 1
22:46:39.477: [Loaded global audio device]: 'Desktop Audio'
22:46:39.477: [win-wasapi: 'Mic/Aux'] update settings:
22:46:39.477: device id: default
22:46:39.477: use device timing: 0
22:46:39.478: [noise suppress: 'Noise Suppression'] NVAFX redist is not installed.
22:46:39.478: [Loaded global audio device]: 'Mic/Aux'
22:46:39.478: - filter: 'Noise Suppression' (noise_suppress_filter_v2)
22:46:39.496: WASAPI: Device 'Microphone (DRELANMIC)' [48000 Hz] initialized (source: Mic/Aux)
22:46:39.505: WASAPI: Device 'Speakers (Realtek(R) Audio)' [48000 Hz] initialized (source: Desktop Audio)
22:46:39.535: adding 42 milliseconds of audio buffering, total audio buffering is now 42 milliseconds (source: Mic/Aux)
22:46:39.535:
22:46:39.600: [win-wasapi: 'The Messenger (Audio)'] update settings:
22:46:39.600: executable: TheMessenger.exe
22:46:39.600: title: The Messenger
22:46:39.600: class: UnityWndClass
22:46:39.600: priority: 0
22:46:39.601: [win-wasapi: 'Audio Output Capture'] update settings:
22:46:39.601: device id: default
22:46:39.601: use device timing: 1
22:46:39.601: [win-wasapi: 'Doom Classic (Audio)'] update settings:
22:46:39.601: executable: gzdoom.exe
22:46:39.601: title: Halls of the Damned - The Ultimate DOOM
22:46:39.601: class: MainWindow
22:46:39.601: priority: 2
22:46:39.603: Switched to scene 'Streaming'
22:46:39.603: ------------------------------------------------
22:46:39.603: Loaded scenes:
22:46:39.603: - scene 'Scene':
22:46:39.603: - source: 'The Messenger' (game_capture)
22:46:39.603: - source: 'The Messenger (Audio)' (wasapi_process_output_capture)
22:46:39.603: - scene 'Streaming':
22:46:39.603: - source: 'Doom Classic' (game_capture)
22:46:39.603: - scene 'Test':
22:46:39.603: - source: 'Audio Output Capture' (wasapi_output_capture)

L2?
19:47:56.866: Loaded scenes:
19:47:56.866: - scene 'Scene':
19:47:56.866: - source: 'The Messenger' (game_capture)
19:47:56.866: - source: 'The Messenger (Audio)' (wasapi_process_output_capture)
19:47:56.866: - scene 'Streaming':
19:47:56.866: - source: 'Dusk' (game_capture)
19:47:56.866: - source: 'Lethal Company' (game_capture)
19:47:56.866: - source: 'Doom (2016)' (game_capture)
19:47:56.866: - source: 'Doom Eternal' (game_capture)
19:47:56.866: - scene 'Test':
19:47:56.866: - source: 'Audio Output Capture' (wasapi_output_capture)

Hi, sorry for the late reply. Yesterday, I couldn't test anything.

I deleted a bunch of redundant sources, and ran a test with what you suggested. It looks good, but since you mentioned memory leaks last time, I'm afraid those are still an issue. I think I will update my drivers regardless. On that note, I was suggested by some friends to switch to software encoder (CPU encoder, from what I understand) because, as you suggested, AMD GPU encoder is a hit or miss, and that might be messing with it. Could that make things better/more consistent?

Also, is it possible I was having random, freak-accident type of memory leaks and that after a couple of days, it's working fine?

Again, thank you so much for the help, I really appreciate it! And sorry for my ignorance.

 

[rockbottom]

Improvement, moving in the right direction.

I only get memory leaks with OBS when using certain plugins. If I don't use them, no leaks. I didn't see any plugins installed in your log but think there's a possibility that your leak may be coming from the GL error. Update the driver, hopefully the error & the leak are history.

21:36:00.506: [game-capture: 'Doom Classic'] gl_free: GL error occurred on free: 1282

22:46:18.725: Number of memory leaks: 1

 

[Franciscop98]

Again, sorry for the late reply! I've been really busy this week, but I could dedicate more time this weekend to solve this issue definitively (unless there's no solution other than a new GPU)

So, this is a new log for today. It seems I'm still getting that GL error, and I still have a memory leak somewhere. I updated my drivers, but haven't changed anything other than that. And I tried to do the appropriate legwork, but there doesn't seem to be a dedicated or recommended driver for AMD, other than the newest. I could try hardware encoder, but I don't know if that'd be the best solution.

 

[rockbottom]

Yeah, i see it. Try rolling back to AMD driver 24.8.1 & see if things improve. I've been helping other people with AMD GPU's this week. Both were having trouble encoding H264 with drivers 24.10.1 & 24.9.1 that you have installed. Rolling back cleared it up.

All videos corrupting - GPU failure?

Good day everyone, I've been using OBS for a few years to record but exactly 2 and a half weeks ago I ran into an issue where all my videos started corrupting. Think green artifacts, morphing, etc. I've attached a sample of what it looks like. Now, I've been trying to fix it with a lot of...

obsproject.com

 

[Franciscop98]

Yeah, i see it. Try rolling back to AMD driver 24.8.1 & see if things improve. I've been helping other people with AMD GPU's this week. Both were having trouble encoding H264 with drivers 24.10.1 & 24.9.1 that you have installed. Rolling back cleared it up.

All videos corrupting - GPU failure?

Good day everyone, I've been using OBS for a few years to record but exactly 2 and a half weeks ago I ran into an issue where all my videos started corrupting. Think green artifacts, morphing, etc. I've attached a sample of what it looks like. Now, I've been trying to fix it with a lot of...

obsproject.com

Alright, I'll revert the drivers and try once again, and report back

 

[rockbottom]

Updated, rollback, like I said hit or miss. 24.8.1 was a hit twice so far.

 

[Franciscop98]

I had to revert to AMD drivers 24.3.1 because for RX 580 24.8.1 isn't compatible. 24.3.1 is the latest previous driver (If there's a way to force 24.8.1, I don't know it, and I couldn't even find a vega/polaris 24.8.1 driver, only rdna).

That being said, I still seem to have the memory leak. Also anecdotal, but even tho I went for the balanced preset instead of the speed preset, the video quality seems incredibly more grainer and blurrier. Ran a quick test.

Another anecdotal thing is that I tried with software encoder, and the quality seemed to be much lower, so I don't think that can be a permanent solution (also, the memory leak is still there).

I'm truly at a loss here. I'm not sure it's a driver issue at this point, but at the same time, I just have no idea what else it could be.

 

[rockbottom]

Some info I found on the GL error. Something went wrong/invalid operation. You're going to need to troubleshoot it. One suggestion was to create a new Scene Collection.

Question / Help - Inexplicable Capture lags on OpenGL games

Okay since the arrival of that bloody update I can't stream some of my games properly anymore... By that I mean that I always managed to find a mix of settings that allowed me to stream at a solid 60 FPS Unfortunately given I didn't backup the logs of the previous state of things you'll have...

obsproject.com

gl_free: GL error occurred on free: 1282 - Google Search

Recording now, not streaming. Try

00:46:31.737: rate_control: CBR >CQP
00:46:31.737: bitrate: 2500
00:46:31.737: cqp: 20 > 15-20
00:46:31.737: keyint: 250 > 2 Seconds
00:46:31.737: preset: balanced
00:46:31.737: profile: high
00:46:31.737: b-frames: 0
00:46:31.737: width: 1360
00:46:31.737: height: 768
00:46:31.737: params: (none)
00:46:31.745: [game-capture: 'Game Capture'] attempting to hook process: gzdoom.exe
00:46:31.756: ---------------------------------
00:46:31.756: [FFmpeg aac encoder: 'Track1'] bitrate: 160, channels: 2, channel_layout: stereo
00:46:31.756:
00:46:31.787: ==== Recording Start ===============================================
00:46:31.787: [ffmpeg muxer: 'adv_file_output'] Writing file 'C:/Users/franc/Videos/2024-11-02 00-46-31.mkv'...
00:46:32.861: [game-capture: 'Game Capture'] capture stopped
00:46:35.762: [game-capture: 'Game Capture'] attempting to hook process: gzdoom.exe
00:46:35.778: [game-capture: 'Game Capture'] capture stopped
00:46:39.778: [game-capture: 'Game Capture'] attempting to hook process: gzdoom.exe
00:46:39.800: [game-capture: 'Game Capture'] gl shared texture capture successful
00:46:39.811: [game-capture: 'Game Capture'] shared texture capture successful
00:46:39.811: [win-wasapi: 'Game Capture (Audio)'] update settings:
00:46:39.811: executable: gzdoom.exe
00:46:39.811: title: Hell Beneath - The Ultimate DOOM
00:46:39.811: class: MainWindow
00:46:39.811: priority: 0
00:46:40.651: WASAPI: Device '[VIRTUAL_AUDIO_DEVICE_PROCESS_LOOPBACK]' [48000 Hz] initialized (source: Game Capture (Audio))
00:46:40.660: Device '[VIRTUAL_AUDIO_DEVICE_PROCESS_LOOPBACK]' invalidated. Retrying (source: Game Capture (Audio))
00:46:40.661: WASAPI: Device '[VIRTUAL_AUDIO_DEVICE_PROCESS_LOOPBACK]' [48000 Hz] initialized (source: Game Capture (Audio))
00:50:56.134: [ffmpeg muxer: 'adv_file_output'] Output of file 'C:/Users/franc/Videos/2024-11-02 00-46-31.mkv' stopped
00:50:56.134: Output 'adv_file_output': stopping
00:50:56.134: Output 'adv_file_output': Total frames output: 15849
00:50:56.134: Output 'adv_file_output': Total drawn frames: 15857 (15861 attempted)
00:50:56.134: Output 'adv_file_output': Number of lagged frames due to rendering lag/stalls: 4 (0.0%)
00:50:56.135: ==== Recording Stop ================================================
00:50:56.135: Video stopped, number of skipped frames due to encoding lag: 4/15859 (0.0%)

 

[rockbottom]

This is from the release notes for driver 24.3.1, franc looks OK but you never know.

Known Issues​

• Shader caching may fail for Windows usernames containing accented characters.

 

[Franciscop98]

Alright, now I got plenty of time to get down to business.

Ran a new test today. Did almost all of your recommendations from the other message, except keyint because I read online for recording specifically it's better to leave it on auto instead of 2 seconds, but I can be persuaded on the contrary. I also did a bit of changes of my own, went back to the speed preset but upped the bitrate quite a bit. I realized that was probably what caused the previous 2 recordings to be so blurry (I don't know why it went down to 2500, or when, but it looks much better now.)

Honestly, it doesn't look too bad now, and I didn't get that horrible thing that started all of this, but I STILL got a memory leak. I am starting to think I'll just have to live with it.

If you see anything still wrong with the log (maybe something that'll be a problem in the future, like skipped frames due to overloading or something) let me know. I greatly appreciate the help, but I feel a bit bad that I got you on a wild goose chase that doesn't seem to have an end. (I tend to have random tech problems that are unfixable, 1 in a million chance of happening).