The Kiloview RE-3 is a current multi-input encoding card, not a decoder. Put it in an RU01 or RU03 chassis, choose HDMI, 3G-SDI or USB as the production source, and use SRT to carry the encoded programme feed into Callaba. Callaba then becomes the operational receiving layer: operators can inspect transport health, monitor the picture, record the source, route it or place it in Multiview.
The setup is easier when you decide three things in order: which physical input is authoritative, which encode profile the receiver can decode, and which side should accept the SRT connection. Starting with the protocol before answering those questions usually creates an impressive-looking configuration that still produces the wrong picture or audio.
Choose the source the operator is expected to trust
Kiloview specifies one HDMI 1.4b input, one 3G-SDI input, USB-A or USB-C input, and a 3.5 mm line input. The card supports H.264 and H.265 encoding and uses Gigabit Ethernet. These inputs are not interchangeable in a live plan:
| Input | Verified ceiling in Kiloview's specification | Typical reason to choose it |
|---|---|---|
| HDMI | Up to 3840×2160p30; HD modes up to 1080p60 | A local switcher, camera or presentation source that already delivers the programme over HDMI. |
| 3G-SDI | Up to 1920×1080p60, with HD-SDI and SD-SDI compatibility | A broadcast chain where locking, cabling and embedded SDI audio are already part of the operating standard. |
| USB | Up to 1920×1080p60 on listed modes | A supported UVC camera or USB source that has been tested with the installed firmware. |
RE-3 can use HDMI and SDI together for PIP or PBP layouts. That is useful when the composition belongs at the edge. It is not the same as sending two independent programme feeds and switching them later in Callaba. Decide whether the card should create one composed output or whether each source needs its own contribution path.
Start with the profile most likely to work everywhere
RE-3 supports H.264 AVC and H.265 HEVC. For a first Callaba test, H.264 with a receiver-supported audio codec is the conservative choice: it removes decoder compatibility from the initial network test. Move to H.265 only after confirming that every downstream operation—preview, recording, restreaming or playback—accepts the chosen profile.
Audio deserves its own preflight check. Kiloview's RE-3 firmware notes explicitly state that SRT does not support G.711a/u audio encoding on this device. Do not interpret a connected SRT session as proof that audio is valid. Select a supported codec such as AAC where appropriate, map the intended embedded or line input, and verify actual audio in Callaba.
If the production needs four embedded channels, preserve channel order from the selected input and check each channel rather than listening only to the first pair. The current product specification lists up to four embedded channels from HDMI, SDI and USB.
Choose the SRT mode pair from the network boundary
Kiloview's SRT documentation defines Caller, Listener and Rendezvous. The mode does not describe which device encodes or receives video; it describes which endpoint initiates the SRT session.
- RE-3 encodes the selected HDMI, SDI or USB source.
- RE-3 Caller opens an outbound SRT session from the venue.
- Callaba Listener accepts the feed on the assigned UDP port.
- Callaba operators validate bitrate, RTT, loss, audio and preview before enabling downstream jobs.
- RE-3 Caller → Callaba Listener
- Best default for a venue or remote site. The card initiates outbound traffic, and the controlled Callaba endpoint owns the public listening port.
- Callaba Caller → RE-3 Listener
- Useful on a managed private network or VPN where Callaba can reach the card directly. On the public internet it requires intentional inbound UDP access to the RE-3 network.
- RE-3 Rendezvous ↔ Callaba Rendezvous
- Reserve for a tested network design in which both endpoints expose the mode and both sides have compatible port mapping. Do not choose it merely because neither side's Listener setup has been completed.
Connect RE-3 to a Callaba SRT Listener
- Install and discover the card. RE-3 is designed for RU01/RU03. Unlike older cards that commonly used a fixed default address, Kiloview notes that RE-3 obtains an address through DHCP at first use. Find it from the chassis or local discovery workflow before opening its web interface.
- Confirm input lock. Select HDMI, SDI or USB, confirm the expected resolution and frame rate, and check every required audio channel.
- Create the encode profile. Start with one H.264 output and a known audio mapping. Keep PIP/PBP, overlays and extra destinations off until the base feed is validated.
- Create the receiver in Callaba. Add an SRT server in Listener mode, assign a UDP port, and set Stream ID and a passphrase only if the operating policy requires them. Make that UDP port reachable at the Callaba endpoint.
- Add an SRT stream service on RE-3. Set the connection mode to Caller, enter the Callaba address and port, and match latency, payload, encryption and optional identifiers.
- Start the stream and inspect transport. A stable session should show sustained bitrate in Callaba, a valid picture and audio, and transport statistics that make sense for the actual network.
Kiloview documents 125 ms latency, 1316-byte payload and 25% bandwidth overhead as defaults in its SRT guide. They are useful starting values. Production values should reflect measured RTT, loss and available upload capacity, not a copied screenshot.
Turn one connected feed into an operational path
Do not switch on every RE-3 destination and every Callaba feature during the first handshake test. Prove the contribution path, then add responsibilities deliberately:
- Monitoring: keep the RE-3 source in Callaba Multiview with visible connection and media state.
- Recording: decide whether the authoritative recording belongs at the edge, in Callaba, or in both places. RE-3 supports recording while streaming, while Callaba can centralize event recordings with the receiving workflow.
- Recovery: add a separately encoded backup source and configure manual or automatic failover in Callaba. A second output from the same card does not protect against card, chassis, power or source failure.
- Distribution: let Callaba create downstream routes or restreams when several receivers need the same programme. This keeps venue upload predictable and gives the operator one place to observe delivery.
- Automation: after the UI workflow is stable, create or control the receiving endpoint through the Callaba SRT Server API.
Respect the verified boundaries
- RE-3 is an encoder card. It accepts baseband or USB sources and creates IP streams. It is not the RD-350/RD-260 decoder card or the RMG-300v2 media-gateway card.
- 4K applies to HDMI, not 3G-SDI. Kiloview lists HDMI up to 4Kp30 and SDI up to 1080p60.
- NDI support is HX2/HX3. The official specification does not claim NDI High Bandwidth for RE-3. NDI HX is useful inside a managed LAN; direct SRT is usually the clearer WAN contribution path.
- G.711a/u is not an SRT audio option on the cited firmware. A transport session can be healthy while the chosen audio codec remains incompatible.
- Destination-count wording is inconsistent on the vendor page. Its heading says up to eight destinations while the body says four platforms simultaneously. Validate the required output count on current firmware rather than designing to the larger marketing number.
- Firmware changes behavior. Record the installed version in the runbook and retest after upgrades, especially API authentication, recording and streaming settings.
Fast fault isolation
| What you see | What it usually means | Next test |
|---|---|---|
| Callaba never sees a session | Wrong mode pair, address, UDP port or firewall path | Use RE-3 Caller and Callaba Listener; test reachability to the exact public endpoint. |
| Session connects, preview stays black | Input is not locked or the encode profile is not accepted | Check RE-3 input status, then retry with one H.264 source and no PIP/PBP. |
| Video is good, audio is absent | Wrong input mapping or unsupported audio codec | Select the intended embedded/line source and replace G.711a/u on SRT with a supported codec. |
| Periodic freezes | Bitrate exceeds usable uplink or latency is too low for measured loss/RTT | Correlate Callaba loss and retransmits with venue upload; reduce bitrate or raise latency. |
| NDI works locally, SRT does not | They are separate stream services and network paths | Create an explicit SRT service; do not assume the active NDI HX output also publishes SRT. |
Primary sources used for this guide
Build the receiving side in Callaba
Use the Callaba SRT Server page to create the Listener and inspect the received feed. Once the RE-3 path is stable, open the live Multiview demo to see how an operator can monitor primary and recovery sources in one interface, or continue to the SRT Server API for repeatable provisioning.
