media server logo
PricingAPI docsLaunch SRT server

Kiloview E1/E2 SRT setup: SDI or HDMI encoder to Callaba Gateway

May 16, 2026
Iurii Pakholkov, founder of Callaba

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 E1 and E2 are compact H.264 hardware encoders for SDI and HDMI sources.

The practical Callaba path is simple: push SRT from E1 or E2 to Callaba Gateway, then use the received feed for browser multiview, cloud recording, playback, routing, NDI workflows or delivery.

This guide is written for the search intent behind Kiloview E1 SRT, Kiloview E2 SRT, Kiloview E1/E2 encoder, Kiloview E1/E2 multiview, Kiloview E1/E2 recorder, Kiloview E1/E2 playback, Kiloview E1/E2 NDI and Callaba SRT Gateway.

Quick answer: how do I connect Kiloview E1 or E2 to Callaba Gateway?

Create an SRT server in Callaba Gateway in Listener mode, open the selected UDP port, then configure the Kiloview E1 or E2 main stream with SRT-TS pushing. Enter the Callaba public IP or DNS name as the pushing address, use the same UDP port, set latency or bandwidth options if exposed, and start with a conservative H.264 profile before adding multiview, recording, playback or extra destinations.

Kiloview E1 and E2 to Callaba Gateway using SRT Infographic showing Kiloview E1 SDI and Kiloview E2 HDMI encoders sending H.264 SRT streams to Callaba Gateway for multiview, recording, playback and cloud routing workflows. Kiloview E1 / E2 → Callaba Gateway H.264 SRT ingest for SDI and HDMI production sources Kiloview E1 / E2 E1 SDI · E2 HDMI · H.264 SRT-TS push push address · port · latency · bandwidth Callaba Gateway cloud ingest and routing SRT ingest Multiview Recorder Playback
The recommended first test is direct SRT-TS pushing from Kiloview E1 or E2 to a Callaba SRT listener.

What this setup does

This workflow sends a live H.264 stream from a Kiloview E1 or E2 encoder to Callaba Gateway over SRT. Callaba receives the stream in the cloud, then the feed can be monitored, recorded, previewed, routed, restreamed, used in a web player, or placed into a browser-based multiview board.

  • Kiloview E1: SDI input path.
  • Kiloview E2: HDMI input path.
  • Callaba Gateway: public SRT listener, monitoring, recording, routing and playback layer.
Kiloview E1 and E2 SRT ingest workflow with Callaba Infographic showing an SDI or HDMI source connected to Kiloview E1 or E2, SRT pushed to Callaba Gateway, then used for browser multiview, cloud recording, playback and routing. E1 / E2 direct SRT workflow The encoder sends the source. Callaba receives it and runs the cloud workflow. SourceSDI or HDMI E1 / E2H.264 encoderSRT-TS push CallabaSRT gatewaylistener Multiview Recorder Playback Routing
E1/E2 sends the venue or camera source. Callaba turns that source into a monitored and routable cloud workflow.

Kiloview E1 vs E2 workflow notes

The setup logic is almost the same for E1 and E2. The main difference is the physical source connector. Use E1 when your source is SDI. Use E2 when your source is HDMI.

Kiloview E1 and E2 model map for Callaba SRT workflows Infographic comparing Kiloview E1 and Kiloview E2 for Callaba Gateway: E1 is the SDI input path, E2 is the HDMI input path, and both can send H.264 SRT streams to Callaba. Choose E1 or E2 by source connector The SRT logic is similar. The physical video input is the main difference. Kiloview E1 SDI input and SDI loop output H.264 IP stream output SRT, NDI|HX, RTMP, HLS, TS-UDP SDI source Kiloview E2 HDMI input and HDMI loop output H.264 IP stream output SRT, NDI|HX, RTMP, HLS, TS-UDP HDMI source
The Callaba side stays the same: receive SRT, monitor it, record it, play it back or route it.
Device Best Callaba angle Source path
Kiloview E1 SDI camera or switcher output to Callaba SRT ingest. SDI input / loop output
Kiloview E2 HDMI camera, laptop, small switcher or converter output to Callaba SRT ingest. HDMI input / loop output

Before you start

Prepare the SRT connection before changing production settings. For older compact encoders, keep the first test simple: one source, one main stream, one SRT destination, one Callaba listener.

