So you’ve successfully created a live stream on your StreamingVideoProvider Platform. Great! Now what? Before you go live, here are a few tips and tricks to help your stream run smoothly.

1. Choose an Encoder That Sends Multiple Streams

Having multiple streams is a good way to ensure your live stream is viewed without issue. With the right encoder, you can send three separate streams to our platform which will trigger adaptive bitrate.

We recommend using FMLE on Mac or Wirecast as both can send three separate streams to our platform. Alternatively, any other RTMP encoder that can send multiple streams (with different resolutions and bitrates) will work.

2. Recommended Bitrates For The Different Resolutions:

2K - up to 8 Mbits when multiple streams are sent from your RTMP encoder or up to 4 Mbits for a single stream.

1080p - up to 6 Mbits when multiple streams are sent from your RTMP encoder or up to 4 Mbits for a single stream.

720p - up to 2 Mbits

480p - up to 1 Mbits

360p - up to 0.6 Mbits

240p - up to 0.2 Mbits

Use an Optimal Bitrate with OBS

When streaming with OBS, it’s important to make sure your bitrate is well within the optimal range to avoid annoying buffering. We recommend streaming at a bitrate less than 4 mbps.

3. Use the Right Codecs
Make sure your RTMP encoder is set to stream with H.264 video codec and AAC for audio codec. If MP3 audio codec is used, iOS devices will not have sound. Any other codecs will trigger the delivery to go via our fallback Flash Player instead of the default HTML5 player.

4. Use Network Connection

It’s best to avoid streaming over Wi-Fi or 4G. To avoid any interruption in streaming, use a high-speed network connection.

5. Run a Speed Test

Running a speed test is an absolute must before going live. This will tell you if you have a strong enough connection. Go to speedtest.net and ensure the upload is at least 30% higher than the total bitrate that is set in the RTMP encoder.

Troubleshooting:

  • If you’re experiencing connection issues to the primary ingest publishing point rtmp://livecast.webvideocore.net/live, you can temporarily use any of the following alternatives:

rtmp://cast3ch.webvideocore.net/live USA , New Jersey

rtmp://cast4uk.webvideocore.net/live UK, London

rtmp://cast6sg.webvideocore.net/live Singapore

rtmp://cast8au.webvideocore.net/live Australia, Sydney

rtmp://cast9br.webvideocore.net/live Brazil, Sao Paulo

rtmp://cast10in.webvideocore.net/live India, Bangalore

rtmp://cast11uk.webvideocore.net/live UK , London

rtmp://cast13mi.webvideocore.net/live USA, Miami

rtmp://cast16nl.webvideocore.net/live Netherlands

rtmp://cast17wa.webvideocore.net/live USA, Washington

rtmp://cast18dal.webvideocore.net/live USA, Dallas

rtmp://cast19mi.webvideocore.net/live USA, Miami

rtmp://cast20il.webvideocore.net/live USA, Chicago

rtmp://cast21la.webvideocore.net/live USA, LA

NOTE: This is only a temporary solution. We STRONGLY recommend always using rtmp://livecast.webvideocore.net/live

  • In case of an issue before or during the event, contact us via the live chat widget and provide the following:
  1. ClipID of the live stream (which you can find here)
  2. Ping and tracert to the RTMP address used in the encoder (See how to ping on Mac , Windows)
    Example:
    ping livecast.webvideocore.net
    tracert livecast.webvideocore.net

  3. Screenshots of your RTMP broadcasting equipment/software where we can see the type of RTMP encoder you are using and the RTMP details ( RTMP address and stream key, as well as the bitrate of the video and audio streams )
  4. A detailed description of the problem and ways for us to reproduce the error

NOTE: This information is imperative in order for us to resolve the issue, so be sure to provide us with this information immediately.

Did this answer your question?