There are many different things that could be affecting your stream quality. This guide will take you through some basic troubleshooting to ensure that you’re all set up correctly and will help you troubleshoot what your issue may be.
We are working hard every day testing and improving the service so don’t think that because these steps didn’t work you can never stream on Glimesh. It may just be the right fix going in place for you to have a successful stream so keep an eye on #site-updates. Also feel free to experiment and report on what works for you. These settings should be the best available options but some user’s networks may have better success with other encoder settings.
Any questions feel free to reach out to #streaming-help via our discord or firstname.lastname@example.org
FTL - Faster than light, an ultra-low-latency streaming protocol originally used by Mixer and now being used by Glimesh.tv to deliver sub-second stream latency
OBS - Open Broadcaster Software (https://obsproject.com/)
Streamlabs - Streamlabs Desktop (https://streamlabs.com/streamlabs-live-streaming-software)
Because streaming to Glimesh.tv using the FTL protocol is designed to be ultra-low-latency, it can be very sensitive to network issues such as lost or delayed packets. You may be able to stream at a high bitrate to other services but struggle to get a stable FTL stream with the same settings. While we are continuously working to improve the streaming experience, for now the most effective step is generally to reduce your bitrate.
However we have seen cases where users were able to diagnose problems with their network using the below steps and fix them by calling their ISP (internet service provider) or by replacing faulty network cables or other equipment.
Glimesh.tv Stream Debug Information
Open your stream page and click the signal strength icon to see statistics about your stream.
If you see lost / nack'd packets under the stream section you may have network issues, please read through the other network troubleshooting sections. If your viewers see lost packets under the "edge" section your viewers may have network issues.
We will be improving this information in the future as we find how to make it more useful.
FTL is currently especially sensitive to packet loss, even a single lost packet can cause video to drop out briefly for your viewers so we want to see 0% loss here. We recommend heading over to https://packetlosstest.com/, select the 720p preset approximation if you stream at 720p and select the closest server to you.
Both of these results have 0% packet loss which is good. A small amount of variability in packet latency (aka jitter) can be okay.
The left result has both a large spike in latency and packet loss, the right result has both spikey latency and packet loss. Both results indicate you may see significant stuttering and dropped video frames.
What To Do
If you are experiencing packet loss there are a few things you can do. Try restarting your router, check all the cables are undamaged, and try replugging everything in to confirm the connections are snug. Check your network, router, and modem drivers/firmware to make sure they’re up to date. If the issue still persists, consider calling your ISP. Some ISPs will not acknowledge late or lost UDP packets as an issue, but generally if you are experiencing this it will also be impacting the quality of your gaming or video conferencing experience on your network.
You can try reducing your video bitrate, sometimes pushing less video packets reduces how often packets are lost or delayed.
Common causes for delayed/lost packets is network congestion, outdated infrastructure, an outdated modem, or insufficient signal strength. Calling your ISP may get them to change settings or upgrade hardware that improves your experience.
Also make sure you are not connected to a VPN as these can cause issues as well.
As a protocol capable of sub-second latency, FTL is sensitive to variable latency (aka jitter) where some packets are significantly delayed. The above packetlosstest.com site does a good job of measuring average jitter so we always recommend running that first.
If you have a high jitter (>150ms) we also recommend using http://www.dslreports.com/speedtest to test for bufferbloat lag on uploads. If you have a poor BufferBloat score (D or lower) we recommend you contacting your ISP for assistance and if you are technically included read through the self-help guide here: https://www.bufferbloat.net/projects/bloat/wiki/What_can_I_do_about_Bufferbloat/
In the below example a user on a 4G network has several issues. They on average have a 70ms latency with 8mbps upload which should be sufficient for a 2500kbps stream. However even at idle we see some packets can be delayed 1400ms. If this happens while streaming it would likely result in dropped frames or the stream cutting out. Also while under load (e.g. uploading a file) we see latency increases to 800ms. This means if you are streaming away and any device on your network uploads data it could cause significant spikes in latency that would likely result in dropped frames or the stream cutting out.
This buffering while under load is called BufferBloat. Making sure nothing else is using your network while streaming may help but we've had reports of things as simple as a music player loading the next track causing stream dropouts. Your ISP may be able to assist you with this.