Question / Help Average frame rendering time

W

WWWKENNYSEQCOM

Member
Picture of my problem


Hi ... I'm facing a problem that is "average frame rendering time"

Is it possible that when running OBS Studio / Streamlabs OBS without recording or streaming, my average frame rendering time is 0.8-1.0 ms? When I have a single scene in which there is only one source?

My streaming PC:

  • MB: ASRock B450M PRO4
  • WIN: Windows 10 Pro 64 bit
  • CPU: Amd Ryzen 7 2700X
  • GPU: Msi Geforce 1070 Gaming X 8G 8Gb
  • RAM: Corsair Vengeance Black 16Gb DDR4 3000Mhz
  • PSU: Seasonic Focus Plus Gold - 850W
  • SSD: Samsung SSD 960 EVO (M.2) - 250GB
  • HDD: Seagate BarraCuda - 2TB
  • CASE: Be quiet! Silent Base 801
  • MONITOR1: Acer Nitro VG270bmiix - LED monitor 27"(1920x1080 60Hz)
  • MONITOR2: Acer Nitro VG270bmiix - LED monitor 27"(1920x1080 60Hz)
  • CPU COLER: Be quiet! Dark Rock PRO 4
  • SOUND CARD: Creative Sound Blaster ZX
  • EDITINGCARD: Elgato Game Capture 4K60 Pro
  • WEBCAM1: Logitech Webcam C922 Pro Stream
  • WEBCAM2: Logitech Webcam C922 Pro Stream
  • WEBCAM3: Creative Live! Cam Sync HD
  • MICROPHONE1: Behringer C-1U
  • MICROPHONE2: Behringer C-1U
  • HEADPHONES1: Logitech G231 Prodigy
  • HEADPHONES2: Logitech G231 Prodigy
  • GREENSCREEN: Elgato Green Screen

    My gaming pc:
  • MB: Msi mag Z390 Tomahawk
  • WIN: Windows 10 Pro 64 bit
  • CPU: Intel Core i9 9900k
  • GPU: Msi Geforce 2070 Gaming Z 8G 8Gb GDDR6
  • RAM: Corsair Vengeance Black 16Gb DDR4 3000Mhz
  • PSU: Seasonic Focus Plus Gold - 850W
  • SSD1: Samsung SSD 960 EVO (M.2) - 250GB
  • SSD2: Samsung SSD 970 EVO PLUS (M.2) - 500GB
  • HDD1: Seagate BarraCuda - 2TB
  • HDD2: Seagate BarraCuda - 2TB
  • CASE: Be quiet! Silent Base 801
  • MONITOR: LG 34UC89G-B - LED monitor 34"(2560x1080 144Hz)
  • CPU COLER: NZXT Kraken X72
  • SOUND CARD: Creative Sound Blaster ZX
  • HEADPHONES: Logitech G231 Prodigy
 
D

Deleted member 121471

It's only a problem if you're a minecraft player that streams or records at >1000-1250 FPS.
 
W

WWWKENNYSEQCOM

Member
If you understand me that I have these values while running OBS without streaming or recording so thank you and I take this topic for done :) And I would like to refer to one more thing that I fight and for God I can not figure out what the problem is like this is really a problem and not just small. At first I thought that this topic could concern but according to you probably not and I believe you.

Link here:
https://obsproject.com/forum/thread...6UWzeFATbUxhIBbYiQxTolUlPb7R36zMRzELCvJv_3kIA

https://obsproject.com/forum/threads/crash-obs-dual-streaming-setup.110927/
 
Last edited:
Narcogen

Narcogen

Active Member
Yes, that is what I mean. That number will not drop to zero while OBS is running, even if you have no sources.

That number is for rendering frames. OBS renders frames at all times while running-- even if you are not streaming or recording, and even if the preview window is off.

The number may be lower or higher, but again, it's not really a problem until it approaches 16, and it will never, ever be zero.
 
D

Deleted member 121471

There would be a problem if that number was 0, every frame needs time to composite and render.

Divide 1000 by the FPS you're encoding at to know which value the "average time to render frame" needs to be lower than, in miliseconds.
 
W

WWWKENNYSEQCOM

Member
Narcogen said:
Yes, that is what I mean. That number will not drop to zero while OBS is running, even if you have no sources.

That number is for rendering frames. OBS renders frames at all times while running-- even if you are not streaming or recording, and even if the preview window is off.

The number may be lower or higher, but again, it's not really a problem until it approaches 16, and it will never, ever be zero.
Click to expand...
Thank you, thank you, it cleaned me up
 
Narcogen

Narcogen

Active Member
It will vary wildly from computer to computer, from scene collection to scene collection, from scene to scene, and also depend on what is going on in each individual frame.

Again, you do not need to worry about this until that number starts approaching 16ms-- because that is when you will have difficulty keeping a smooth framerate because of dropped frames.

If your logs don't show rendering or encoding lag, if your average time to render is not approaching 16, spend your time improving your streams in other ways-- these things are not a problem.

If you are seeing smoothness issues in your videos but aren't seeing rendering or encoding lag, and the average time to render is well below 16ms, then the issues are coming from something else and you should not be spending time on trying to optimize this number.
 
You must log in or register to reply here.
Top