Multilingual Livestreams from outside of Europe

It is possible to produce multilingual live streams with Clevercast from outside of Europe. But there are a number of things you should know.


1. Our ingest servers are in Europe, but our streaming servers are worldwide

Our ingest servers are currently located in Europe, which has consequences for broadcasting to Clevercast from other continents (see 2) and for choosing interpreters if you’re using Translate@Home (see 3).

For the delivery of the streams to your viewers, we use global CDNs with local edge servers all over the globe, guaranteeing a fast connection to the viewer’s location. So Clevercast is perfectly suited for global audiences.


2. Broadcasting from another continent: use SRT as your broadcast protocol !

The RTMP protocol has not been created for intercontinental broadcasts over unreliable networks. To broadcast using RTMP over the internet from a location not in or near Europe without interruptions, you will need a very fast and stable connection. Intercontinental network speeds may vary depending on the time of day.

Comparison of maximum bandwidth for long distance streams between RTMP and SRT

Comparison of maximum bandwidth for long distance streams between RTMP and SRT

We therefore strongly recommend using the SRT protocol to broadcast from other continents. SRT is designed to perform very well over long distances and unreliable networks (see this comparison with RTMP by Haivision). In our experience it is perfectly possible to send a HD quality SRT broadcast to Clevercast from anywhere in the world.

With SRT you can choose to send embedded audio streams along with the video, or you can send a single language as the floor language for your translators when using Translate@Home (T@H). If your encoder doesn’t support SRT, you can try using OBS Studio (free) instead.

If you do use RTMP for intercontinental broadcasts, this is at your own risk. We cannot guarantee that the connection will remain stable. We also don’t provide support for troubleshooting these broadcasts. In practice, we see that lowering the bitrate often offers a solution for unstable streams. This also includes RTMP re-streaming from a 3rd party solution on another continent (their connection may be faster and/or more stable, but there is no way for us to know).

Note: in case of large projects where RTMP is required somehow, we can set up a local ingest server that forwards the broadcast to Clevercast using SRT. Since this is strictly on a project basis, it will have an impact on the price.


3. Test sufficiently if you want to use T@H with interpreters on another continent !

T@H uses WebRTC, so a basic requirement for interpreters is that they must have a fast and reliable connection to our ingest servers in Europe.

In this regard, we have found that each case is different. Sometimes, interpreters from another continent sound perfect. On other occasions, there is too much packet drop for realtime translation.

If you want to use interpreters on other continents, we recommend to test sufficiently in advance under circumstances parallel to the live stream.