Question / Help OBS Local Recording Overloaded (Need Help)

[Scenarika]

So I usually use OBS for recording my audio (game audio, discord, my voice) while I let AMD Relive record my gameplay but recently Relive has been really lagging and desyncing my audio so I figured I'd give OBS a shot. I do use OBS for recording console gameplay with my Razer Ripsaw and it works fine at a 50,000 bitrate with the AVC encoder with VBR going. I mainly record games like Siege and PUBG (FPP) on my PC and never usually have issues with Relive but my OBS always says encoder is overloaded! So as I don't know much about OBS I was wondering if anyone could help me out? Also I record at 1080p 60fps and I can't do 1080p 30fps or 720p 60fps for recording videos.

My current specs are:
CPU: Intel Core i5 8400 (6 Cores/6 Threads)
CPU Cooler: Arctic Freezer 33 eSports Edition (Black/White)
Motherboard: ASRock Z370 Taichi (Bought it with an i7 8700k in mind but I couldn't get my hands on one at the time)
RAM: Adata XPG Spectrix D41 16GB 2x8 DDR4-2666 (Dual Channel)
Storage: Seagate Barracuda 1TB 7200 RPM HDD
Western Digital Caviar Green 1TB 5400 RPM HDD
Seagate Backup Plus Hub 4TB External HDD
GPU: Asus Radeon R9 280x 3GB DirectCU II
PSU: Thermaltake Toughpower Grand RGB 650W 80+ Gold
Case: NZXT H700i Black (It's a large case with plenty of airflow and I have a lot of fans in it so overheating isn't an issue)

My specs aren't too bad so I don't see why I'm having an issue with OBS. Only other option I could think of is the GPU is quite old but I record with Relive at 1080p 60fps 50,000 bitrate on it so it shouldn't be an issue.

I have a logfile here to hopefully be of some use.

https://obsproject.com/logs/D11-QH2SQaY_O6rp

If anyone can help me it would be most appreciated! Thank you in advanced!

Edit: The above part where it says:
video settings reset:
08:30:19.508: base resolution: 1920x1080
08:30:19.508: output resolution: 640x360
08:30:19.508: downscale filter: Bicubic
08:30:19.508: fps: 60/1
08:30:19.508: format: NV12
08:30:19.508: YUV mode: 709/Partial
08:30:19.508: Audio monitoring device:
08:30:19.508: name: Default
08:30:19.508: id: default

That's from when I was recording audio only and I had no issues with it, it ended up in the log somehow anyways.

 

[Scenarika]

Bump

 

[Narcogen]

You can't record "audio only", OBS is always recording a video stream, even if all you're giving it is an empty frame.

I am not familiar with the AMF encoder but the logfile suggests that you are, in fact, significantly overloading it with the settings you've chosen. You're asking a 280 to encode 1080p60 and it looks to me like it can't.

08:31:21.976: video settings reset:
08:31:21.976: base resolution: 1920x1080
08:31:21.976: output resolution: 1920x1080
08:31:21.976: downscale filter: Bicubic
08:31:21.976: fps: 60/1
08:31:21.976: format: NV12
08:31:21.976: YUV mode: 709/Partial
08:31:21.982: Settings changed (outputs, video)

08:54:22.035: [AMF] <Id: 7> Initial Frame Latency is 77494000 nanoseconds.
08:54:22.262: [AMF] <Id: 7> No output Packet, encoder is overloaded!
08:54:22.313: [AMF] <Id: 7> No output Packet, encoder is overloaded!
08:54:22.365: [AMF] <Id: 7> No output Packet, encoder is overloaded!
08:54:22.419: [AMF] <Id: 7> No output Packet, encoder is overloaded!
08:54:22.470: [AMF] <Id: 7> No output Packet, encoder is overloaded!
08:54:22.523: [AMF] <Id: 7> No output Packet, encoder is overloaded!
08:54:22.575: [AMF] <Id: 7> No output Packet, encoder is overloaded!
08:54:22.629: [AMF] <Id: 7> Input Queue is full, encoder is overloaded!

I would try 1080p30 or 720p60 and see if either mode performs better, or perhaps try the x264 encoder and see what results that gives you.

 

[Scenarika]

You can't record "audio only", OBS is always recording a video stream, even if all you're giving it is an empty frame.

I am not familiar with the AMF encoder but the logfile suggests that you are, in fact, significantly overloading it with the settings you've chosen. You're asking a 280 to encode 1080p60 and it looks to me like it can't.

08:31:21.976: video settings reset:
08:31:21.976: base resolution: 1920x1080
08:31:21.976: output resolution: 1920x1080
08:31:21.976: downscale filter: Bicubic
08:31:21.976: fps: 60/1
08:31:21.976: format: NV12
08:31:21.976: YUV mode: 709/Partial
08:31:21.982: Settings changed (outputs, video)

08:54:22.035: [AMF] <Id: 7> Initial Frame Latency is 77494000 nanoseconds.
08:54:22.262: [AMF] <Id: 7> No output Packet, encoder is overloaded!
08:54:22.313: [AMF] <Id: 7> No output Packet, encoder is overloaded!
08:54:22.365: [AMF] <Id: 7> No output Packet, encoder is overloaded!
08:54:22.419: [AMF] <Id: 7> No output Packet, encoder is overloaded!
08:54:22.470: [AMF] <Id: 7> No output Packet, encoder is overloaded!
08:54:22.523: [AMF] <Id: 7> No output Packet, encoder is overloaded!
08:54:22.575: [AMF] <Id: 7> No output Packet, encoder is overloaded!
08:54:22.629: [AMF] <Id: 7> Input Queue is full, encoder is overloaded!

I would try 1080p30 or 720p60 and see if either mode performs better, or perhaps try the x264 encoder and see what results that gives you.

Thanks for the reply! When I said "audio only" I meant I capture a black screen at the lowest resolution I can go just to get the separate audio tracks so technically I'm still recording audio only. I tried 1080p 30fps and 720p 60fps as well as x264 (even though for my YT channel I don't want to go under 1080p 60fps). I can't find a reason for the R9 280x to not record 1080p since it usually records just fine in Relive at 1080p 60fps with a 50,000 bitrate. OBS isn't that great of a software for recording my PC apparently so I think I'll continue with Relive since it actually works and with a very little performance hit unlike OBS. Siege is the only game that the audio desyncs which is odd since PUBG never has that issue, I'll just sync the audio where it should be when I'm editing my videos for now. I'm getting an EVGA RTX 2070 soon so hopefully I won't have issues in OBS with that. Thanks for your help though!

 