Before you start: confirm the exact E1/E2 firmware and whether your device is the NDI model. Depending on firmware, the menu item can be called SRT-TS pushing, SRT stream or SRT caller. If the label is different, look for the SRT service that lets you enter a destination IP address and port.

Callaba public address Use the public IP address or DNS name of the Callaba instance that will receive the SRT stream.
UDP port Choose one UDP port for this input and make sure it is open in the cloud firewall.
Resolution first test Start with 1080p30 if possible. This reduces bitrate pressure before testing 1080p60.
Main stream Use the main stream for the first test. Add sub stream or extra services only after the first feed is stable.

Setup steps

Step 1: create the SRT listener in Callaba

  1. Open your Callaba environment.
  2. Create a new SRT input or SRT server.
  3. Set the role to Listener if the UI exposes this option.
  4. Choose a UDP port, for example 10140.
  5. Set latency, stream ID and passphrase if your workflow uses them.
  6. Open the UDP port in your cloud firewall or security group.

Step 2: configure Kiloview E1/E2 SRT-TS pushing

In the Kiloview web interface, configure the main H.264 stream and add SRT-TS pushing as a stream service. The usual path is Encoding & Stream → Encoding and Stream Settings → H.264 main stream → Add a stream → SRT-TS pushing.

  1. Confirm the SDI or HDMI input is locked and visible in the device preview.
  2. Use a conservative H.264 profile for the first test.
  3. Add SRT-TS pushing as a stream service.
  4. Enter the Callaba public IP address or DNS name as the pushing address.
  5. Enter the same destination UDP port that Callaba is listening on.
  6. Start the stream and watch for connection state in Callaba.

Settings table

This table is the fastest way to avoid mismatches. The words in the Kiloview interface can differ, but the values must describe the same SRT connection.

Kiloview E1 E2 and Callaba SRT settings including resolution, bitrate and audio Infographic listing SRT settings to align between Kiloview E1 or E2 and Callaba Gateway: role, push address, UDP port, latency, bandwidth, stream ID, resolution and frame rate, codec and audio. SRT settings to check before going live Match the transport first. Then verify source, resolution, bitrate and audio. FieldCallaba GatewayKiloview E1 / E2Why ModeListenerSRT-TS pushhandshake Addresspublic IP / DNSpushing addresstarget UDP portopen listener portsame target portfirewall Resolution/FPSmatches received sourcestart 1080p30debugging Bitrateingest capacitybelow uplinkstability Bandwidthnetwork headroomSRT max bandwidthoverhead CodecH.264 inputH.264 profilecompatibility Audiodetected audioembedded audiomonitoring
Match SRT transport settings first. Then verify source, resolution, bitrate, audio and workflow outputs.
Setting Callaba Gateway Kiloview E1/E2 Why it matters
Mode Listener SRT-TS pushing One side waits, the other side pushes.
Address Public IP or DNS Pushing address The encoder must send to the reachable Callaba address.
Resolution / FPS Accepts source resolution and frame rate Start with 1080p30 or known source format Sync and bandwidth issues are easier to isolate before moving to 1080p60.
Codec H.264 received by Callaba H.264 profile selected on E1/E2 Keep downstream compatibility simple during the first test.
Audio Detected audio format and channels Embedded source audio Audio must be present before recording, playback or monitoring is trusted.

Kiloview E1/E2 multiview workflow with Callaba

E1/E2 does not need to be your multiview system. It can be the source encoder. After Callaba receives the SRT stream, the feed can be placed on a browser-based multiview board with other cameras, backup paths, remote sources or player outputs.

Interactive check: open the Callaba multiview demo to see how a received field source can look after cloud ingest. You can also read more about browser multiview. Your real E1/E2 feed would appear as a live input in your own deployment.

Kiloview E1/E2 recorder workflow: device-side options vs cloud recording

Some E-series workflows include local recording or NAS storage, depending on model, firmware and configuration. Callaba adds a different layer: cloud-side recording after SRT ingest. These two recordings protect different points in the chain.

Recording layer What it protects When to use it
Device-side recording / NAS The source side, before or near transport. Use it when the operator wants a local or network-storage copy.
Callaba cloud recording The received workflow side, after SRT reaches Callaba. Use it when you need proof of what actually arrived at the gateway.

Kiloview E1/E2 playback workflow with Callaba

E1/E2 is the encoder side of the workflow, not the local decoder. Playback happens after Callaba receives the stream. That playback can be browser preview, a generated player page, an HLS output, a recording review link or a downstream route to another system.

