Using Video Transport
Read this article once you've downloaded and installed the product.
Last updated
Was this helpful?
Read this article once you've downloaded and installed the product.
Last updated
Was this helpful?
We assume that you've already downloaded the ZIP package with Video Transport software. If not, please
Now, you are ready to try Video Transport in two simple scenarios:
remote feed monitoring;
transporting video feeds between two locations.
The quickest way to have a Video Transport experience is via the Web Preview:
Run VT Publisher.
Select the source you wish to publish from the list of available sources (1). Once selected, the preview of the source will start and its parameters (Video Format, FPS) will be shown.
To start publishing, choose the desired bitrate (2) and hit "Start Publishing" (3).
Copy the link from the "URL" tab (4) and paste it into a browser.
Feel free to share the Web Preview link with someone located in a different place.
On the sending side:
Run VT Publisher.
Select the source you wish to publish from the list of available sources (5). Once selected, the preview of the source will start and its parameters will be shown (6).
Copy the Publisher ID (4) and send it to the receiving side (via Skype, email or other form of messaging). You can use the same Publisher ID on multiple instances of VT Publisher and VT Receiver.
You can set a custom name for this particular instance of VT Publisher via the "Location" field – to make it easier to locate this feed in VT Receiver.
To start publishing, choose the desired bitrate (7) and hit "Start Publishing" (11).
On the receiving side:
Run VT Receiver.
Put the same license file into the product folder.
Select one of the available sources in the "Source" tab (5).
Once selected, the preview of the feed will soon start to play.
Select desired protocol in tab 6 (SRT and H.265 are used by default).
Select desired latency in the "Buffer" tab (10).
Select the output method in the "Output" tab (NDI®, a hardware device, or a virtual device) and hit "Start Output" (15).
If these two use cases worked well, feel free to try a more complex scenario: remote contribution via the .
If you have any questions, send us an email to – and we'll do our best to help.