Kiloview E3 SRT setup: HDMI and SDI encoder to Callaba Gateway

May 16, 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 E3 is a dual-channel 4K HDMI and 3G-SDI HEVC encoder for professional IP video workflows.

The practical Callaba path is simple: send SRT from E3 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 E3 SRT, Kiloview E3 encoder, Kiloview E3 HDMI SDI, Kiloview E3 multiview, Kiloview E3 recorder, Kiloview E3 playback, Kiloview E3 NDI and Callaba SRT Gateway.

Quick answer: how do I connect Kiloview E3 to Callaba Gateway?

Create an SRT server in Callaba Gateway in Listener mode, open the selected UDP port, then configure Kiloview E3 to send SRT in Caller or push mode to the Callaba public IP or DNS name. Enter the same UDP port, set latency, add stream ID and AES key only if needed, and start with a conservative H.264 1080p profile before testing H.265, 4K HDMI, dual-channel, PIP or PBP workflows.

The recommended first test is direct SRT from Kiloview E3 to a Callaba SRT listener.

What this setup does

This workflow sends a live stream from a Kiloview E3 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, converted to NDI workflows, or placed into a browser-based multiview board.

Kiloview E3 prepares HDMI, SDI, USB, PIP or PBP sources and sends the encoded stream.
Callaba Gateway listens on a public UDP port and accepts the incoming SRT stream.
Operators use Callaba to check preview, bitrate, codec, packet loss, recording, multiview, playback and route behavior.

E3 sends the production source. Callaba turns that source into a monitored and routable cloud workflow.

Why E3 is different from E1/E2

E1 and E2 are simpler source-specific encoders: SDI for E1, HDMI for E2. E3 is the more flexible workflow device. It can handle HDMI, SDI and USB input paths, and it can be useful when the production needs dual-source, mixed-source, PIP or PBP output before the stream reaches Callaba.

Choose the E3 input mode first. Then send the selected output into Callaba over SRT.

E3 mode	Best Callaba angle	First test recommendation
Single HDMI	HDMI camera, laptop, switcher or converter output to Callaba SRT ingest.	Start with 1080p30 H.264 before 4Kp30.
Single SDI	Broadcast camera or switcher SDI output to Callaba SRT ingest.	Start with 1080p30 or 1080p60 after network check.
PIP / PBP / dual-source	Combine or manage HDMI and SDI sources before sending one production feed to Callaba.	Validate each source alone first, then test the mixed output.

Recommended SRT mode: Callaba Listener, E3 Caller

For most cloud ingest workflows, the cleanest model is:

Callaba Gateway: Listener
Kiloview E3: Caller or SRT push to the Callaba IP and port

This keeps the public listening port on the Callaba side. The encoder only needs outbound UDP access to Callaba, which is usually easier than exposing the encoder to inbound internet traffic.

Caller, Listener and Rendezvous note:

E3 SRT settings can expose Caller, Listener and Rendezvous. For Callaba cloud ingest, start with E3 as Caller and Callaba as Listener. Use Rendezvous only when both sides and the network path are intentionally designed for that mode. Depending on firmware, the destination field can be called Receiver Address, Push URL or Server URL. The meaning is the same: enter the Callaba public IP address or DNS name.

A template SRT URL looks like this:

srt://YOUR_CALLABA_IP:10150?mode=caller&latency=200&streamid=kiloview-e3-main

A filled example for field testing can look like this:

srt://demo.callaba.io:10150?mode=caller&latency=200&streamid=kiloview-e3-main

Use the second example as a template. Replace host, port, stream ID and passphrase with your own Callaba values. In the Kiloview UI, you may enter these as separate fields instead of one full URL.

Before you start

Prepare the SRT connection before changing production settings. E3 has more options than a simple single-input encoder, so keep the first test narrow: one selected source, one encoded output, one SRT destination, one Callaba listener.

Before you start: confirm the exact E3 firmware and stream mode. Menu labels and available fields can differ, but the values to check are the same: handshake mode, receiver address, port, latency, stream ID, AES key, source input, codec, bitrate and audio.

Selected input Decide whether the source is HDMI, SDI, USB, PIP, PBP or dual-source before testing SRT.

