Kiloview N6 with Callaba: HDMI and USB NDI workflow, SRT bridge, multiview and recording

May 19, 2026

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 N6 is a compact HDMI and USB to NDI encoder/decoder. It is useful when your source is HDMI or USB, but your local production workflow is built around NDI High Bandwidth or NDI HX.

If you searched for Kiloview N6 SRT, the practical answer is: do not start by treating N6 as a direct SRT encoder. In the standard NDI workflow, N6 is not the place where you configure SRT push. Treat N6 as the HDMI/USB → 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 N6 SRT, Kiloview N6 NDI, Kiloview N6 HDMI, Kiloview N6 USB camera, Kiloview N6 multiview, Kiloview N6 recorder, Kiloview N6 playback and Callaba SRT Gateway.

Quick answer: can I connect Kiloview N6 directly to Callaba Gateway over SRT?

Kiloview N6 does not provide native SRT push/server settings in its standard NDI workflow. Do not look for SRT output settings inside the N6 web interface. Use N6 as an HDMI / USB → NDI device. For Callaba Gateway over SRT, create a bridge: N6 → 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.

N6 solves the HDMI/USB to NDI part. Callaba receives SRT after a bridge or direct SRT-capable device exists.

What this setup does

This workflow connects an HDMI source, USB camera, or NDI return path to an NDI network using Kiloview N6. If the same source needs to be handled by Callaba Gateway as SRT, do not debug N6 as if it were a direct SRT encoder first. Use an intermediate NDI-to-SRT bridge or another SRT-capable device.

N6: HDMI input, USB camera input, or HDMI 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.

N6 role: HDMI and USB to NDI first

The main mistake is to force N6 into the wrong protocol role. It is better to treat N6 as the HDMI/USB-to-NDI or NDI-to-HDMI part of the system. Then decide where the NDI-to-SRT conversion should happen.

N6 is the HDMI/USB-to-NDI boundary. Callaba is the cloud SRT workflow after a suitable SRT source exists.

Important distinction: N6 is best treated as an HDMI / USB → NDI device. If you need direct SRT from the hardware into Callaba, N6 is usually not the right first choice. Use N6 when the local workflow is NDI High Bandwidth or NDI HX. 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: N6 is an NDI HB/HX device in this workflow. The SRT part must be handled by Callaba Engine, OBS/FFmpeg in a lab setup, another bridge, or direct SRT-capable hardware.

Source signal Confirm whether the source is HDMI or USB camera, then verify that N6 receives it correctly.

NDI mode Decide whether the working output is NDI High Bandwidth, NDI HX2 or NDI HX3.

USB camera compatibility If you use a USB camera, confirm that it is a UVC camera or a USB webcam detected by N6, then select the correct USB source in the web interface.

NDI discovery Confirm that the N6 source is visible on the same network before adding SRT.

Resolution first test Start with 720p30 or 1080p30 before 1080p60.

Bridge workflow: NDI to SRT to Callaba

Use this path when the source starts as HDMI or USB camera, N6 turns it into NDI, and the production needs that source inside a Callaba SRT workflow.

Callaba receives SRT from the bridge, not the local NDI source directly in this SRT Gateway workflow.

A typical Callaba SRT listener URL for the bridge output can look like this:

srt://YOUR_CALLABA_IP:10210?mode=caller&latency=200&streamid=kiloview-n6-bridge-main

Use this as a field-format example only. The bridge, not the N6 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 N6 is already part of your local NDI network. One Callaba Engine instance can run near the NDI device and see the N6 source. Another Callaba Gateway instance in the cloud can receive SRT.

Connect the HDMI or USB source to N6 and confirm the N6 NDI source is visible on the local network.
Open the local Callaba Engine instance and check the NDI discovered devices area.
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 suggested by your Callaba installation; in this article the example bridge URL uses 10210. Save the server, copy the generated SRT Publisher URL, and open the selected UDP port in your cloud firewall or security group.
On the local Callaba Engine, open Restreams, click Add New, set Input Type to NDI Device, and select the N6 source.
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.

