Remote video production FAQ
The hidden secrets
behind our point-to-point streaming technology.
Get Video Transport app
Just type your contacts
Your email address:
What can I use it for?
There are at least two use cases, where we've seen people use this product:

  1. Remote video production—check our blog post, where discuss how you can have cameras feed raw streams back to the studio, where the actual switching, CG and commentary are done.
  2. Video transport for contribution—replace expensive point-to-point streaming solutions.
How does it work?
Let's say we have location A running the Publisher and location B running the Receiver. We've connected submitted the Publisher ID in the Receiver and have hit "Start Publishing" in the Publisher app.

The applications will do the following:

  1. The Publisher will connect to our address server via TCP port 8080 and register the Publisher ID.
  2. The Receiver will also connect to the address server via port 8080 and look for the Publisher ID.
  3. If both connections are successful, both locations will receive enough information to establish a peer-to-peer connection.
  4. The Publisher and Receiver will attempt to connect to each other using this information and, if successful, video transfer will begin.
  5. If not successful (such as if one of the locations is under a symmetric NAT or if a firewall is blocking port range 1024-65536), the peers will use our TURN server via a UDP connection at port 3478. All traffic in this case will be routed through the TURN server and latency may slightly increase.
I can see the Publisher's source in my Receiver, but I am not getting any video—what is wrong?
Most probably, the locations could connect to the address server and have received the data they need in order to connect to each other. However, for some reason, they couldn't establish a direct P2P connection. In this case, they would automatically try to connect via the TURN server.

But one of the locations could not connect to the TURN server. Please check UDP and TCP for port 3478.
What bandwidth do you recommend?
Our technology currently supports up to 50 Mbps.

The following minimum bit rate is required:

  • 20 Mbps for 4K;
  • 15 Mbps for 1080p;
  • 10 Mbps for 1080i or 720p.

In order to achieve proper video quality, we recommend the following values:

  • 40 Mbps for 4K;
  • 30 Mbps for 1080p;
  • 20 Mbps for 1080i or 720p.

Keep in mind that we use adaptive bit rate, so quality will dynamically decrease if bandwidth is not available.
I have a 100 Mbps connection: why doesn't my bandwidth in the app go above 20 Mbps.
Even if you set 50 Mbps as your streaming bitrate, the encoder will use only the maximum bandwidth that is needed for this particular content.

For instance, if the input is an upscaled SD stream or a white wall in 4K, a lot less bandwidth will be required to transmit this is stream in it's original quality.
Do I need to configure the networks in any way?
In many situations—no.

In some situations you might need to make sure that port 8080 is open for TCP.

In more sophisticated situations (such as a symmetric NAT or firewall), you'll need to open port 3478 for TCP and UDP to allow traffic to be relayed via our server.
Why does quality get worse if I see the TURN indicator?
If you have made sure that you have the bandwidth you need on both locations, the reason may be that the connection to our TURN server is not good enough.

If this is something you observe, please reach out and we will look for a solution.
How many streams can be encoded by one PC?
There are no limitations for this in the app itself. We recommend the QUADRO P2000 with NVIDIA's GPU on board if you want to build a systems that encodes 6 streams concurrently.
Do support alpha channel?
Do you plan to charge for this?
Our goal is to have both a free version (with watermark) and a paid subscription. Feel free to reach out if you have a real use case for this.
Give it a try today!