Bug Report Ping spiking issues

C

Carnavas

New Member
So I've got roughly 2/mb upload speed. My stream quality is absolutely fine, but I've noticed in the corner the little meter that shows kb/s sits at a normal level then every now and again it randomly jumps up by about 1000. The stream stays fine but my in game ping jumps up by quite a lot when this is happening. Any ideas what could be causing it to spike like that?

It happens with Xsplit too so it's not OBS it's obviously an internet problem but how can I find out what the problem is?
 
L

Lain

Forum Admin
Lain
Forum Moderator
Developer
It's x264, you may want to try turning down the quality balance, and maybe turn down your video encoding buffer size, and see if that changes anything. Your game has to share the bandwidth with the app, so you might get spikes on occasion. Could also try CBR as a last resort if nothing else works, I have heard that it can be less spiky with that.
 
H

hilalpro

Member
prioritize the port of the game in your router if you''re using a connection that supports qos or use a program called cfosspeed and prioritize your game.
 
C

Carnavas

New Member
Thanks for the replies.

I've tried fiddling with those things before I'm still seeing these spikes in the kb/s - but it hasn't always been this way. What's CBR?

Virgin Media superhub doesn't support qos, and I'm not sure where to get cfosspeed. Is it free?

How is it that this affects my in game ping but the stream quality is perfectly smooth?
 
H

hilalpro

Member
Carnavas said:
Thanks for the replies.

I've tried fiddling with those things before I'm still seeing these spikes in the kb/s - but it hasn't always been this way. What's CBR?

Virgin Media superhub doesn't support qos, and I'm not sure where to get cfosspeed. Is it free?

How is it that this affects my in game ping but the stream quality is perfectly smooth?
Click to expand...

no problem mate.

cbr is constant bitrate.. the bitrate could be less bursty using this mode.

cfosspeed gives you 30 days free test with full features available. a great alternative is NetBalancer the free edition allows you to control 3 process's/connections simultaneously.. you only need to put the game exe file on a higher priority. just google "NetBalancer"
 
C

Carnavas

New Member
The problem with CBR was it was just bringing the kb/s up to a higher level consistently but it was still spiking. I tried NetBalancer but I didn't really notice a difference. I just don't feel like my in game ping should be affected at all when I have 1000 bitrate on a 2/mb upload. I would have thought that setting a maxium bitrate of 1000 would mean that the kb/s couldn't go over 1000 but that doesn't seem to be the case...

It's just irritating not having a stable ping when streaming. Is this a normal thing? It's somewhat worse for me because my ping on the NA servers for LoL is already 170~ without streaming.
 
H

hilalpro

Member
Carnavas said:
The problem with CBR was it was just bringing the kb/s up to a higher level consistently but it was still spiking. I tried NetBalancer but I didn't really notice a difference. I just don't feel like my in game ping should be affected at all when I have 1000 bitrate on a 2/mb upload. I would have thought that setting a maxium bitrate of 1000 would mean that the kb/s couldn't go over 1000 but that doesn't seem to be the case...

It's just irritating not having a stable ping when streaming. Is this a normal thing? It's somewhat worse for me because my ping on the NA servers for LoL is already 170~ without streaming.
Click to expand...
i have a slightly over 1mbps up line and for experimenting purposes i'm using a high resolution looping gif with around 600 frames (0.01 delay period between frames) each frame being totally different

bitrate 900 and the buffer is 2356

here's some data during a usual congestion hour

obs to a lower priority with cfos traffic shaping - stream on

Pinging [68.67.73.20] with 1492 bytes ->bytes=1492 time=210ms TTL=44
Pinging [68.67.73.20] with 1492 bytes ->bytes=1492 time=202ms TTL=44
Pinging [68.67.73.20] with 1492 bytes ->bytes=1492 time=241ms TTL=44
Pinging [193.10.252.19] with 1492 bytes ->bytes=1492 time=138ms TTL=237
Pinging [193.10.252.19] with 1492 bytes ->bytes=1492 time=127ms TTL=237
Pinging [193.10.252.19] with 1492 bytes ->bytes=1492 time=158ms TTL=237
Pinging [169.232.33.241] with 1492 bytes ->bytes=1492 time=281ms TTL=41
Pinging [169.232.33.241] with 1492 bytes ->bytes=1492 time=272ms TTL=40
Pinging [169.232.33.241] with 1492 bytes ->bytes=1492 time=250ms TTL=41
Pinging [173.194.78.103] with 1492 bytes ->Request Timed Out
Pinging [173.194.78.103] with 1492 bytes ->Request Timed Out
Pinging [173.194.78.103] with 1492 bytes ->Request Timed Out
Pinging [67.212.154.222] with 1492 bytes ->bytes=1492 time=241ms TTL=108
Pinging [67.212.154.222] with 1492 bytes ->bytes=1492 time=292ms TTL=108
Pinging [67.212.154.222] with 1492 bytes ->bytes=1492 time=231ms TTL=108
Ping statistics for above hosts:
Packets: Sent = 15, Received = 12, Lost = 3 (20% loss)
Approximate round trip times (RTT) in milli-seconds:
Minimum = 127ms, Maximum = 292ms, Average = 176ms

traffic shaping turned off - stream on

