Question / Help Encoding Overloaded

Exyztence

New Member
Hello!
I've been streaming on my old pc for about 2 months:
i7-6700k, GTX 970 4GB, ASUS 170-K and it was all fine, without any lags/problems/fps drops with really nice video quality.
Few days ago I decided to upgrade my PC to I9-9900k, RTX 2070 and MSI MPG Z390 GAMING CARBON AC.
Since then, there are huge lags on streams which I've never had before. I have the settings the same as before in my OBS.
I attached my logs, I really appreciate your help!
 

Attachments

  • 2020-02-28 09-48-23.txt
    14.2 KB · Views: 17

Exyztence

New Member
I will add that I have two monitors, the main one - 2560x1440 and if I have a stream, everything works smoothly. On the second - 1920x1080 I have a live preview and it stutters/lags very much.
 

Sukiyucky

Member
This shouldn't be happening on an i9-9900k and RTX 2070 super while recording:

09:48:47.428: Output 'simple_file_output': Number of lagged frames due to rendering lag/stalls: 216 (26.1%)
09:48:47.428: ==== Recording Stop ================================================
09:48:47.428: Video stopped, number of skipped frames due to encoding lag: 224/825 (27.2%)


What could be happening is you are using too many game, monitor, and window captures in one scene. Resources are allocated per each screen capture type and take up too much memory to hold their state for encoding.

09:48:25.032: - scene 'TWITCH.TV':
09:48:25.032: - source: 'Przechwytywanie ekranu 2' (monitor_capture)
09:48:25.032: - source: 'Przechwytywanie gry' (game_capture)
09:48:25.032: - source: 'Przechwytywanie okna' (window_capture)
09:48:25.032: - source: 'Ostatnie 5 donate' (browser_source)
09:48:25.032: - source: 'Cel donate' (browser_source)
09:48:25.032: - source: 'Top donate' (browser_source)
09:48:25.032: - source: 'follow etc' (browser_source)
09:48:25.032: - source: 'bits sub' (browser_source)
09:48:25.032: - source: 'donate' (browser_source)
09:48:25.032: - source: 'Przechwytywanie ekranu' (monitor_capture)
09:48:25.032: - source: 'kamerka' (image_source)
09:48:25.032: - source: 'facerig' (game_capture)
09:48:25.032: - filter: 'Kluczowanie koloru (chroma key)' (chroma_key_filter)
09:48:25.032: - source: 'napis' (image_source)
09:48:25.032: - source: 'paski' (image_source)


Instead, try making separate scenes for each screen type and setting things up in a generic manner:

For example:
  1. Intro
  2. Stage - Game Capture
  3. Stage - Window Capture
  4. Stage - Display Capture
  5. Intermission
  6. Outro
 

Exyztence

New Member
I still have these problems ;/
I see there's new nvidia driver yesterday update, Im downloading it.
If nothing helps, I will reboot my system.
 

Attachments

  • 2020-02-28 12-10-36.txt
    11.6 KB · Views: 12

Exyztence

New Member
I opened obs
This shouldn't be happening on an i9-9900k and RTX 2070 super while recording:

09:48:47.428: Output 'simple_file_output': Number of lagged frames due to rendering lag/stalls: 216 (26.1%)
09:48:47.428: ==== Recording Stop ================================================
09:48:47.428: Video stopped, number of skipped frames due to encoding lag: 224/825 (27.2%)


What could be happening is you are using too many game, monitor, and window captures in one scene. Resources are allocated per each screen capture type and take up too much memory to hold their state for encoding.

09:48:25.032: - scene 'TWITCH.TV':
09:48:25.032: - source: 'Przechwytywanie ekranu 2' (monitor_capture)
09:48:25.032: - source: 'Przechwytywanie gry' (game_capture)
09:48:25.032: - source: 'Przechwytywanie okna' (window_capture)
09:48:25.032: - source: 'Ostatnie 5 donate' (browser_source)
09:48:25.032: - source: 'Cel donate' (browser_source)
09:48:25.032: - source: 'Top donate' (browser_source)
09:48:25.032: - source: 'follow etc' (browser_source)
09:48:25.032: - source: 'bits sub' (browser_source)
09:48:25.032: - source: 'donate' (browser_source)
09:48:25.032: - source: 'Przechwytywanie ekranu' (monitor_capture)
09:48:25.032: - source: 'kamerka' (image_source)
09:48:25.032: - source: 'facerig' (game_capture)
09:48:25.032: - filter: 'Kluczowanie koloru (chroma key)' (chroma_key_filter)
09:48:25.032: - source: 'napis' (image_source)
09:48:25.032: - source: 'paski' (image_source)


Instead, try making separate scenes for each screen type and setting things up in a generic manner:

For example:
  1. Intro
  2. Stage - Game Capture
  3. Stage - Window Capture
  4. Stage - Display Capture
  5. Intermission
  6. Outro
I opened OBS by administrator and its better now, but not perfect. The recording is really laggy
 

Attachments

  • 2020-02-28 12-32-52.txt
    13.9 KB · Views: 14

Sukiyucky

Member
You are still setting things up incorrectly.

This scene is using both window capture and a game capture source in one scene:

12:32:54.528: - scene 'TWITCH.TV':
12:32:54.528: - source: 'Przechwytywanie okna' (window_capture) <-----
12:32:54.528: - source: 'Ostatnie 5 donate' (browser_source)
12:32:54.528: - source: 'Cel donate' (browser_source)
12:32:54.528: - source: 'Top donate' (browser_source)
12:32:54.528: - source: 'follow etc' (browser_source)
12:32:54.528: - source: 'bits sub' (browser_source)
12:32:54.528: - source: 'donate' (browser_source)
12:32:54.528: - source: 'kamerka' (image_source)
12:32:54.528: - source: 'napis' (image_source)
12:32:54.528: - source: 'paski' (image_source)
12:32:54.528: - source: 'Przechwytywanie gry' (game_capture) <-----
12:32:54.528: - filter: 'Kluczowanie koloru (chroma key)' (chroma_key_filter)

This scene is using both a monitor capture and window capture source in one scene:

12:10:38.199: - scene 'Nagrywanie':
12:10:38.199: - source: 'ekran1' (monitor_capture) <----
12:10:38.199: - source: 'Przechwytywanie okna 2' (window_capture) <-----


Use only one screen capture type (window, game, or display/monitor) per scene.

Keep your scenes general per screen capture type like I listed above. Call it a Stage.
  1. Stage Display Capture
  2. Stage Window Capture
  3. Stage Game Capture

This avoids creating too many scenes for each game. Its pointless to have 1000 scenes for 1000 games. You choose the game that you want to capture in the screen capture source properties by right clicking on it BEFORE you record or stream. This keeps things very general and flexible to manage.

For:
  1. Game capture: change to either fullscreen or specific window
  2. Window capture: Change Window and Window Match Priority
  3. Display capture: You dont have to do anything it captures the entire full screen of the display
In most of my recordings and streams, I just use display capture.

The advantage is I don't have to screw around with selecting the window, the match conditions and all that other crap. Game capture is not even guaranteed to work because it is based on walking the application and parent window list. If OBS can't match, it will never work. With display capture it is always works and is based on the GetDC(null) of the display. The disadvantage with display capture is there can be a small performance hit and you show windows start bar. But who cares? In most cases, when you play a full screen game, nobody sees the start bar anyway. Keep life simple and just use a display capture everywhere.
 
Last edited:
Top