Question / Help High number of missed frames from rendering lag, but little CPU/GPU usage

S

scatterclegge

New Member
Hi, I have an LGX2 HD capture card. Unfortunately whenever I try to stream or record with it through OBS, there's an insufferable amount of missed frames due to rendering lag, around 5%. This is very noticeable and is more than I've seen any other streamers have. I have decent hardware, a GTX 960 and an i5-4690. They're a few years old now but should be able to handle 1080p60 video. I'm using NVENC encoding and tried every preset, from max quality to max performance, with little difference. If I look at task manager during this, I see about 20-30% usage on my CPU and about 5-20% on my GPU, so I don't think either is bottlenecking me. I updated my drivers (audio, chipset,and video) and the issue remains. Log file from a short session where I tried recording from the LGX2 (I can upload the video if necessary): https://obsproject.com/logs/bgnIXjSqlaCng9bj
 
S

scatterclegge

New Member
Is it possible I have too many sources? It looks like quite a bit in that log file. I was under the impression that they were unloaded when not in view. My LGX2 scene only has 4 sources in it. Should I tidy up my scenes? (I'll try when I get home either way)
 
Narcogen

Narcogen

Active Member
Yes, it is possible to have too many sources.

22:52:02.737: Windows Version: 10.0 Build 17134 (revision: 829; 64-bit)

Windows is out of date and a broken feature is on by default that degrades OBS performance. See the link at the bottom; you should update Windows.

You're running 3 displays on a single 960. Are they all at the same refresh rate?

22:52:03.236: Adapter 0: NVIDIA GeForce GTX 960
22:52:03.236: Dedicated VRAM: 4250206208
22:52:03.236: Shared VRAM: 4260864000
22:52:03.236: output 0: pos={0, 0}, size={1920, 1080}, attached=true
22:52:03.236: output 1: pos={1920, 0}, size={1920, 1080}, attached=true
22:52:03.236: output 2: pos={792, -1080}, size={1920, 1080}, attached=true

22:52:11.479: adding 46 milliseconds of audio buffering, total audio buffering is now 92 milliseconds (source: blue yeti)
22:52:21.690: adding 23 milliseconds of audio buffering, total audio buffering is now 116 milliseconds (source: blue yeti)
22:53:02.663: adding 46 milliseconds of audio buffering, total audio buffering is now 162 milliseconds (source: blue yeti)
22:53:43.579: adding 46 milliseconds of audio buffering, total audio buffering is now 208 milliseconds (source: blue yeti)

Increasing audio buffering on a USB device indicates either bus overload or general machine overload. 200 isn't terrible, but it isn't great, either.

22:56:30.894: Output 'adv_file_output': Number of lagged frames due to rendering lag/stalls: 43 (3.5%)

Rendering lag caused by GPU overload.

https://obsproject.com/wiki/GPU-overload-issues

22:56:30.895: Video stopped, number of skipped frames due to encoding lag: 48/1219 (3.9%)

Encoder overload.

https://obsproject.com/wiki/General-Performance-And-Encoding-Issues
 
S

scatterclegge

New Member
I updated windows and it seems MUCH better now, or at least it did at first. After running it for about 5 minutes (not recording or streaming, just having the scene open) it went back to stuttering. It's not quite as bad as it was before, but still quite bad. After about 10 minutes total, frames missed due to rendering lag are at about 1.2%, and it seems to be holding steady there. This is also after I deleted as many scenes/sources as possible (with, notably, no Display Capture sources anymore). I also tried recording a short video, and it got worse still. Here's the new logfile if anything still stands out to you. https://obsproject.com/logs/Yt08cRHcRoo_UqPV
 
You must log in or register to reply here.
Top