Pinging [68.67.73.20] with 1492 bytes ->bytes=1492 time=247ms TTL=44
Pinging [68.67.73.20] with 1492 bytes ->bytes=1492 time=185ms TTL=44
Pinging [68.67.73.20] with 1492 bytes ->bytes=1492 time=314ms TTL=44
Pinging [193.10.252.19] with 1492 bytes ->bytes=1492 time=174ms TTL=237
Pinging [193.10.252.19] with 1492 bytes ->bytes=1492 time=200ms TTL=237
Pinging [193.10.252.19] with 1492 bytes ->bytes=1492 time=170ms TTL=237
Pinging [169.232.33.241] with 1492 bytes ->bytes=1492 time=353ms TTL=41
Pinging [169.232.33.241] with 1492 bytes ->bytes=1492 time=429ms TTL=41
Pinging [169.232.33.241] with 1492 bytes ->bytes=1492 time=256ms TTL=41
Pinging [173.194.78.103] with 1492 bytes ->Request Timed Out
Pinging [173.194.78.103] with 1492 bytes ->Request Timed Out
Pinging [173.194.78.103] with 1492 bytes ->Request Timed Out
Pinging [67.212.154.222] with 1492 bytes ->bytes=1492 time=385ms TTL=108
Pinging [67.212.154.222] with 1492 bytes ->Request Timed Out
Pinging [67.212.154.222] with 1492 bytes ->bytes=1492 time=270ms TTL=108
Ping statistics for above hosts:
Packets: Sent = 15, Received = 11, Lost = 4 (27% loss)
Approximate round trip times (RTT) in milli-seconds:
Minimum = 170ms, Maximum = 429ms, Average = 198ms

i can imagine the numbers get closer by simply lowering the bitrate but those are just some numbers for you and its not a 1 run test. traffic shaping is proven to be good when it comes to streaming while playing online games

no shaping - stream off

Pinging [68.67.73.20] with 1492 bytes ->bytes=1492 time=192ms TTL=43
Pinging [68.67.73.20] with 1492 bytes ->bytes=1492 time=207ms TTL=43
Pinging [68.67.73.20] with 1492 bytes ->bytes=1492 time=190ms TTL=43
Pinging [193.10.252.19] with 1492 bytes ->bytes=1492 time=128ms TTL=236
Pinging [193.10.252.19] with 1492 bytes ->bytes=1492 time=129ms TTL=236
Pinging [193.10.252.19] with 1492 bytes ->bytes=1492 time=129ms TTL=236
Pinging [169.232.33.241] with 1492 bytes ->bytes=1492 time=237ms TTL=39
Pinging [169.232.33.241] with 1492 bytes ->bytes=1492 time=237ms TTL=39
Pinging [169.232.33.241] with 1492 bytes ->bytes=1492 time=237ms TTL=39
Pinging [173.194.47.82] with 1492 bytes ->bytes=1492 time=107ms TTL=46
Pinging [173.194.47.82] with 1492 bytes ->bytes=1492 time=108ms TTL=46
Pinging [173.194.47.82] with 1492 bytes ->bytes=1492 time=107ms TTL=46
Pinging [67.212.154.222] with 1492 bytes ->bytes=1492 time=219ms TTL=106
Pinging [67.212.154.222] with 1492 bytes ->bytes=1492 time=218ms TTL=106
Pinging [67.212.154.222] with 1492 bytes ->bytes=1492 time=219ms TTL=106
Ping statistics for above hosts:
Packets: Sent = 15, Received = 15, Lost = 0 (0% loss)
Approximate round trip times (RTT) in milli-seconds:
Minimum = 107ms, Maximum = 237ms, Average = 177ms
 
C

Carnavas

New Member
Maybe I'll have to try cfosspeed instead then to see if I notice any different. Do you set the game to a high priority and obs to a low priority or is it one or the other?
 
R

R1CH

Forum Admin
Developer
Yes that's normal. In low / no motion scenes, your B/P frames will be tiny since there is very little difference, but the I-frames (keyframes) still need to be full size. An I-frame is sent every 4 seconds.
 
C

Carnavas

New Member
R1CH said:
Yes that's normal. In low / no motion scenes, your B/P frames will be tiny since there is very little difference, but the I-frames (keyframes) still need to be full size. An I-frame is sent every 4 seconds.
Click to expand...

Ah thanks. I'm not sure why my ping is being affected when my bitrate is a lot lower than my upload then. :(
 
C

Carnavas

New Member
Okay so I made two videos. One with 1500 bitrate, and one with 800 bitrate.

This is on the NA server for League:
800 - http://www.twitch.tv/carnavas/b/353204912#
1500 - http://www.twitch.tv/carnavas/b/353204678


I also did it on the EU server:
800 - http://www.twitch.tv/carnavas/b/353207235
1500 - http://www.twitch.tv/carnavas/b/353207757#

In every case you can see my ping jumps around while streaming. This isn't normal is it? I know for a fact at my old address any ping issues I had would only be apparent if my bitrate was too close to or above my upload speed, and even then it was consistent (it would stay high not jump up and down).
 
V

Voxletum

Member
Are you using lolrecorder/lolreplay? They download a file every 30 seconds when spectating your own game, it nearly doubles the bandwidth that LoL will use over the course of a game but it happens in spikes about every 30 seconds.
 
You must log in or register to reply here.
Top