Question / Help HUGE Stream Delay [CLOSE]

ForbiddenSoul

New Member
I was streaming perfectly contently a few days ago. By the way I just thought I would say I love the new version and glad to see that new software developers actually know something about network coding (which unfortunately I don't).

Today I start to stream, and the online game I am playing beings to increase in latency and lags all over the place. I'm not sure how, but the second I start streaming the video plays fine (in this case twitch), but after about 30-40 minutes of streaming the playback is about 10 minutes behind what I am currently recording.

This makes absolutely no sense to me as the only way this could happen is if it was delayed 10 minutes to start with or is somehow playing back at a slower speed.

Does anyone have any idea what I have done to cause this delay and lag, what causes it, and how to fix it.

Thanks!
 

ForbiddenSoul

New Member
My apologies for the long response time. Here's a log:
20:39:11: OBS 0.10.1 (windows)
20:39:11: CPU Name: Pentium(R) Dual-Core CPU E6500 @ 2.93GHz
20:39:11: CPU Speed: 2926MHz
20:39:11: Physical Cores: 2, Logical Cores: 2
20:39:11: Physical Memory: 4094MB Total, 3004MB Free (NOTE: 4 gigs max is normal for 32bit
programs)
20:39:11: Windows Version: 6.2 Build 9200
20:39:11: audio settings reset:
samples per sec: 44100
speakers: 2
buffering (ms): 1000
20:39:11: ---------------------------------
20:39:11: Initializing D3D11..
20:39:11: Available Video Adapters:
20:39:11: Adapter 0: NVIDIA GeForce GTX 550 Ti
20:39:11: Loading up D3D11 on adapter NVIDIA GeForce GTX 550 Ti (0)
20:39:11: D3D11 loaded sucessfully, feature level used: 45056
20:39:12: video settings reset:
base resolution: 1280x720
output resolution: 1280x720
fps: 15/1
format: NV12
20:39:13: No blackmagic support
20:39:13: Failed to start search for DeckLink devices
20:39:13: output 'simple_stream' (rtmp_output) created
20:39:13: output 'simple_file_output' (flv_output) created
20:39:13: encoder 'simple_h264' (obs_x264) created
20:39:13: encoder 'simple_aac' (ffmpeg_aac) created
20:39:13: service 'default_service' (rtmp_common) created
20:39:13: WASAPI: Device 'Speakers (Turtle Beach PLa Headset)' initialized
20:39:13: source 'Desktop Audio' (wasapi_output_capture) created
20:39:13: WASAPI: Device 'Microphone (Turtle Beach PLa Headset)' initialized
20:39:13: source 'Mic/Aux' (wasapi_input_capture) created
20:39:13: source 'LoL' (scene) created
20:39:13: source 'LoL - Lobby' (game_capture) created
20:39:13: source 'LoL - Game' (game_capture) created
20:39:13: Update check failed: Unable to init SSL Context:
20:39:15: [game-capture: 'LoL - Lobby'] attempting to hook process: LolClient.exe
20:39:15: [game-capture: 'LoL - Lobby'] Hooked to process: LolClient.exe
20:39:15: [game-capture: 'LoL - Lobby'] (half life scientist) everything.. seems to be in
order
20:39:15: [game-capture: 'LoL - Lobby'] Hooked D3D9
20:39:15: [game-capture: 'LoL - Lobby'] d3d9 shared texture capture successful
20:39:19: [game-capture: 'LoL - Lobby'] Hooked DXGI
20:40:58: [x264 encoder: 'simple_h264'] preset: veryfast
20:40:58: [x264 encoder: 'simple_h264'] profile: main
20:40:58: [x264 encoder: 'simple_h264'] settings:
bitrate: 1280
buffer size: 1280
fps_num: 15
fps_den: 1
width: 1280
height: 720
keyint: 30
cbr: on
20:40:58: Using ffmpeg "aac" aac encoder
20:40:58: FFmpeg AAC: bitrate: 96, channels: 2
20:40:58: [rtmp stream: 'simple_stream'] Connecting to RTMP URL rtmp://live-
jfk.twitch.tv/app...
20:40:59: [rtmp stream: 'simple_stream'] Connection to rtmp://live-jfk.twitch.tv/app
successful
20:43:29: WriteN, RTMP send error 10054 (490 bytes)
20:43:29: WriteN, RTMP send error 10054 (79 bytes)
20:43:29: WriteN, RTMP send error 10038 (42 bytes)
20:43:29: [rtmp stream: 'simple_stream'] Disconnected from rtmp://live-jfk.twitch.tv/app
20:43:29: Output 'simple_stream': stopping
20:43:29: Output 'simple_stream': Total frames: 2260
20:43:29: Output 'simple_stream': Number of skipped frames: 45 (1.99115%)
20:43:29: Output 'simple_stream': Number of dropped frames: 423 (18.7168%)
20:44:51: service 'default_service' destroyed
20:44:51: encoder 'simple_h264' destroyed
20:44:51: encoder 'simple_aac' destroyed
20:44:51: 2 frames left in the queue on closing
20:44:51: output 'simple_stream' destroyed
20:44:51: output 'simple_file_output' destroyed
20:44:51: source 'Desktop Audio' destroyed
20:44:51: WASAPI: Device 'Speakers (Turtle Beach PLa Headset)' Terminated
20:44:51: source 'Mic/Aux' destroyed
20:44:51: WASAPI: Device 'Microphone (Turtle Beach PLa Headset)' Terminated
20:44:51: Freeing OBS context data
20:44:51: 3 user source(s) were remaining
20:44:51: source 'LoL' destroyed
20:44:51: source 'LoL - Lobby' destroyed
20:44:51: source 'LoL - Game' destroyed
20:44:51: Number of memory leaks: 0

I have tried removing all OBS files and starting fresh, but that didn't help...

Also if I press the "Stop Streaming" button the program will hang until it catches up to the delay, just depending on how long I have been streaming for, and how large the delay has gotten. Once it stops I loose internet connectivity until I restart my PC.
Someone else posted the same issue about the loss of connection and they were instructed to update their Broadcom network drivers, and apparently it fixed it, but mine are already up to date.
I'm going to try my wireless adapter and see if I have the same issue.
I'm sure I'm not helping development by not using the most up to date source code in the repositories. Once I get that large chain of prerequisites of prerequisites downloaded I'll attempt to build it and maybe be helpful.

Thanks!
 
Your bitrate/buffer size is pretty low for streaming in 720p...(what is your upload speed anyway ?)
I also see ~19% of your frames are dropped...I think your CPU & GPU are too weak to stream in 720p.
Try to stream in 480p:
  • Bitrate & buffer size: 1000
  • Output resolution: 854x480
  • FPS: 30
 

ForbiddenSoul

New Member
Yeah I lowered the bitrate and frame rate because the lag and delay had started. I was originally streaming at 1280x720 2500kbps video 128kbps audio 29.97FPS (NTSC). Those were the default settings, except I think I changed fps from 30 to 29.97. In-Game frame rate was 25-45 fps while streaming, once I lowered the settings I started getting 60 fps in-game.

I was successfully streaming with a 20-30 second delay with those settings for about a week, before dropped frames and the stream delay started happening.

To be honest I think I just did something on my end that had absolutely nothing to do with the OBS software. (now that I think about it I changed video drivers, I'm going to go change back as we speak.)


*EDIT*
Also changing the network adapters didn't help OBS still breaks the internet connection if let shutdown "properly"

I Just change back to NVidia CUDA drivers, rather than their generic ones. Got a nice performance increase, but the stream delay still exists with a ton of buffering during playback...
 
Last edited:

ForbiddenSoul

New Member
Thanks for the help, but you guys both missed the part where I stated I was streaming fine for 7 days straight, then all of a sudden I get a stream delay.
Settings and hardware were not an issue for the first week, then this problem started happening.
I think the issue is that some of my routes have changed, and my upload bandwidth to twitch.tv is just not high enough. Rather than make a chunky video, the real time playback buffers, and the delay is created.
So seems like it is a connection issue and not the fault of OBS (I never thought it was OBS).
I'm going to close this post because no one on here ever takes the time to read what peoples problems actually are just give generic robotic answers of:
Lower your settings
Upgrade your hardware
Which in this case have nothing to do with anything, other than lowering the bitrate will match my new shitter upload speed.
 
Last edited:
Well, theoretically, if you lower your bitrate to prevent dropping frames due to upload speed you could increase the processing effort so you'll get a slightly better picture. Problem is then that your hardware can't handle that (neither do the hardware encoders).

So shitty connection + shitty hardware = problems

When your connection was going good you were able to lower your cpu usage by upping your bitrate. Essentially solving your hardware problem by throwing bitrate at it.
 
Top