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). If you want to send a 1080p stream to Clevercast using RTMP, make sure to use our local ingest hub (see 3).
Using interpreters located on another continent with Translate@Home is possible, but make sure to test sufficiently in advance (see 4).
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.
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.
3. Use our local ingest hub if you must use RTMP on another continent
If you do use RTMP for intercontinental broadcasts, this is at your own risk. We cannot guarantee that the connection will remain stable. In practice, we see that lowering the bitrate often offers a solution for unstable streams (eg broadcasting 720p instead of 1080p from the US). Note that we don’t provide support for troubleshooting these broadcasts.
In cases where you must use RTMP, we provide a solution in the form of a local ingest hub. For example, when using a 3rd party solution (eg in-browser studio) which only supports RTMP and has its streaming servers on another continent. In that case we can set up a local ingest hub near the broadcast server, which receives the RTMP stream and sends it to Clevercast using SRT. Currently this must be manually configured, so it involves an extra cost. In a future release, we will provide this as an automated solution.
4. 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. It depends on each individual interpreter’s connection, in Europe or on another continent.
We strongly recommend to follow our general rule of testing sufficiently in advance under circumstances parallel to the live stream. Also make sure your interpreters meet our requirements and best practices.