Kiloview N20 with Callaba: HDMI NDI workflow, SRT bridge, multiview and recording
Written by Iurii Pakholkov
Founder of Callaba. Building cloud video tools for SRT, RTMP, WebRTC, NDI, live routing, monitoring, recording, and production workflows.
Release: Callaba 8.4
Kiloview N20 is a compact HDMI 2.0 to NDI bidirectional converter. It is useful when your source or destination is HDMI, but your local production workflow is built around NDI.
If you searched for Kiloview N20 SRT, the practical answer is: do not start by looking for a direct N20 SRT push profile. Treat N20 as the HDMI ↔ NDI device. If the same feed must enter Callaba Gateway over SRT, add an NDI-to-SRT bridge, for example Callaba Engine, or use a direct SRT-capable device such as N60.
This guide is written for the search intent behind Kiloview N20 SRT, Kiloview N20 NDI, Kiloview N20 HDMI, Kiloview N20 multiview, Kiloview N20 recorder, Kiloview N20 playback and Callaba SRT Gateway.
Quick answer: can I connect Kiloview N20 directly to Callaba Gateway over SRT?
Kiloview N20 does not expose native SRT push or SRT server settings in the standard NDI workflow. Do not try to find SRT-push settings in its web interface — treat N20 as an HDMI ↔ NDI device. For Callaba Gateway over SRT, create a bridge: N20 → NDI → NDI-to-SRT bridge, for example Callaba Engine → Callaba Gateway. If you need native hardware-side SRT without a bridge, use an all-protocol model such as N60 for HDMI.
What this setup does
This workflow connects a HDMI source or destination to an NDI network using Kiloview N20. If the same source needs to be handled by Callaba Gateway as SRT, do not debug N20 as if it were a direct SRT encoder first. Use an intermediate NDI-to-SRT bridge or another SRT-capable device.
- N20: HDMI input, loop-through or output in an NDI workflow.
- NDI-to-SRT bridge: converts the NDI source into SRT for cloud contribution.
- Callaba Gateway: receives SRT, then enables browser multiview, cloud recording, playback, routing and downstream delivery.
N20 role: HDMI to NDI first
The main mistake is to force N20 into the wrong protocol role. It is better to treat N20 as the HDMI-to-NDI or NDI-to-HDMI part of the system. Then decide where the NDI-to-SRT conversion should happen.
Important distinction: N20 is best treated as an HDMI ↔ NDI device in this workflow. If you need direct SRT from the hardware into Callaba, N20 is usually not the right first choice. Use N20 when the local workflow is HDMI ↔ NDI. Use N60 or another all-protocol encoder/decoder when the hardware itself must send or receive SRT directly.
Before you start
Prepare the NDI path before you create the Callaba SRT path. If NDI is unstable before the bridge, Callaba cannot fix that later in the chain.
Protocol warning: Kiloview N20 does not expose native SRT push/server settings in the standard NDI workflow. It is an NDI device here. The SRT part must be handled by Callaba Engine, OBS/FFmpeg in a lab setup, another bridge, or direct SRT-capable hardware.
Bridge workflow: NDI to SRT to Callaba
Use this path when the source starts as HDMI 2.0, N20 turns it into NDI, and the production needs that source inside a Callaba SRT workflow.
A typical Callaba SRT listener URL for the bridge output can look like this:
srt://YOUR_CALLABA_IP:10190?mode=caller&latency=200&streamid=kiloview-n20-bridge-mainUse this as a field-format example only. The bridge, not the N20 itself, sends this SRT stream to Callaba.
Practical option: use Callaba Engine as the NDI-to-SRT bridge
This is the cleanest Callaba-native path when N20 is already part of your local NDI network. One Callaba Engine instance can run near the NDI device and see the N20 source. Another Callaba Gateway instance in the cloud can receive SRT.
- Connect the HDMI source to N20 and confirm the N20 NDI source is visible on the local network.
- Open the local Callaba Engine instance and check the NDI discovered devices area. Your N20 source should appear there before you build the SRT path.
- Open the cloud Callaba Gateway instance. Go to SRT Servers and click Add New.
- Name the SRT server. If you are not sure which port to use, keep the default port, often
10090, and make sure that UDP port is open in the cloud firewall or security group. Save the server and copy the generated SRT Publisher URL. - Return to the local Callaba Engine instance. Open Restreams and click Add New.
- In Input settings, set Input Type to NDI Device. In the Device dropdown, select the N20 source.
- In Destination settings, set Stream Destination to SRT Output URL.
- Paste the copied SRT Publisher URL into Output Stream URL, save, and start the restream.
- Switch back to cloud Callaba Gateway and verify preview, bitrate, codec, audio and connection state.
Full walkthrough: use Set up NDI® bridge over SRT for the complete Callaba bridge flow.
Lab option: OBS or FFmpeg as the NDI-to-SRT bridge
For a fast lab test, a workstation can act as the bridge. This is useful for proof-of-concept. For production, I prefer Callaba Engine because it keeps ingest, monitoring and routing inside the same operational model.
OBS-style test
- Install an NDI source plugin compatible with your OBS version.
- Add the N20 NDI source to an OBS scene.
- Use an OBS output method that can send SRT through FFmpeg or a compatible SRT output plugin.
- Send the output to the Callaba SRT listener URL.
- Verify in Callaba that the stream connects and that audio, codec, bitrate and preview are correct.
FFmpeg-style lab command
FFmpeg warning: standard FFmpeg builds usually do not include NDI input support. This command needs a special FFmpeg build compiled with NDI SDK support, or another build that already includes NDI. For a quick lab test, OBS with an NDI source plugin is usually easier.
ffmpeg -f libndi_newtek -i "N20 Camera 1" \
-c:v libx264 -preset veryfast -b:v 8000k \
-c:a aac -b:a 128k -f mpegts \
"srt://YOUR_CALLABA_IP:10190?mode=caller&latency=200&streamid=kiloview-n20-bridge-main"Use this as a lab template, not as a universal production command. Replace the NDI source name, bitrate, host, port, latency and stream ID with your actual values.
N20 vs N40 Plus/N60 for SRT workflows
Many people searching for “Kiloview N20 SRT” are really trying to decide whether N20 is the right hardware for Callaba Gateway. This table keeps the decision simple.
N40 Plus note: N40 Plus is also an NDI-first HDMI converter in this comparison. Like N20, it needs a bridge for a Callaba SRT Gateway workflow. If you want native HDMI-to-SRT without a bridge, use N60 instead.
| Model | Direct SRT path | Main role | Video I/O | Recommendation |
|---|---|---|---|---|
| N20 | Use bridge for Callaba SRT workflow | HDMI ↔ NDI | HDMI 2.0 | Use when the local job is HDMI ↔ NDI. Add bridge for Callaba SRT. |
| N40 Plus | Use bridge for Callaba SRT workflow | Newer HDMI ↔ NDI High Bandwidth | HDMI | Use for newer HDMI NDI workflows. Still bridge for SRT. |
| N60 | Yes, all-protocol workflow | 4K HDMI all-in-one encoder/decoder | HDMI | Use when you need HDMI and direct SRT from the hardware. |
Device choice rule: if you need direct SRT from HDMI without a bridge, choose N60. Choose N20 only when the core workflow is HDMI ↔ NDI, or when you already own N20 and can add a bridge.
Settings table
This table helps keep the NDI side and SRT side separate.
| Setting | N20 side | Callaba side | Why it matters |
|---|---|---|---|
| Protocol | NDI | SRT after bridge | Do not confuse the NDI device with the SRT ingest endpoint. |
| Device role | NDI encoder or decoder | SRT input or output route | Direction decides the whole workflow. |
| Network | Gigabit network for NDI | Open SRT listener port | NDI bandwidth is high before bridge compression. |
| Resolution / FPS | Up to 4Kp60 HDMI workflow | Match bridge SRT output | A bridge can change format, bitrate or codec. |
| Audio | HDMI embedded or analog audio path | Detected after SRT ingest | Audio must be confirmed after the bridge, not only on the NDI side. |
N20 multiview workflow with Callaba
N20 can create or receive an NDI source, but Callaba multiview becomes relevant after the feed reaches Callaba as a supported live input. In an SRT Gateway workflow, that means the NDI source must first be bridged into SRT.
Interactive check: open the Callaba multiview demo to see how a received source can look after cloud ingest. Your N20 source would appear there only after it enters Callaba through a bridge or a supported ingest path.
N20 recorder workflow: NDI source vs Callaba cloud recording
The N20 side and the Callaba side protect different points in the workflow. N20 handles the HDMI ↔ NDI conversion. Callaba records what actually arrived after the NDI-to-SRT bridge or another ingest path.
| Layer | What it verifies | Use case |
|---|---|---|
| NDI/source-side check | That HDMI reached the NDI network correctly. | Use during local setup and source validation. |
| Callaba cloud recording | That the bridged SRT stream actually reached Callaba. | Use when you need cloud-side proof of the received workflow. |
N20 playback workflow with Callaba
Playback also has two meanings. N20 can decode NDI to HDMI inside the local NDI network. Callaba playback means browser player, HLS output, embed link or a cloud route after Callaba receives the stream.
HLS playlist after Callaba ingest:
https://YOUR_CALLABA_DOMAIN/hls/kiloview-n20-bridge-main/playlist.m3u8
Player or embed page:
https://YOUR_CALLABA_DOMAIN/embed/kiloview-n20-bridge-mainWhere the links come from: These example URLs are not generated automatically for every stream. Callaba creates them after you create a web player or HLS packaging path for the incoming bridged stream. Depending on your configuration, links may include temporary tokens or authorization parameters.
Troubleshooting
Most issues come from mixing up NDI and SRT responsibilities. Check the HDMI/NDI side first, then the bridge, then Callaba.
1. No SRT connection in Callaba
- Confirm the SRT sender is the bridge or another SRT-capable device, not the N20 itself.
- Confirm Callaba is listening on the expected UDP port.
- Check stream ID, passphrase and latency on the SRT sender.
2. NDI source is not visible or unstable
- Confirm N20 is in the correct encoding or decoding mode.
- Check HDMI signal, NDI discovery and network segment.
- Use a stable Gigabit network for NDI and confirm the bridge can see the same NDI source.
- If you see artifacts, drops or discovery issues before the bridge, check switches, cables, link speed and total NDI traffic. The bridge cannot repair problems that already exist on the NDI side.
- If N20 is not visible in the NDI source list on a Windows workstation, check NDI Access Manager and Windows Firewall rules. Discovery can fail even when the device itself is online.
3. Connected, but no picture in Callaba
- Check the NDI-to-SRT bridge output codec.
- Start with H.264 and 1080p30 before testing 4Kp60.
- Check audio mapping after the bridge, not only on the HDMI or NDI side.
Official and technical references used for this guide
Use these if you need N20 device role, HDMI limits, NDI bitrate notes, SRT background or bridge details before configuring a production workflow.
FAQ
Can Kiloview N20 send SRT directly to Callaba Gateway?
No. In the standard NDI workflow, Kiloview N20 does not provide native SRT push/server settings. Treat N20 as an HDMI to NDI bidirectional converter. To use Callaba SRT Gateway, add an NDI-to-SRT bridge such as Callaba Engine, or choose a direct SRT-capable model such as N60.
How do I bridge N20 NDI to Callaba SRT?
Use a Callaba Engine instance, OBS/FFmpeg test bridge, or another NDI-to-SRT bridge. The bridge receives the N20 NDI source and sends SRT to a Callaba Gateway listener.
Can I use N20 with Callaba multiview?
Yes, after the N20 source enters Callaba through a supported ingest path. In an SRT Gateway workflow, this usually means NDI is bridged into SRT first.
Should I use N20 or N60 for direct SRT?
Use N20 when the job is HDMI ↔ NDI and you already have an NDI bridge path. Use N60 when you need direct SRT from HDMI hardware.
Final practical rule
Do not force N20 into the wrong role. Use N20 for HDMI ↔ NDI. Do not treat the N20 web UI as the SRT sender in this workflow. Use Callaba Gateway for SRT ingest, monitoring, recording and playback after the stream becomes SRT through Callaba Engine, another NDI-to-SRT bridge, or direct SRT-capable hardware.
Last updated: May 16, 2026
Try Callaba Gateway with your NDI-to-SRT workflow
Create an SRT listener in Callaba, send your bridged N20 source to the gateway, and monitor the feed before routing it to recording, restreaming, multiview, playback or player delivery.
See SRT server setup Open multiview demo Read NDI bridge guide See N60 direct SRT setup