jazzathepro
New Member
I also just checked, Streaming at 2000 bitrate causes the green box to like flash yellow suddenly for a millisecond the goes back to green and the bitrate is fluctuating by atleast 800
Question / Help Pixelated Stream and Bit Rate Question.
- Thread starter jazzathepro
- Start date
jazzathepro
New Member
I think I solved the problem, Like I stated before I said I received a 5mbps(megaBITS) upload speed. The bitrate in obs is measured in KB/s and 5mbps is only 700KB/s!! I have been trying to stream at 2000 causing it to go lower than its CBR which causes the pixelation. I made sure that I clearly stated mbps earlier in my post and apparently it wasn't a problem. Could someone please shine some light on this and help me out?
jazzathepro
New Member
I just read this post https://obsproject.com/forum/threads/can-someone-explain-this-to-me.24328/#post-121944
Now im extremely confused. WHY IS MY GREEN BOX CHANGING COLOURS >_<
Now im extremely confused. WHY IS MY GREEN BOX CHANGING COLOURS >_<
FerretBomb
Active Member
OBS measures in kilobits per second (kbps) not kilobytes per second (KB/s, kBps, caps matter).
The box is your buffer indicator. It can go all the way to RED and be fine, so long as you aren't dropping frames; it just means that you have an inconsistent/flaky connection, or that the connection has to wait to send, and as a result your buffer is getting full (also, do not increase the size of your buffer, this is again AOK so long as you don't drop frames). You also will indeed have bitrate fluctuation. Normally it's minor, but on a poor connection to the server it can need to 'catch up' and will go higher temporarily to clear out more of the buffer.
Be aware that speedtest sites are generally-speaking useless for livestreamers; they normally test a different type of connection than livestreaming uses (overall file transfer speed, instead of baseline minimum throughput). They also don't test the connection to the Twitch ingest servers, just to a server (hopefully) in that general region (many will pick a server closest to you to check your last-mile connection, making them doubly worthless as you care about a connection to a specific location, and this does not take your routing path into account). Also, speedtest.net is especially livestreamer-useless as they discard the slowest 1/3 of your traffic.
Went and watched your video clip, and it looks fine given the resolution, framerate and bitrate at which you are streaming. You will never get perfect 1:1 video; compression is a necessity, and real-time video encoding is an extremely computationally-heavy task. Especially when playing a high-motion game (which is to say ANY third-person game, be it DayZ, almost any MMO in existence, H1Z1, etc).
About the only way to improve it is to use more/better compression (and thereby more CPU, by using a slower compression preset) or more bitrate (and risk having viewers buffer like crazy).
Stay away from NVENC and/or QSV. This is the opposite of what you want. They sacrifice quality to reduce CPU usage, and look terrible at the same bitrate as compared to x264. Good for local recordings if you plan to keep a higher-res copy and want to minimize CPU impact for that second encoding, and can afford to drop a few MB/s (not mbps) in disk space to make it happen.
The box is your buffer indicator. It can go all the way to RED and be fine, so long as you aren't dropping frames; it just means that you have an inconsistent/flaky connection, or that the connection has to wait to send, and as a result your buffer is getting full (also, do not increase the size of your buffer, this is again AOK so long as you don't drop frames). You also will indeed have bitrate fluctuation. Normally it's minor, but on a poor connection to the server it can need to 'catch up' and will go higher temporarily to clear out more of the buffer.
Be aware that speedtest sites are generally-speaking useless for livestreamers; they normally test a different type of connection than livestreaming uses (overall file transfer speed, instead of baseline minimum throughput). They also don't test the connection to the Twitch ingest servers, just to a server (hopefully) in that general region (many will pick a server closest to you to check your last-mile connection, making them doubly worthless as you care about a connection to a specific location, and this does not take your routing path into account). Also, speedtest.net is especially livestreamer-useless as they discard the slowest 1/3 of your traffic.
Went and watched your video clip, and it looks fine given the resolution, framerate and bitrate at which you are streaming. You will never get perfect 1:1 video; compression is a necessity, and real-time video encoding is an extremely computationally-heavy task. Especially when playing a high-motion game (which is to say ANY third-person game, be it DayZ, almost any MMO in existence, H1Z1, etc).
About the only way to improve it is to use more/better compression (and thereby more CPU, by using a slower compression preset) or more bitrate (and risk having viewers buffer like crazy).
Stay away from NVENC and/or QSV. This is the opposite of what you want. They sacrifice quality to reduce CPU usage, and look terrible at the same bitrate as compared to x264. Good for local recordings if you plan to keep a higher-res copy and want to minimize CPU impact for that second encoding, and can afford to drop a few MB/s (not mbps) in disk space to make it happen.
Last edited: