It is perfectly possible to produce multilingual live streams with Clevercast from outside of Europe. But there are a number of things you should know.
1. Our streaming servers are worldwide
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. Our ingest servers are in Europe
Our ingest servers are currently only located in Europe, which has consequences for broadcasting to Clevercast from other continents. To send a full HD broadcast from outside of Europe, make sure to use the SRT broadcast protocol or ask us to set up a local ingest hub.
Using the SRT 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). It is perfectly possible to send a full HD 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.
RTMP broadcasts from Streamyard, Zoom …
Even if you are located in Europe, Streamyard and Zoom will actually send their broadcast from a server in the US. Therefore, Clevercast provides a local ingest hub which receives the RTMP stream and relays it to Clevercast using SRT. So if you are broadcasting from Streamyard or Zoom, you must select the
Translate@Home RTMP from Streamyard, Zoom... (US East ingest hub) broadcast protocol when creating an event.
Note that many other in-browser studio’s or meeting solutions will also send their RTMP broadcast from the US. If you are using another application and you don’t know its broadcast location, let us know in advance so we can check it for you.
RTMP broadcasts with a custom ingest hub
If you need to use RTMP for an intercontinental broadcast, we can set up a local ingest hub (nearby your broadcast location) which receives your RTMP stream and relays it to Clevercast using SRT. In that case, you must select
Translate@Home RTMP using custom Ingest Hub as broadcast protocol when creating an event.
If you do use RTMP directly for intercontinental broadcasts (without the ingest hub) this is at your own risk. We cannot guarantee that the connection will remain stable. An unstable connection may result in interruptions in your stream and partial recordings. 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 or restoring the recordings from these broadcasts.
3. Interpreters can be located outside Europe
WebRTC is made for worldwide communication in real time, so interpreters don’t have to be located in Europe. 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 best practices.