A lot of people are leaving my stream because the lag is unbearable at the highest quality. I understand that you have to be partnered with Twitch to have the ability to change qualities on the Twitch player, but is there way I can change the default quality to a lower one, mine is set at 900p atm.
Question / Help People are complaining that quality is too high on Twitch?
- Thread starter Deflect
- Start date
itsRyansKi
New Member
Re: People are complaining that quality is too high on Twitc
It can be because of two (three) reasons.
- You have the Bitrate too high, the Bitrate is the amount of data you send to your stream per second. If you set the bitrate to 3000 the viewer will need a 3Mbps connection to view your stream when all the bits are being used.
- You're dropping packets to the Twitch server, this is when you are sending data to the server but the data is lost on the route. This could be due to several things such as line fault, streaming wirelessly or due to a bad segment along the route.
- It's not uncommon for Twitch nodes to be overloaded along some segments, though this seems to be fixed for me recently. When a node is overloaded it will drop packets because it doesn't have bandwidth available or power to process of all the data trying to go through so it is dropping packets. This leading to your viewer losing packets because of the node causing the stream to lag.
- If your PC isn't good enough you could see your PC bottleneck. Bottlecking is when a part(s) in your computer has too many requests and doesn't have enough power to process the data and loses/drops the data or processes it too late.
It can be because of two (three) reasons.
- You have the Bitrate too high, the Bitrate is the amount of data you send to your stream per second. If you set the bitrate to 3000 the viewer will need a 3Mbps connection to view your stream when all the bits are being used.
- You're dropping packets to the Twitch server, this is when you are sending data to the server but the data is lost on the route. This could be due to several things such as line fault, streaming wirelessly or due to a bad segment along the route.
- It's not uncommon for Twitch nodes to be overloaded along some segments, though this seems to be fixed for me recently. When a node is overloaded it will drop packets because it doesn't have bandwidth available or power to process of all the data trying to go through so it is dropping packets. This leading to your viewer losing packets because of the node causing the stream to lag.
- If your PC isn't good enough you could see your PC bottleneck. Bottlecking is when a part(s) in your computer has too many requests and doesn't have enough power to process the data and loses/drops the data or processes it too late.
Re: People are complaining that quality is too high on Twitc
Alrighty then.
Alrighty then.
Code:
15:13:16: Open Broadcaster Software v0.522b - 32bit (´・ω・｀)
15:13:16: -------------------------------
15:13:16: CPU Name: AMD Phenom(tm) II X6 1090T Processor
15:13:16: CPU Speed: 3200MHz
15:13:16: Physical Memory: 4095MB Total, 4059MB Free
15:13:16: stepping id: 0, model 10, family 15, type 0, extmodel 8, extfamily 0, HTT 1, logical cores 6, total cores 6
15:13:16: monitor 1: pos={0, 0}, size={1440, 900}
15:13:16: Windows Version: 6.1 Build 7601 S
15:13:16: Aero is Enabled
15:13:16: -------------------------------
15:13:16: OBS Modules:
15:13:16: Base Address Module
15:13:16: 01140000 OBS.exe
15:13:16: 69050000 OBSApi.dll
15:13:16: 6D0F0000 DShowPlugin.dll
15:13:16: 738B0000 GraphicsCapture.dll
15:13:16: 715B0000 NoiseGate.dll
15:13:16: ------------------------------------------
15:13:16: Adapter 1
15:13:16: Video Adapter: NVIDIA GeForce GTX 470
15:13:16: Video Adapter Dedicated Video Memory: 1293352960
15:13:16: Video Adapter Shared System Memory: 2952343552
15:13:16: =====Stream Start: 2013-06-04, 15:13:16===============================================
15:13:16: Multithreaded optimizations: On
15:13:16: Base resolution: 1440x900
15:13:16: Output resolution: 1440x900
15:13:16: ------------------------------------------
15:13:16: Loading up D3D10...
15:13:16: Playback device {0.0.0.00000000}.{aea23a3b-544e-4b79-95f1-081924a98f0c}
15:13:16: ------------------------------------------
15:13:16: Using desktop audio input: Speakers (Logitech USB Headset H540)
15:13:16: ------------------------------------------
15:13:16: Using auxilary audio input: Microphone (Logitech USB Headset H540)
15:13:16: ------------------------------------------
15:13:16: Audio Encoding: MP3
15:13:16: bitrate: 128
15:13:16: ------------------------------------------
15:13:16: device: Logitech QuickCam S5500,
15:13:16: device id \\?\usb#vid_046d&pid_09a1&mi_00#6&331e3e26&0&0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{bbefb6c7-2fc4-4139-bb8b-a58bba724083},
15:13:16: chosen type: I420, usingFourCC: false, res: 320x240 - 320x240, frameIntervals: 333333-2000000, fourCC: 'I420'
15:13:16: audio device: Disable,
15:13:16: audio device id Disabled,
15:13:16:
15:13:16: Using directshow input
15:13:16: Using graphics capture
15:13:16: Using Window Capture
15:13:16: Using bitmap image
15:13:16: ------------------------------------------
15:13:16: Video Encoding: x264
15:13:16: fps: 60
15:13:16: width: 1440, height: 900
15:13:16: preset: veryfast
15:13:16: CBR: yes
15:13:16: CFR: no
15:13:16: max bitrate: 2000
15:13:16: ------------------------------------------
15:13:16: SharedTexCapture hooked
15:13:17: Using RTMP service: Twitch / Justin.tv
15:13:17: Server selection: rtmp://live-mia.justin.tv/app
15:13:18: SO_SNDBUF was at 8192
15:13:18: SO_SNDBUF is now 65536
15:13:47: Exit signal received, terminating capture
15:14:07: ------------------------------------------
15:14:07: device: Logitech QuickCam S5500,
15:14:07: device id \\?\usb#vid_046d&pid_09a1&mi_00#6&331e3e26&0&0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{bbefb6c7-2fc4-4139-bb8b-a58bba724083},
15:14:07: chosen type: I420, usingFourCC: false, res: 320x240 - 320x240, frameIntervals: 333333-2000000, fourCC: 'I420'
15:14:07: audio device: Disable,
15:14:07: audio device id Disabled,
15:14:07:
15:14:21: ------------------------------------------
15:14:21: device: Logitech QuickCam S5500,
15:14:21: device id \\?\usb#vid_046d&pid_09a1&mi_00#6&331e3e26&0&0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{bbefb6c7-2fc4-4139-bb8b-a58bba724083},
15:14:21: chosen type: I420, usingFourCC: false, res: 320x240 - 320x240, frameIntervals: 333333-2000000, fourCC: 'I420'
15:14:21: audio device: Disable,
15:14:21: audio device id Disabled,
15:14:21:
15:20:17: SharedTexCapture hooked
16:02:13: Exit signal received, terminating capture
16:03:40: Total frames rendered: 181358, number of frames that lagged: 68 (0.04%) (it's okay for some frames to lag)
16:03:41: RTMPPublisher::SocketLoop: Aborting due to bStopping
16:03:41: Number of times waited to send: 0, Waited for a total of 0 bytes
16:03:41: Number of b-frames dropped: 0 (0%), Number of p-frames dropped: 0 (0%), Total 0 (0%)
16:03:41: =====Stream End: 2013-06-04, 16:03:41=================================================
16:03:41:
16:03:41: Profiler results:
16:03:41:
16:03:41: ==============================================================
16:03:41: frame - [100%] [avg time: 3.944 ms] [avg calls per frame: 1] [children: 86%] [unaccounted: 14%]
16:03:41: | scene->Preprocess - [7.66%] [avg time: 0.302 ms] [avg calls per frame: 1]
16:03:41: | video encoding and uploading - [78.4%] [avg time: 3.091 ms] [avg calls per frame: 1] [children: 76.8%] [unaccounted: 1.55%]
16:03:41: | | CopyResource - [0.71%] [avg time: 0.028 ms] [avg calls per frame: 0]
16:03:41: | | conversion to 4:2:0 - [0.279%] [avg time: 0.011 ms] [avg calls per frame: 0]
16:03:41: | | call to encoder - [74.4%] [avg time: 2.933 ms] [avg calls per frame: 0]
16:03:41: | | sending stuff out - [1.47%] [avg time: 0.058 ms] [avg calls per frame: 0]
16:03:41: ==============================================================
16:03:41:
Re: People are complaining that quality is too high on Twitc
It might be the 60fps. I know plenty of computers have trouble with 1080p60...in general, high resolution + high frame rate seems to not work well with Flash. 720p is the highest resolution I recommend using with 60fps. Can you try downscaling a bit to see if that helps people?
It might be the 60fps. I know plenty of computers have trouble with 1080p60...in general, high resolution + high frame rate seems to not work well with Flash. 720p is the highest resolution I recommend using with 60fps. Can you try downscaling a bit to see if that helps people?