Question / Help Massive FPS Drops while streaming

T

Tayrint

New Member
Hello guys,
fist : sorry for my english^^ its probaly not the best =)


I use
OBS Studio 18.0.1 & FTL 0.9.4

and I stream on beam.pro

My problem is that that I can not stream without framedrops by 30 fps or more.
few days ago I could stream with 720p at 60 fps and 5k Bitrate.
Thats a dream now and I dont know why.

Today I tested it again with the game "paragon" and bam maybe only 10 - 25 fps.
CPU usage not above 20%

Ingame its all fine but not on OBS and Stream

stream and capture both this problem -.-


https://gist.github.com/anonymous/53971f81cfefa724920bb65b4275a411
 
Boildown

Boildown

Active Member
Windows Version: 10.0 Build 15063 (revision: 138; 64-bit)
Click to expand...
Log says Windows 10.

17:55:51.734: [x264 encoder: 'streaming_h264'] preset: faster
17:55:51.734: [x264 encoder: 'streaming_h264'] profile: baseline
17:55:5.734: [x264 encoder: 'streaming_h264'] tune: zerolatency
Click to expand...

Use Very Fast preset.
Main or High profile (main if your viewers use old mobile devices, High if they mainly watch on PCs or newer mobile devices).
Get rid of the zerolatency tune. Don't use any tune at all.

18:07:50.800: Output 'adv_stream': Number of skipped frames due to encoding lag: 179 (0.4%) 18:07:50.800: Output 'adv_stream': Number of lagged frames due to rendering lag/stalls: 13264 (30.7%)
Click to expand...

30% lagged frames is bad, I think that's due to your preset, it would be resolved by switching it to Very Fast.

As an additional test, see if it performs better without the webcam.
 
NicOnAcid

NicOnAcid

Member
ah thx broildown. didn notice this part in the logs.

i dont know exactly. what i know is, that me and other has this problem since they all got this update. no problems before this update.
 
T

Tayrint

New Member
Oh i think it was the false log file.
I use very fast and high profile.

Beam.pro recommend to use zerolatency tune.
I tested so much settings today.
Without cam it is not better.
 
R

RytoEX

Forum Admin
Forum Moderator
Developer
Boildown said:
Oh jeez, you're thinking its like the Anniversary Update all over again?
Click to expand...
plsnokthx
No seriously, I hope not. I don't want to relive this nightmare.

Boildown said:
Use Very Fast preset.
Main or High profile (main if your viewers use old mobile devices, High if they mainly watch on PCs or newer mobile devices).
Get rid of the zerolatency tune. Don't use any tune at all.
Click to expand...
Incidentally, it looks like the FTL folks recommend those settings for streaming to Beam, except that they do recommend the high profile rather than baseline.
  • CPU Usage: this is more related to how hard the encoder tries to do a good job; faster values typically means the encoder spends less time resulting in lower quality for the same bitrate. if you have a very good CPU you can pick a slower settings but pay attention to how much CPU OBS is consuming. Some of the very slow settings will introduce more delay to improve the encoding quality (recommended setting: faster)
  • profile: high
  • tune: zero latency

Also incidentally, the Windows 10 Creator Update introduced some new features regarding Game Mode, the Game Bar, streaming, and Beam. Hopefully that's just coincidental and not causing the issues here.

A cursory look at the log's profiler results seems to indicate that the graphics card is getting overloaded. If it worked fine before, I recommend checking these things:
  • if your graphics card driver was updated recently
  • if your OS was updated recently
  • if your streaming software was updated recently
  • if your computer temperatures are higher than normal
  • if you installed new software recently
 
R

RytoEX

Forum Admin
Forum Moderator
Developer
Tayrint said:
Updated win10
Updated grafic driver
Click to expand...
If it worked fine before you did these things, and if you haven't changed any of your OBS settings, then I'd say that one of these things is causing your problems.

If you feel comfortable, you can try rolling back those updates. Please understand that there may be downsides to rolling back those updates.
 
O

Osiris

Active Member
I've heard some ppl talking about Disabling fullscreen optimizations in the compatibility tab of the executable's properties. Try that for both the OBS executables and the game's
 
T

Tayrint

New Member
ok, i done Disabling fullscreen optimizations.
and disabled game mode of win10

It helps a bit and I set the FPS from 60 to 48 FPS

I done a campture and a stream.
But I dont understand die Logs, so here are the Logs of today -.-

Profile was NOT Ultrafast like the logs says...Profile is very fast.

https://gist.github.com/anonymous/ab39f0a63befa9dbf8909c6679885715
https://gist.github.com/anonymous/88b393d9887390345187ee80918b918d
https://gist.github.com/anonymous/484efcdf14cba4dd5376976cdd1bf2b6
https://gist.github.com/anonymous/1bf6e985bab6a45d57a50f104fbe3919
https://gist.github.com/anonymous/2d1386a336ea4fbbc3cc88407760579c
 
Boildown

Boildown

Active Member
I'm still concerned about zerolatency tune. From this: https://superuser.com/questions/564402/explanation-of-x264-tune

What it does is:
- zerolatency:
--bframes 0 --force-cfr --no-mbtree
--sync-lookahead 0 --sliced-threads
--rc-lookahead 0
Click to expand...

Most of those are things that are undesirable. I'd ignore their zerolatency requirement, as a test, and see if things improve. The latency savings are pretty negligible on the zerolatency tune anyways, but its really costly in performance.

Some of your logs look fine and others have a large amount of dropped frames (encoder lag). It would be best if you can come up with the one setting that has been working best for you and then we just iterate on that, instead of posting logs with settings seemingly randomly assigned all over the place.
 
T

Tayrint

New Member
zerolatency is for the FTL Beam.pro Stream for a delay about 200ms.

before something broken or what ever happens
were my settings

profile : very fast
bitrate : 5k
tune: zerol.
keyframe: 3
CBR
720p Downscale
Bilinear filter
48fps
process priority : higher as normal.

and Auto Server ingest.

I didnt change this settings and then happens the sh't
 
Boildown

Boildown

Active Member
Finally googled it and now I see what you're talking about, but I have new questions....

Are you using the FTL fork of OBS as described here: https://watchbeam.zendesk.com/hc/en-us/articles/209659623-FTL-Faster-Than-Light-streaming-protocol- ?

Because if not, maybe you should. And if you are, maybe they have better advice for you than we can give, since we don't know what they changed in their customized version of OBS?

Edit:
15:34:41.174: OBS 18.0.1-ftl.0.9.4 (64bit, windows)
Click to expand...
Looks like you are.
 
Last edited:
You must log in or register to reply here.
Top