Bug Report Massive desktop lag when OBS-MP is open

dudist

New Member
EDIT: Jim explains the issue I was having in the next post. Thanks again Jim for being responsive and helpful!

tl;dr Display Capture is the culprit behind the freezing for me and it might have been because of a few different reasons. If I had to guess it'd be graphics drivers, since that was the latest driver update I've done (Nvidia 358.50.) Again though, it's a guess so not 100%. Anyways, for now I'll just avoid Display Capture unless I really need it.

Original post:

I use OBS-MP for local recordings of gameplay. Seemingly out of nowhere, my entire desktop starts to intermittently freeze up completely while I have OBS-MP open and, curiously, the recorded video has no skipped frames. Alt-tabbing has a noticeable delay of anywhere from 2 - 8 seconds, and clicking start can take up to 4 seconds to register, but only while OBS-MP is running.

As I'm sure anybody can imagine, this behavior is highly irritating and frustrating. I have no idea what may have caused this. (Driver updates? OBS-MP updates?) Either way, it's only started doing this in maybe the past 2 - 3 weeks. My system is more than capable of recording with OBS-MP with my chosen settings and has done so without issue in the past couple of months.

OBS-MP reports 1 - 2% cpu usage , and task manager doesn't show anything out of the ordinary either, yet my entire system chugs.

1000 kb/s Bitrate, Custom Buffer Size = 0, crf = 18.

Sorry if I've failed to provide any other relevant details. Any help would be really appreciated.
 

Attachments

  • 2015-10-12 18-45-27.txt
    17.8 KB · Views: 25
Last edited:

Lain

Forum Admin
Lain
Forum Moderator
Developer
He came by chat, this actually turned out to be caused by display capture on windows 10 with his particular setup. Removed the display capture and started using the other capture methods, and everything was fine. Not sure if it was caused by the drivers, by microsoft's changes to display capture on windows 10, or what it might have ultimately been caused by, but it did seem to come from display capture in general, so it's something to make note of. (Windows 8/10+ display capture is entirely handled by microsoft and drivers, so it's almost assuredly a driver, hardware, or microsoft/nvidia issue of some sort)
 
Top