Author: VaughnSoft

VaughnSoft Blog

Encoder restrictions

At the time of this post, we’ve implemented lower and upper bitrate limits for streams. Why? To help improve stability and watchability. Not everyone can watch a 15,000Kbps live stream with 2-5 second latency.

Here are the video and audio bitrate limits:

  • Minimum video bitrate: 100 Kbps
  • Maximum video bitrate: 3500 Kbps
  • Minimum audio bitrate: 32 Kbps
  • Maximum audio bitrate: 320 Kbps

VIP Gold and VPN’s

We’ve got a reputation for blocking VPN’s, it’s no secret. The original reason behind doing that was to slow down malicious users from coming back as easily after being banned from our sites. While we have no intention of allowing VPN’s, it is no secret that many legitimate folks use VPN services in non-malicious ways.

Starting today you can leave your VPN on if you have a VIP Gold account. Normally during the sign in process you’re presented with a message asking to turn off your VPN if you’ve left it on, but if you sign in with your VIP Gold account you will no longer get that message.

-Mark

Watch me daily at https://vaughn.live/mark

Mark broke it!

It’s true, I did it again. This time it’s with the Go LIVE Now broadcast tool. For a while now, many folks have had issues getting our broadcast tool to work. As it turns out, this has been caused by webcams not supporting higher resolutions. But that’s not the best part! Today I discovered that I set the minimum resolution to 640×640 instead of 640×360. How did that happen? I used the minimum width variable for both the width and height.

Yeah, I know.

If you’ve had trouble getting Go LIVE Now to work in the past, even as recent as an hour before this post has been made, refresh and give it another try.

#BlameMark

-Mark

Video system crashes and overheating CPUs

For several months we’ve been trying to track down a very elusive cause of the video system crashing. From extensive configuration changes to all servers to code patches to the primary ingest software by its vendor. Two days ago we set up hyper logging of all OS events and waited for the primary ingest server to crash again. Like clockwork, it crashed last night and shed light on a serious issue. One of the CPUs in the primary ingest server were running over 90c at less than 50% load. This caused the OS to throttle that CPU down significantly which caused the ingest server software to lock up, which caused a domino effect, thus resulting in a complete video system outage.

At 9am, July 12, 2018, the datacenter housing that server is replacing it with an entirely new server. This will cause about 15-30 minutes downtime, unfortunately. But I’d say that’s minimal compared to the frustration the video system crashes have caused us and everyone using our sites for the last several months.

Of course there’s always the possibility that this may not entirely fix the issue. But based on how the video system crashes when that CPU goes into thermal protection, we’re fairly confident that will be resolved with the new server.

Thank you all for sticking with us and being so patient. The amount of lost sleep and frustration thanks to this issue has been incredible and has taken its toll on us. (I’m personally taking a 30 hour nap after all this.) But we’re pushing forward to try and provide the best live streaming experience we possibly can.

Mark Vaughn