Typical generated playback links can look like this:

Install steps 
HLS playlist:
https://YOUR_CALLABA_DOMAIN/hls/kiloview-e1-main/playlist.m3u8

Player or embed page:
https://YOUR_CALLABA_DOMAIN/embed/kiloview-e1-main

Use these as URL shape examples only. In production, use the exact player link, HLS playlist URL or output route generated by your Callaba deployment.

Where the links come from: Callaba generates these links after you create a web player or HLS packaging path for the incoming E1/E2 stream. The exact URL depends on your domain, routing and player configuration.

Troubleshooting

Most E1/E2 to Callaba SRT issues fall into a small number of buckets. Check them in this order.

Kiloview E1 E2 to Callaba SRT troubleshooting path Troubleshooting path for Kiloview E1 and E2 SRT to Callaba Gateway: check input signal, main stream, SRT-TS pushing, push address, UDP port, bitrate, codec, audio and Callaba preview. Debug E1 / E2 SRT in this order First prove the input. Then prove SRT push. Then prove the cloud workflow. 1. InputSDI or HDMI lock2. Main streamH.264 enabled3. SRT serviceSRT-TS pushing4. PortUDP5. Networkbandwidth / loss6. Mediacodec, bitrate, audio7. Callabapreview / record / route
Start with the input signal and main stream. Then check SRT push, network, bitrate and Callaba preview.

1. No connection in Callaba

  • Confirm Callaba is listening on the expected UDP port.
  • Confirm SRT-TS pushing is added to the correct main stream.
  • Check the pushing address and target port in the Kiloview settings.
  • Check that the UDP port is open in the cloud firewall.

2. Connected, but no picture

  • Confirm the SDI or HDMI input has a valid video signal.
  • Check the device preview before troubleshooting Callaba.
  • Confirm you are using the right main stream and not an inactive sub stream.
  • Check codec, profile, resolution, frame rate and audio settings in Callaba.
  • If the stream connects but the preview fails, try switching H.264 profile to Main or Baseline, then restart the stream.

3. Stream drops or stutters

  • Lower bitrate and test again.
  • Start with 1080p30 before testing 1080p60.
  • Check network bandwidth, latency and packet loss.
  • Stop unused stream services during the first test.

Official references used for this guide

Use these if you need exact Kiloview model details, protocol support, firmware behavior, SRT-TS pushing steps or recording support before configuring a production device.

FAQ

Can Kiloview E1 or E2 send SRT to Callaba Gateway?

Yes. E1/E2 supports SRT streaming. In a simple cloud ingest setup, Callaba Gateway listens for the incoming SRT stream and the Kiloview encoder uses SRT-TS pushing toward Callaba.

What is the difference between Kiloview E1 and E2?

Use E1 for SDI sources and E2 for HDMI sources. The SRT setup thinking is similar: create a Callaba listener and push the encoder stream to that IP and port.

Should I use SRT-TS or another SRT service on E1/E2?

Start with SRT-TS pushing because it is the common E-series path in Kiloview documentation. If your firmware uses a different label, choose the SRT service that lets you enter a destination IP address and UDP port, then confirm in Callaba what payload, codec and audio are received.

Can I monitor Kiloview E1/E2 in Callaba multiview?

Yes. After Callaba receives the SRT stream, you can place the E1/E2 feed on a browser-based multiview board with other live sources.

Can Callaba record a Kiloview E1/E2 stream?

Yes. Callaba can record the received SRT stream in the cloud. This records what reached the gateway, which is different from device-side or NAS recording.

Should I test 1080p60 first?

No. Start with 1080p30 or a lower bitrate profile for the first SRT test, then move to 1080p60 after connection, preview, audio and recording are stable.

Final practical rule

Make the first Kiloview E1/E2 → Callaba SRT connection boring. One input, one main H.264 stream, one SRT-TS push, one UDP port and one Callaba listener. When that is stable, add multiview, recording, playback, NDI, HLS, extra pushes or downstream routes.

Last updated: May 16, 2026

Try Callaba Gateway with your Kiloview E1 or E2

Create an SRT listener in Callaba, send an E1 or E2 stream to the gateway, and monitor the feed before routing it to recording, restreaming, multiview, playback, player delivery or NDI-based production workflows.

See SRT server setup Open multiview demo Explore NDI workflows