Question / Help Can't stream whatsoever, very suddenly.

twitchtvm_tt

twitchtvm_tt

New Member
On the 22nd, I was able to stream fine. Here is my OBS log of the 22nd: https://gist.github.com/80a7f1a8ac41f612e159

However, on the 23rd, something suddenly changed. Here is that log: https://gist.github.com/c4701114922a0e0e8c86

As you can see from the logs, my internet constantly dropped out, after changing absolutely nothing about my setup. I have Comcast and they have sworn up and down that they aren't throttling me, but I got a new modem today and it's doing the exact same thing.

Same bitrate degrading (1400, 700, then 0, then 1400, then 700, then 0) over and over and over again.

I feel like I've run out of options, but does anyone know of anything I can do to fix this? I have a tech coming over Sunday but I'd like to fix it now.
 
23:53:04: RTMPPublisher::SocketLoop: Stalled for 2358 ms to write 271538 bytes (buffer: 0 / 272384), unstable connection?
23:53:07: RTMPPublisher::SocketLoop: Stalled for 3008 ms to write 268529 bytes (buffer: 0 / 272384), unstable connection?
23:53:09: RTMPPublisher::SocketLoop: Stalled for 2558 ms to write 270816 bytes (buffer: 0 / 272384), unstable connection?
23:53:15: RTMPPublisher::SocketLoop: Stalled for 6111 ms to write 269415 bytes (buffer: 0 / 272384), unstable connection?
23:53:18: RTMPPublisher::SocketLoop: Stalled for 2993 ms to write 269930 bytes (buffer: 0 / 272384), unstable connection?
23:53:24: RTMPPublisher::SocketLoop: Stalled for 4098 ms to write 272265 bytes (buffer: 0 / 272384), unstable connection?
23:53:27: RTMPPublisher::SocketLoop: Stalled for 2611 ms to write 272085 bytes (buffer: 0 / 272384), unstable connection?
23:53:29: RTMPPublisher::SocketLoop: Stalled for 2513 ms to write 272246 bytes (buffer: 0 / 272384), unstable connection?
23:53:32: RTMPPublisher::SocketLoop: Stalled for 2833 ms to write 272084 bytes (buffer: 0 / 272384), unstable connection?
23:53:37: RTMPPublisher::SocketLoop: Stalled for 3683 ms to write 272085 bytes (buffer: 0 / 272384), unstable connection?
23:53:39: RTMPPublisher::SocketLoop: Stalled for 1921 ms to write 272265 bytes (buffer: 0 / 272384), unstable connection?
23:53:43: RTMPPublisher::SocketLoop: Stalled for 3851 ms to write 271350 bytes (buffer: 0 / 272384), unstable connection?
23:53:49: RTMPPublisher::SocketLoop: Stalled for 6046 ms to write 268717 bytes (buffer: 0 / 272384), unstable connection?
23:53:53: RTMPPublisher::SocketLoop: Stalled for 4298 ms to write 270628 bytes (buffer: 0 / 272384), unstable connection?
23:53:56: RTMPPublisher::SocketLoop: Stalled for 3313 ms to write 269603 bytes (buffer: 0 / 272384), unstable connection?
23:54:00: RTMPPublisher::SocketLoop: Stalled for 3813 ms to write 272319 bytes (buffer: 0 / 272384), unstable connection?
23:54:03: RTMPPublisher::SocketLoop: Stalled for 3465 ms to write 272027 bytes (buffer: 0 / 272384), unstable connection?
23:54:05: RTMPPublisher::SocketLoop: Stalled for 1779 ms to write 272086 bytes (buffer: 0 / 272384), unstable connection?
23:54:08: RTMPPublisher::SocketLoop: Stalled for 2760 ms to write 272244 bytes (buffer: 0 / 272384), unstable connection?
23:54:10: RTMPPublisher::SocketLoop: Stalled for 1903 ms to write 272087 bytes (buffer: 0 / 272384), unstable connection?
23:54:12: RTMPPublisher::SocketLoop: Stalled for 2272 ms to write 272263 bytes (buffer: 0 / 272384), unstable connection?
23:54:16: RTMPPublisher::SocketLoop: Stalled for 4268 ms to write 272087 bytes (buffer: 0 / 272384), unstable connection?
23:54:20: RTMPPublisher::SocketLoop: Stalled for 3854 ms to write 272077 bytes (buffer: 0 / 272384), unstable connection?
23:54:26: RTMPPublisher::SocketLoop: Stalled for 4692 ms to write 271189 bytes (buffer: 0 / 272384), unstable connection?
23:54:30: RTMPPublisher::SocketLoop: Stalled for 3486 ms to write 269057 bytes (buffer: 0 / 272384), unstable connection?
23:54:35: RTMPPublisher::SocketLoop: Stalled for 5191 ms to write 270273 bytes (buffer: 0 / 272384), unstable connection?
23:54:37: RTMPPublisher::SocketLoop: Stalled for 2363 ms to write 269794 bytes (buffer: 0 / 272384), unstable connection?
23:54:41: RTMPPublisher::SocketLoop: Stalled for 3794 ms to write 272261 bytes (buffer: 0 / 272384), unstable connection?
23:54:45: RTMPPublisher::SocketLoop: Stalled for 3841 ms to write 272070 bytes (buffer: 0 / 272384), unstable connection?
23:54:49: RTMPPublisher::SocketLoop: Stalled for 4606 ms to write 272265 bytes (buffer: 0 / 272384), unstable connection?
23:54:58: RTMPPublisher::SocketLoop: Stalled for 8034 ms to write 272085 bytes (buffer: 0 / 272384), unstable connection?
23:55:07: RTMPPublisher::SocketLoop: Received FD_CLOSE, 9640 ms since last send (buffer: 272263 / 272384)
23:55:07: RTMPPublisher::SocketLoop: Aborting due to FD_CLOSE, error 0
Click to expand...