PIP/PBP source sync For dual-source modes, ensure both sources have matching resolution and frame rate. Mismatched formats may cause flickering or missing video in the mixed output.

Callaba public address Use the public IP address or DNS name of the Callaba instance that will receive the SRT stream.

Resolution first test Start with 1080p30, not 4K. This reduces bitrate pressure and helps isolate codec, HDMI handshake or network issues.

Codec first test Start with H.264. Move to H.265 after Callaba preview, recording and playback are stable.

Bitrate Keep bitrate below the real uplink capacity. Leave extra room if the same encoder is sending multiple streams.

Audio Confirm embedded audio exists on the selected HDMI or SDI source and that Callaba detects it after ingest.

Step 1: create the SRT listener in Callaba

In Callaba, create a new incoming SRT server for the Kiloview E3 feed. Callaba opens a UDP port and waits for E3 to connect or push the stream.

Open your Callaba environment.
Create a new SRT input or SRT server.
Set the role to Listener if the UI exposes this option.
Choose a UDP port, for example 10150.
Set latency, for example 200 ms as a starting point.
Add a stream ID if your routing model uses it.
Add the same AES key or passphrase that you plan to use on E3, if encryption is needed.
Open the UDP port in your cloud firewall or security group.

Step 2: configure Kiloview E3 SRT output

In the Kiloview E3 web interface, select the source mode and add an SRT stream. The exact path can differ by firmware, but the E3 user manual describes adding an SRT stream in the streaming service, then filling in the stream ID and port. The SRT settings can expose Caller, Listener, Rendezvous, latency, AES encryption mode, SRT streaming ID and AES key.

Confirm the HDMI, SDI or USB input is locked and visible in the E3 preview.
Choose the source mode: single input, dual-source, PIP or PBP.
Choose a conservative H.264 profile for the first test.
Add or enable an SRT stream service.
Set handshake mode to Caller for the first cloud ingest test.
Enter the Callaba public IP address or DNS name as the receiving address.
Enter the same UDP port that Callaba is listening on.
Set latency, stream ID and AES key if your Callaba listener expects them.
Start the stream and watch for connection state in Callaba.

For the first test, do not enable every output at once. Start with one SRT output to one Callaba listener. After that works, add NDI, HLS, extra platforms, local recording, PIP/PBP or downstream routes.

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.

Match SRT transport settings first. Then verify source, resolution, bitrate, codec, audio and workflow outputs.

Bandwidth note: if E3 is also sending other streams, do not size the network only for the Callaba SRT output. Leave headroom for all active outputs and SRT recovery traffic.

Setting	Callaba Gateway	Kiloview E3	Why it matters
Mode	Listener	Caller or push mode	One side waits, the other side connects.
Address	Public IP or DNS	Receiver Address / Push URL / Server URL	The encoder must send to the reachable Callaba address.
Port	Open UDP port	Same target port	A wrong or blocked port looks like no connection.
Stream ID	Expected stream ID if used	Same value if used	Useful when several streams share routing logic.
AES key	Same passphrase if encryption is enabled	Same key, commonly 10–32 letters or numbers	Encryption fails if the two sides do not match exactly.
Resolution / FPS	Must match what E3 sends	Start with 1080p30 or known source format	Sync and bandwidth issues are easier to isolate before moving to 4K.
Codec	H.264 or H.265 received by Callaba	Start with H.264, then test H.265	H.264 is the safer first compatibility test.
Audio	Detected audio format and channels	Embedded HDMI or SDI audio	Audio must be present before recording, playback or monitoring is trusted.

Kiloview E3 multiview workflow with Callaba

E3 does not need to be your multiview system. It can prepare the source or mixed source. 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.

This is useful when the production team wants to see E3 sources in the browser before deciding what to route, record or deliver.

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 E3 feed would appear as a live input in your own deployment.

Kiloview E3 recorder workflow: device-side recording vs cloud recording

E3 workflows can include recording while streaming, including USB or NAS style workflows depending on 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
E3 local / NAS recording	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.

For critical workflows, the safest setup is parallel recording: keep a device-side copy when available and record the received SRT stream in Callaba.

Kiloview E3 playback workflow with Callaba

