Question / Help Dropped Frames v0.16.0 and Up

[Andy-BDE]

Hi everyone, having an issue with 0.16.0 (and 0.16.2) randomly stopping its live stream. Dropped frames just seem to rack up between 15-20 mins into a stream. Checked to ensure there were no issues with internet or with our CDN. Rolled back to 0.15.4 and it doesn't happen. Anyone else have this issue? I'm thinking I just need to stick with 0.15.4 until it's resolved. I have log files from 1 computer.

Here's a log from the last 0.16.0 session where it stopped streaming --http://pastebin.com/raw/nqpYcig3

Here's a log from after we rolled back to 0.15.4 which stayed streaming without issue for the final hour or so -- http://pastebin.com/raw/gaD1m0AK

 

[Osiris]

It's probably related to this fix:
"Fixed an issue where frames wouldn't drop under certain circumstances and become more delayed than expected."

So in 0.15.4 your stream would just become more and more delayed, while in 0.16.0 and above it would actually work as designed and drop the frames.

Do this test and post a screenshot: http://www.teamliquid.net/forum/tech-support/478845-twitchtest-twitch-bandwidth-tester

 

[Andy-BDE]

We were monitoring the stream closely and once on 0.15.4 it never strayed from being more than 5-7 seconds behind real time, which is where it should be. Any version on 0.16.0 would stop streaming entirely. Not sure how that would be the "correct" way of functioning. There was a memory leak noted at the end of the bad stream log. Does that have any bearing on the results? Also we had this issue occur on 3 separate computers streaming from 3 separate locations and they all went down at the same time...except when we rolled back 1 of them to 0.15.4. After that, the two computers on 0.16.0 stopped streaming at the same time while the 0.15.4 one kept going without issue. We rolled back the other two systems to 0.15.4 and they streamed without a problem from there on as well. So there has to be something wrong with the 0.16.0 build.

 

[Osiris]

If there was something wrong with 0.16.0, we would have heard about it from more people though.

 

[Andy-BDE]

I see plenty of reports of issues in the forum. Maybe no one has quite tested this specific combination of factors to yield this result? We've been troubleshooting this issue for 2 weeks now, trying different OBS versions and altering stream settings (initially thinking it was a lack of bandwidth issue), but last night's test was the first definitive session where we could dial it into a specific version of OBS causing a specific result. I'll use the Twitchtest you mentioned for any areas that experience problems tonight but I'm going to be rolling all of my systems back to 0.15.4 for the time being because it was fairly consistent last night that every 15-20 minutes any stream using 0.16.0 would just completely stop streaming. It happened 3 times before we were able to get all 3 systems rolled back to 0.15.4 and then they were all clean for 90 minutes afterward and that is the only factor we changed. None of the hardware was altered, stream settings (upload bit rate, encoding method, etc.) were kept the same, available bandwidth from each site stayed the same. Our CDN reset their entire server after the initial freeze to eliminate their side of things as a possibility and the freezes still kept happening until we did the roll back on the local systems.

 

[Harold]

Sounds like the routes between the local systems and the CDNs have taken the piss.