Your connection is crapping out. Badly.
 
FerretBomb said:
Your connection is crapping out. Badly.
Click to expand...

Yes, but the strange thing is that every speed test I've ran shows that everything is basically the same prior to this stuff happening. I've gone through Comcast's, speedtest.net, and I tried to use ShaperProbe but it never popped up/said the servers were too busy
 
Speedtest.net is worthless for livestreamers on many levels. It tests peak throughput for a set file, not minimum throughput for an active buffer. It also throws out the lowest 30% of results (which are very important for streamers). Most other speed-test sites do the same thing.

Here, go download and run this:
http://www.teamliquid.net/forum/tech-support/478845-twitchtest-twitch-bandwidth-tester

Short version is that your connection to that ingest is boned at the moment. Try switching to another, see if it may help.
Saying that nothing changed and now it doesn't work is about as effective as complaining that your arm wasn't broken before, though. Doesn't matter how it happened or whose fault it is, it's simply not and there may be nothing you can do about it.

Comcast is also NOTORIOUS for connection hostility to Twitch. Could also just be coincidence that Twitchcon is happening this weekend. If I was of a conspiracy-nut bent, I'd wonder if they might be causing it to screw up intentionally, when a lot of eyes are going to be on them, to give a bad impression and damage public interest toward livestreaming. Because it doesn't compete with cable TV at all.

May just have to wait for the tech. Many of them will just run an internal speedtest though and shrug if you have problems visiting any site outside their intranet.
 
I tried TwitchTest, I get about 600 kbps on all servers.

I'd be willing to believe that TwitchCon conspiracy theory if the connection didn't drop constantly trying to stream to Hitbox as well.

Last time I had something like this in an older apartment, the splitter in the attic was old/messed up and they replaced it, after that everything was peachy. I'm hoping that it's something like that.
 
The tech checked the wires, said the signal looked way too strong, weakened it a bit with a splitter, checked the wiring outside, and then found out that the issue is area-based for where I live. So now I'm waiting for that to be fixed for my area.

Also, I have this error even when I have a stable connection:
RTMPPublisher::SocketLoop: Aborting due to FD_CLOSE, error 0

Anyone know what that means and how to prevent it?
 
That means that your connection was unstable enough, or interrupted to the point that the socket was closed. It's another network issue.

Also, I have no idea what your tech was talking about... too STRONG a signal? What? I mean, if it was overpowering the upstream bonded channels I could see that, but a splitter wouldn't fix that, just attenuate the downstream. Which... is a little insane to say that it's too strong and needs to be weaker.

Sounds like you may have been handed some bullshittium to trigger the smile-and-nod, feel better about a placebo fix, and let the tech wrap the call and get to the next one.
 
You must log in or register to reply here.
Back
Top