Question / Help OBS FPS dropping even when not streaming on an empty scene: Dedicated streaming PC, dropped frames remain at 0%

[TheGameMechanics]

Hello!

So I have had this problem for a while, about 3 months.. and it's gotten progressively worse, I think.

I get drops from 60fps to 28, up to 60, down to 37, up to 60 etc the drop number is always random, it's pretty persistent, and even if i drop my capture to 30fps, it then drops further again. My CPU & GPU are not stressed, my GPU is a 750ti and is up to date. I've also tried a 1050ti and the problem persisted.

NOTE: I am running a dual PC setup, this problem is on the streaming PC. The streaming PC is dedicated and has no other programs running in this experiment except OBS, even without hitting the streaming button, it is reading at varying fps in the bottom right hand corner.

I've yet to rule out the SSD, doing health checks on it as we speak, but it shows no other signs of issue outside of OBS, so I am not sure it is that.

I've tried an empty scene, i've deactived the Elgato HD60 Pro, my webcam, disabled the preview, reduced OBS video settings (even though I'm not streaming when this is happening) updating GPU drivers, checking network settings (again, feels pointless when this is an issue happening while not even online). Nothing seems to change the drops. It feels like it's OBS Studio related. I am on the latest version, and the latest version of Windows 10 as well, 64bit pro edition.

One persistent message that continues to pop up is:

"warning: Could not update timestamps for discarded samples."

I've attached the log, and I'm at my wits end, so any advice to fixing this would be greatly appreciated.

 

[TheGameMechanics]

Since I've been going through the forums frequently, looking for answers - I see that some folks insist on it being uploaded to a 3rd party website, so here is the log on a drive link:

https://drive.google.com/file/d/1llX8ZbrXoMxhaOiQStj1MkHG8dC00YFP/view?usp=sharing

I'm getting these FPS drops on an EMPTY scene as well btw, while not streaming. No dropped frames, the FPS counter just keeps dipping and going back up to 60 FPS. Same if I reduce it to 30 FPS.

 

[Osiris]

You have quite a lot of videos running in the background and you also have a ton of scenes, surely that can be chopped up into Scene collections?
Remember that a lot of sources are running even when they are not the active scene.

 

[TheGameMechanics]

Hi @Osiris - first off, thanks for your reply!

Would checking the "close file when inactive" box on each of these sources not stop sources from running? I have that set on all of them, I'm fairly sure.

EDIT: I will def check out Scene Collections properly and learn how to use it, as you are right, I've buttload of scenes.

EDIT 2: Upon removing over half of my scenes in a duplicate, I am still seemingly getting the fps drops.

 

[TheGameMechanics]

moving between Scene Collections is a bit janky, not really ideal for live streaming, so leaving that for now, and just downsized a lot of sources and scenes. Still confused by the highlighted text that persistently pops up in my log, almost spams it throughout each log, whether live or not.

"warning: Could not update timestamps for discarded samples."

Any more information would be greatly appreciated.

 

[TheGameMechanics]

Bump - would love to know why it spams the above message in my log. Anybody have an idea?

 

[TheGameMechanics]

Bump, anybody have a look at the log and give me an idea what might be going on? Feels mad that OBS is dropping frames when it's a) not streaming and b) not being overloaded by GPU CPU or SSD constraints.

 

[RytoEX]

warning: Could not update timestamps for discarded samples.

This is a warning from FFmpeg when decoding media. My first guess would be a specific file (or files) is giving FFmpeg trouble on decode.

It would be easier to review the log if it wasn't 6000 lines before the scene collection has loaded, but here we go.

11:31:12.979: Output 'adv_stream': Number of lagged frames due to rendering lag/stalls: 408 (11.0%)
[...]
11:31:32.999: Output 'adv_stream': Number of lagged frames due to rendering lag/stalls: 106 (9.9%)
[...]
12:13:46.771: Output 'adv_stream': Number of lagged frames due to rendering lag/stalls: 17535 (11.5%)
[...]
12:15:54.949: Output 'adv_stream': Number of lagged frames due to rendering lag/stalls: 132 (4.1%)

Lagged frames are distinctly different from dropped frames, which is why the dropped frames percent is 0% - they aren't the same. Lagged frames are strictly a rendering issue, which is why you also see it occur while offline. This issue is generally GPU overload, which isn't surprising given the amount of stuff you're asking it to do. Every rendered source has a GPU cost. Media Sources and Browser Sources can be particularly demanding. Filters require resources too, and you have a lot of them.

If you can provide a log with lagged frames with an empty scene collection, or at least a vastly reduced one, then that could shed some more light on this. With the information currently available, GPU/system overload or resource shortage seems most likely.

 

[Aaron Hopkins]

Hello!

So I have had this problem for a while, about 3 months.. and it's gotten progressively worse, I think.

I get drops from 60fps to 28, up to 60, down to 37, up to 60 etc the drop number is always random, it's pretty persistent, and even if i drop my capture to 30fps, it then drops further again. My CPU & GPU are not stressed, my GPU is a 750ti and is up to date. I've also tried a 1050ti and the problem persisted.

NOTE: I am running a dual PC setup, this problem is on the streaming PC. The streaming PC is dedicated and has no other programs running in this experiment except OBS, even without hitting the streaming button, it is reading at varying fps in the bottom right hand corner.

I've yet to rule out the SSD, doing health checks on it as we speak, but it shows no other signs of issue outside of OBS, so I am not sure it is that.

I've tried an empty scene, i've deactived the Elgato HD60 Pro, my webcam, disabled the preview, reduced OBS video settings (even though I'm not streaming when this is happening) updating GPU drivers, checking network settings (again, feels pointless when this is an issue happening while not even online). Nothing seems to change the drops. It feels like it's OBS Studio related. I am on the latest version, and the latest version of Windows 10 as well, 64bit pro edition.

One persistent message that continues to pop up is:

"warning: Could not update timestamps for discarded samples."

I've attached the log, and I'm at my wits end, so any advice to fixing this would be greatly appreciated.

HELLO! I have been having the EXACT same issue as you! Even when i am NOT streaming OR recording, i still see the frame skip. I will share with you my file log as well. I have recently just upgraded to a GTX 1080 to attempt to combat this, and I STILL get the rendering lag. Something is not quite right here.

18:33:06.772: Output 'adv_file_output': Number of lagged frames due to rendering lag/stalls: 32 (2.4%)

This is the main line to pay attention to. And like you I too have a lot of scenes and sources and filters. However, my GPU load is staying relatively low whilst recording, such as 21%. I am using NVENC as my encoder setting, and I am using a dual PC stream set up. OBS PC capturing the screen of the gaming PC.

https://obsproject.com/logs/Y7tPhVlqKu-wHEu7

I have tried all sorts. Windows roll back. updating GPU drivers. upgraded from a gtx 960 to a gtx 1080 to eliminate that. Disk defrag. Even removing scenes and sources and filter to help it. And even though I am taking away sources, filters and scenes and progressing making my stream more basic (even though i don't really want to make my stream more basic), it STILL isn't eliminating this random lag spike. It also isn't skipped frames at all due to encoding but it is saying lagged frames due to rendering.

I'm happy I found someone with the same issue, at least. (even though I don't know how to fix it!)

 

[Aaron Hopkins]

You have quite a lot of videos running in the background and you also have a ton of scenes, surely that can be chopped up into Scene collections?
Remember that a lot of sources are running even when they are not the active scene.

I have even tried a test with no capture card. and no webcam on at all. and it still has the issues. so it cant be the capture card or the webcam devices. I have un installed the webcam device from the PC and de activated the video capture card (elgato HD 60 pro). (also: idk if can take a look at my post above this one as well). Really struggling with this random frame render lag issue.

 

[Narcogen]

You have over 1-2 dozen video sources in the same scene, all with hardware decoding on. The log says your GPU is overloaded.

I would start with a blank scene collection verify that the rendering lag goes away, and then start adding elements and see if/when it returns. It might be that you've simply got too many video sources, or maybe one or more of them are complex enough that specific ones are problematic.

 

[Aaron Hopkins]

Hello!

So I have had this problem for a while, about 3 months.. and it's gotten progressively worse, I think.

I get drops from 60fps to 28, up to 60, down to 37, up to 60 etc the drop number is always random, it's pretty persistent, and even if i drop my capture to 30fps, it then drops further again. My CPU & GPU are not stressed, my GPU is a 750ti and is up to date. I've also tried a 1050ti and the problem persisted.

NOTE: I am running a dual PC setup, this problem is on the streaming PC. The streaming PC is dedicated and has no other programs running in this experiment except OBS, even without hitting the streaming button, it is reading at varying fps in the bottom right hand corner.

I've yet to rule out the SSD, doing health checks on it as we speak, but it shows no other signs of issue outside of OBS, so I am not sure it is that.

I've tried an empty scene, i've deactived the Elgato HD60 Pro, my webcam, disabled the preview, reduced OBS video settings (even though I'm not streaming when this is happening) updating GPU drivers, checking network settings (again, feels pointless when this is an issue happening while not even online). Nothing seems to change the drops. It feels like it's OBS Studio related. I am on the latest version, and the latest version of Windows 10 as well, 64bit pro edition.

One persistent message that continues to pop up is:

"warning: Could not update timestamps for discarded samples."

I've attached the log, and I'm at my wits end, so any advice to fixing this would be greatly appreciated.

You have over 1-2 dozen video sources in the same scene, all with hardware decoding on. The log says your GPU is overloaded.

I would start with a blank scene collection verify that the rendering lag goes away, and then start adding elements and see if/when it returns. It might be that you've simply got too many video sources, or maybe one or more of them are complex enough that specific ones are problematic.

I FOUND THE ANSWER! When I build up OBS from scratch again. The 1 and only thing that caused the terrible frame jump was none other than...... Ticking the "outline" box within text properties on a text source!

For the love of all that is holy, please DO NOT tick the "outline" box on your text properties. This is what caused it. I am not back to 100% smooth as butter. Even with all of the sources and scenes. Thank you.

 

[Narcogen]

I am guessing you may have a bad font. I use the outline feature regularly and haven't seen this issue.

 

[JohnnyRingo]

I FOUND THE ANSWER! When I build up OBS from scratch again. The 1 and only thing that caused the terrible frame jump was none other than...... Ticking the "outline" box within text properties on a text source!

For the love of all that is holy, please DO NOT tick the "outline" box on your text properties. This is what caused it. I am not back to 100% smooth as butter. Even with all of the sources and scenes. Thank you.

Aaron if I could give you a hug across the internet... I would. I too was suffering this problem for a while now and had absolutely no clue what was going on. I went high and low across all the suggestions on the forums and did every trick in the book from new / alternate drivers, windows roll-backs, switching pcie slots, swapping cables and removing all usb devices and scenes.

I also have an El Gato HD60 PRO on a GTX 1060 dedicated streaming computer. I was getting absolutely random "Frames missed due to rendering lag" even when OBS was idle and had no other programs running nor any input from the gaming pc (in other words nothing connected to the El Gato). I took your advice and not only removed "outline" from my text sources - but I removed every single text (GDI+) in any of my scenes.

Behold - no more random "Frames missed due to rendering lag". Smooth again - no hiccups. The pain of this absolutely random occurrence is over.

Thanks man. I hope this gets repeated somehow in future help advice threads. Remove the outline. Hell if you can - remove text GDI+. Post some text on a background and save a .jpg and use if if you need it. I'm just so glad it's over.

 

[RytoEX]

Out of curiosity, what font settings are you both using for this?

 

[JohnnyRingo]

Comic Sans MS
Montserrat Regular

A few outline settings with size 10 and opacity at 50%. Random colors selected depending on the text used.
If it also helps other folks out there who happen upon this thread - animated gifs (even if you unload them) will appear to lag out rendering frames. The heavier the size of the .gif the higher chance.

 

[RytoEX]

I'm unable to produce any noticeable render lag with just a single text source with outline enabled using Comic Sans MS. I do not have Monsterrat Regular installed.

 

[JohnnyRingo]

Thank you for looking into it anyway. This is such an obscure error and for what it's worth - I didn't have this issue for over a year before recent Windows 10 updates / Nvidia updates. As with all possible "solutions" to problems - it's just something someone can try if they're getting this specific error. It worked for me and I'm very grateful.

 

[Aaron Hopkins]

Aaron if I could give you a hug across the internet... I would. I too was suffering this problem for a while now and had absolutely no clue what was going on. I went high and low across all the suggestions on the forums and did every trick in the book from new / alternate drivers, windows roll-backs, switching pcie slots, swapping cables and removing all usb devices and scenes.

I also have an El Gato HD60 PRO on a GTX 1060 dedicated streaming computer. I was getting absolutely random "Frames missed due to rendering lag" even when OBS was idle and had no other programs running nor any input from the gaming pc (in other words nothing connected to the El Gato). I took your advice and not only removed "outline" from my text sources - but I removed every single text (GDI+) in any of my scenes.

Behold - no more random "Frames missed due to rendering lag". Smooth again - no hiccups. The pain of this absolutely random occurrence is over.

Thanks man. I hope this gets repeated somehow in future help advice threads. Remove the outline. Hell if you can - remove text GDI+. Post some text on a background and save a .jpg and use if if you need it. I'm just so glad it's over.

Out of curiosity, what font settings are you both using for this?

JohnnyRingo, you are most welcome. It took me so long to pin point the point of failure. I looked in to it pretty much 16 hours a day for about 8 days. I had to build up OBS again from scratch until the error started occurring. I'm so glad i could help somebody with this problem! It's such a crazy one. I think I will try and delete all text sources if possible. It's just some are text files for sub point goals and such like that. (the sub points text files read from text file on the hard drive). I'm over the moon I was happy to help some one else!

And the font that I am using is called perrygothic.

Good luck and happy streaming / recording!

 

[BK-Morpheus]

It definitely is an obscure error, but by simply starting with a new/empty scene- collection and adding sources step by step, this source of the problem could have been identified a lot easier :-)