obsproject / obs-studio

OBS Studio - Free and open source software for live streaming and screen recording
https://obsproject.com
GNU General Public License v2.0
58.79k stars 7.83k forks source link

Opening settings panel causes performance to tank #6661

Open Awpii opened 2 years ago

Awpii commented 2 years ago

Operating System Info

Windows 11

Other OS

No response

OBS Studio Version

27.2.4

OBS Studio Version (Other)

No response

OBS Studio Log URL

https://obsproject.com/logs/NFpgi6s3RY18DsrR

OBS Studio Crash Log URL

No response

Expected Behavior

Game streams at 60 FPS with no frame drops due to rendering lag

Current Behavior

Frames missing due to rendering lag, low fps and high average frame render times.

Steps to Reproduce

  1. Open OBS
  2. Open an application to capture in fullscreen (happening with videogames in my case)
  3. Switch to OBS and open the settings menu
  4. Close the settings menu and go back to the application
  5. Look at OBS stats, frames start dropping due to rendering lag. ...

Alternatively, if I never click settings, game streams at 60FPS just fine without any issues. I was able to reproduce this issue 10/10 times.

Anything else we should know?

You can contact me in discord Awpii#1507 for any further details.

Awpii commented 2 years ago

Worth noting: was told it could be caused by GHUB installing a plugin for OBS, tried on a different computer with equal specs but no logitech software or hardware and the issue was still there, even with the plugin file not present in the plugins folder.

RytoEX commented 2 years ago

So far, I am unable to reproduce this on an i7-7700HQ + GTX 1060 system at 1080p60. Please provide a full log, complete with an encoding session.

Please note that render lag when alt-tabbing in and out of fullscreen games is normal. Render lag while Settings is opening could be expected if you have a large scene collection.

  1. Does OBS continue lagging frames after Settings has finished opening?
  2. Does OBS continue lagging frames after you close Settings?
  3. Have you tried to reproduce this without the Logitech plugin present?
  4. Have you tried to reproduce this in a clean scene collection with nothing in it?
Awpii commented 2 years ago

So far, I am unable to reproduce this on an i7-7700HQ + GTX 1060 system at 1080p60. Please provide a full log, complete with an encoding session.

Please note that render lag when alt-tabbing in and out of fullscreen games is normal. Render lag while Settings is opening could be expected if you have a large scene collection.

  1. Does OBS continue lagging frames after Settings has finished opening?
  2. Does OBS continue lagging frames after you close Settings?
  3. Have you tried to reproduce this without the Logitech plugin present?
  4. Have you tried to reproduce this in a clean scene collection with nothing in it?

Hi Ryan, thanks for replying!

1) Yes, OBS continues lagging frames once the settings menu has opened 2) Yes, OBS continues lagging after closing settings 3) Yes, I tried on a system that has the same components except for all the logitech hardware and GHUB and the problem was still present 4) I'm not sure I know what a "Clean Scene collection is"

Also, render lag is present throughout the whole session once I've opened the settings menu once and it will remain like that until I restart OBS.

What do you mean by "Full log complete with an encoding session?"

RytoEX commented 2 years ago

I'm not sure I know what a "Clean Scene collection is"

A new, empty scene collection with nothing in it. No scenes. No sources. At most, a color source or something else minimal and static, such as a single, non-animated image source using a small image file. This helps rule out existing sources as a contributing factor.

What do you mean by "Full log complete with an encoding session?"

  1. Restart OBS
  2. Start your stream/recording for at least 30 seconds (or however long it takes for the issue to happen). Make sure you replicate any issues as best you can, which means having any games/apps open and captured, etc.
  3. Stop your stream/recording.
  4. Select Help > Log Files > Upload Current Log File. Copy the URL and paste it here.

For the record, these things would be covered by going through our normal support channels, either on Discord or the forums. In the future, we recommend going through the support channels before filing a GitHub Issue to discern whether to not something is likely to be a bug. Going through this process also ensures that all the information required to investigate a possible bug is made available in a GitHub Issue from the beginning.

Awpii commented 2 years ago

I'm not sure I know what a "Clean Scene collection is"

A new, empty scene collection with nothing in it. No scenes. No sources. At most, a color source or something else minimal and static, such as a single, non-animated image source using a small image file. This helps rule out existing sources as a contributing factor.

What do you mean by "Full log complete with an encoding session?"

  1. Restart OBS
  2. Start your stream/recording for at least 30 seconds (or however long it takes for the issue to happen). Make sure you replicate any issues as best you can, which means having any games/apps open and captured, etc.
  3. Stop your stream/recording.
  4. Select Help > Log Files > Upload Current Log File. Copy the URL and paste it here.

For the record, these things would be covered by going through our normal support channels, either on Discord or the forums. In the future, we recommend going through the support channels before filing a GitHub Issue to discern whether to not something is likely to be a bug. Going through this process also ensures that all the information required to investigate a possible bug is made available in a GitHub Issue from the beginning.

Hi, first of all, apologies for my rush into reporting this. I understand it can be troublesome.

I did try with a completely blank scene (nothing at all, not even a source) and I was not able to replicate the issue while recording, here's the log: https://obsproject.com/logs/g_4LifxtA4b9tc3z

I did try also with only a single source (a game - Assetto Corsa) and I was able to reproduce the issue, which was much worse while recording but I assume that's because I haven't really tuned my recording settings: https://obsproject.com/logs/YWEESa5aR5ci3EOp

Hope it helps!