[koala]

The AMD encoder is running on the GPU and needs GPU resources for encoding. If the GPU is already fully loaded with rendering some game, the encoder may starve from computing resources and exhibit the behavior you see. You can try to limit the game's fps to free up resources. If Relive does not suffer as much as OBS from this, it may be that it (as part of the GPU driver) uses some kind of privileged operation that OBS isn't able to use that boosts the priority of the encoding part.

With a Nvidia GPU, such a problem does not exist, or at least it's not that severe, because its hardware encoder (nvenc) is a dedicated hardware circuit on the GPU chip. It does not require GPU computing resources shared with a game or whatever is running on the GPU at the same time.

 

[Scenarika]

The AMD encoder is running on the GPU and needs GPU resources for encoding. If the GPU is already fully loaded with rendering some game, the encoder may starve from computing resources and exhibit the behavior you see. You can try to limit the game's fps to free up resources. If Relive does not suffer as much as OBS from this, it may be that it (as part of the GPU driver) uses some kind of privileged operation that OBS isn't able to use that boosts the priority of the encoding part.

With a Nvidia GPU, such a problem does not exist, or at least it's not that severe, because its hardware encoder (nvenc) is a dedicated hardware circuit on the GPU chip. It does not require GPU computing resources shared with a game or whatever is running on the GPU at the same time.

Sorry for how late I am on this, but I think that's definitely what it is. Nvidia is way better than AMD for sure, but I got the GPU for free so I can't really complain that much. But because of the new AMD drivers I got the blue screen of death and apparently had no restore points so I had to wipe my PC and reinstall Windows 10 because of it. I do have my FPS uncapped on all games and always have at the very least 90 FPS on the games I play with competitive settings, since I'm only running a 60Hz monitor I should probably start capping though. I'm getting an RTX 2070 soon though so hopefully that'll fix my problem! Thanks for the response!