E3 is the encoder side of the workflow, not the local playback 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:

HLS playlist:
https://YOUR_CALLABA_DOMAIN/hls/kiloview-e3-main/playlist.m3u8

Player or embed page:
https://YOUR_CALLABA_DOMAIN/embed/kiloview-e3-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 E3 stream. The exact URL depends on your domain, routing and player configuration. Depending on your Callaba access settings, player or HLS links may include temporary tokens or other authorization parameters, so use the links generated by your own installation instead of copying the examples literally.

Troubleshooting

Most E3 to Callaba SRT issues come from selected input, source mode, SRT role, codec profile, audio source, bitrate, encryption or route assignment. Check them in this order.

Start with the selected input and source mode. Then check SRT role, network, codec and Callaba preview.

1. No connection in Callaba

Confirm Callaba is listening on the expected UDP port.
Confirm E3 is using Caller or push mode for the first test.
Check the receiver address and target port in the E3 settings.
Check stream ID and AES key if either one is enabled.
Check that the local network allows outbound UDP to Callaba.

2. Connected, but no picture

Confirm the HDMI, SDI or USB input has a valid video signal.
Check whether E3 is encoding the correct source: HDMI, SDI, USB, PIP or PBP.
If using PIP, PBP or dual-source mode, confirm that both input signals are active and that the correct source is assigned to each position in the mixed layout.
Check codec, profile, resolution, frame rate and audio settings in Callaba.
Start with H.264 before testing H.265 or 4K workflows.
If the stream connects but 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 4K or multi-output workflows.
Check network bandwidth, latency and packet loss.
Stop unused stream services during the first test.
Watch packet loss and reconnect behavior in Callaba.

4. No audio after ingest

Verify that the selected HDMI or SDI source actually carries audio.
Check the audio encoding settings on E3.
Check Callaba stream metadata and browser preview before troubleshooting the player or recording path.
If using PIP, PBP or dual-source mode, confirm which source is feeding audio.

5. Recording or playback does not work after ingest

Confirm the SRT input is connected and visible in Callaba.
Check that the correct input is assigned to recording, player or route.
Check codec and audio compatibility with the downstream path.
Use one clean route before adding several destinations.

Official references used for this guide

Use these if you need exact Kiloview model details, protocol support, firmware behavior, SRT mode notes, encryption settings or recording support before configuring a production device.

FAQ

Can Kiloview E3 send SRT to Callaba Gateway?

Yes. E3 supports SRT streaming. In a simple cloud ingest setup, Callaba Gateway listens for the incoming SRT stream and E3 connects or pushes the stream to Callaba.

What is the main difference between E3 and E1/E2?

E1 is the compact SDI path and E2 is the compact HDMI path. E3 is more flexible: it supports HDMI, 3G-SDI and USB input paths, plus dual-source and mixed-source workflows such as PIP and PBP.

Should I use H.264 or H.265 first?

Use H.264 for the first compatibility test. After SRT connection, preview, audio and recording are stable, test H.265 or higher-quality profiles if your downstream workflow supports them.

Can I send a 4K HDMI source from E3 to Callaba?

Yes, E3 supports HDMI input up to 4Kp30. Make sure your source and HDMI cable support 4Kp30. E3 is not a 4Kp60 input workflow. For the first SRT test, start with 1080p30 to isolate network and codec issues, then move to 4K when the path is stable.

Can I monitor Kiloview E3 in Callaba multiview?

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

Can Callaba record a Kiloview E3 stream?

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

Should E3 be Caller, Listener or Rendezvous?

For most Callaba cloud ingest workflows, set Callaba as Listener and E3 as Caller. Use Listener or Rendezvous on E3 only when your network path and workflow intentionally require those modes.

Final practical rule

Make the first Kiloview E3 → Callaba SRT connection boring. One selected input, one encoded output, one SRT push or caller connection, one UDP port and one Callaba listener. When that is stable, add H.265, 4K, PIP/PBP, recording, multiview, NDI, HLS, extra platforms or downstream routes.

Last updated: May 16, 2026

Try Callaba Gateway with your Kiloview E3

Create an SRT listener in Callaba, send an E3 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