Firewalls and ports
Please ensure that following ports are open for outgoing traffic: 443, 80 and 1935.
The streams are primarily served via cloud providers where IP ranges or hostnames are not known in advance.
Publishing guide - SDI
- A newer Windows PC (64-bit OS)
- SDI-card (we recommend Blackmagic Decklink)
- SDI-application, provided by Bambuser
- SDI-application credentials provided by Bambuser
Download the SDI application from the Bambuser Dashboard. If you cannot access the Developer page or the SDI receiver software card please ask the administrator of your group to give you permission.
Install it on the platform of choice.
The SDI application has input fields for gid (aka group-id) and api_key.
To access the gid and api_key for an SDI-output, please browse to your Content Dashboard profile. In the “Publish” column you will find Outputs, where publish content using SDI and RTMP. Click on the upper right cog-wheel of the Output you would like to configure to retrieve gid and api_key (illustrated below).
How it works
Videos dropped in the SDI outbox in the Content Management interface will be able to play out over the SDI machine.
The SDI outbox is like a looping playlist and will play videos in the order they appear in the list. If a new video is dragged to the top, it will play out.
Bandwidth requirements: Please allow [2-4 Mbps per stream (depending on resolution etc of the stream)] x [number of streams] x 2
The SDI application is meant to work without manual tuning in most cases, but if the network is too bursty and you are experiencing stuttering/freezing in the video, you can press the "Advanced" button.
By checking the "Override buffering", you are free to configure the buffer parameters. By increasing the "Target buffer size" parameter, you are adding latency to the playback, but also increase tolerance for occasional network variance.
The "Max buffer size" parameter needs to be set accordingly (the application automatically forces this parameter to be at least 0.5 seconds more than the target buffer size); if more data than this happens to be buffered, it tries to skip forward to catch up with real time.
In case playback doesn't seem to work smoothly, there's a built in test tool as well. Make sure to add an archived (non-live) broadcast for testing to the configured outbox (ideally a real world video with real content, ideally a couple minutes long).
Then press the "Test network" button. After running the tests, the application will report the findings, including the roundtrip time to the server hosting the video, the measured download speed, and the required average speed for that particular video.