FFmpeg warning: standard FFmpeg builds usually do not include NDI input support. This command needs a special FFmpeg build compiled with NDI SDK support. For a quick lab test, OBS with an NDI source plugin is usually easier.

ffmpeg -f libndi_newtek -i "N6 Camera 1" \
  -c:v libx264 -preset veryfast -b:v 4500k \
  -c:a aac -b:a 128k -f mpegts \
  "srt://YOUR_CALLABA_IP:10210?mode=caller&latency=200&streamid=kiloview-n6-bridge-main"

N6 vs N5/N60 for SRT workflows

Many people searching for “Kiloview N6 SRT” are really trying to decide whether N6 is the right hardware for Callaba Gateway. This table keeps the decision simple.

Use N6 for HDMI/USB to NDI. Use N60 when the HDMI hardware itself must handle SRT directly.

Model	Direct SRT path	Main role	Recommendation
N6	Use bridge	HDMI/USB → NDI	Use for 1080p HDMI or USB camera NDI workflows.
N5	Use bridge	3G-SDI/USB → NDI	Use when the input is SDI but you still want NDI.
N60	Yes	4K HDMI all-protocol	Use when HDMI hardware must send SRT directly.

Device choice rule: if you need direct SRT from HDMI without a bridge, choose N60. Choose N6 when the core workflow is HDMI/USB → NDI, or when you already own N6 and can add a bridge.

Settings table

This table helps keep the NDI side and SRT side separate.

N6 settings are NDI-side. Callaba settings become relevant after a bridge or SRT-capable device exists.

N6 multiview workflow with Callaba

N6 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.

N6 recorder workflow: NDI source vs Callaba cloud recording

The N6 side and the Callaba side protect different points in the workflow. N6 handles the HDMI/USB ↔ NDI conversion. Callaba records what actually arrived after the NDI-to-SRT bridge or another ingest path.

N6 playback workflow with Callaba

Playback also has two meanings. N6 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-n6-bridge-main/playlist.m3u8

Player or embed page:
https://YOUR_CALLABA_DOMAIN/embed/kiloview-n6-bridge-main

Where 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.

Troubleshooting

Most issues come from mixing up NDI and SRT responsibilities. Check the HDMI/USB and 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 N6 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 N6 is in the correct encoding or decoding mode.
Check HDMI or USB source selection, NDI mode, NDI discovery and network segment.
For USB cameras, confirm UVC/webcam compatibility, check that the camera is not locked by another application, reconnect it, and reboot N6 after changing the USB source.
If N6 is not visible in the NDI source list, check NDI Access Manager, local firewall rules and whether NDI discovery is blocked across subnets.

3. Connected, but no picture in Callaba

Check the NDI-to-SRT bridge output codec.
Start with H.264 and 720p30 or 1080p30 before testing 1080p60.
Check audio mapping after the bridge, not only on the HDMI, USB or NDI side.

Official and technical references used for this guide

Use these if you need exact N6 device role, HDMI/USB limits, NDI behavior, SRT background or bridge details before configuring a production workflow.

FAQ

Can Kiloview N6 send SRT directly to Callaba Gateway?

In the standard NDI workflow, Kiloview N6 does not provide native SRT push/server settings. Treat it as an HDMI/USB to NDI converter, not as a direct SRT encoder. 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 N6 NDI to Callaba SRT?

Use a Callaba Engine instance, OBS/FFmpeg test bridge, or another NDI-to-SRT bridge. The bridge receives the N6 NDI source and sends SRT to a Callaba Gateway listener.

Can I use N6 with Callaba multiview?

Yes, after the N6 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 N6 or N60 for direct SRT?

Use N6 when the job is HDMI/USB to 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 N6 into the wrong role. Use N6 for HDMI / USB → NDI. 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 19, 2026

Try Callaba Gateway with your NDI-to-SRT workflow

Create an SRT listener in Callaba, send your bridged N6 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 for direct SRT