media server logo
PricingAPI docsLaunch SRT server

Kiloview N60 SRT setup: 4K HDMI encode/decode with 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 N60 is a 4K HDMI bi-directional encoder/decoder for IP video workflows.

With Callaba, N60 can work in two directions: send a 4K HDMI source to Callaba over SRT, or decode a Callaba SRT output back to HDMI for a monitor, projector, switcher or return-feed setup.

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

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

For ingest, create an SRT server in Callaba Gateway in Listener mode, open the UDP port, then configure Kiloview N60 in encoding mode to send SRT to the Callaba public IP or DNS name. In encoding mode, N60 usually acts as the SRT caller. For playback, create or select an SRT output route in Callaba, then configure N60 in decoding mode to pull or receive that SRT source and output HDMI locally. In decoding mode, N60 can be caller when it pulls from Callaba, or listener when Callaba pushes to it. Check the exact labels in your firmware.

Kiloview N60 to Callaba Gateway using SRT Infographic showing Kiloview N60 as a 4K HDMI encoder and decoder connected to Callaba Gateway over SRT for multiview, recording, playback, NDI and cloud routing workflows. Kiloview N60 ↔ Callaba Gateway SRT ingest and playback for 4K HDMI IP workflows Kiloview N60 4K HDMI · encode · decode SRT ingest SRT playback Callaba Gateway SRT, NDI, record, route SRT ingest Multiview Recorder Playback
N60 can be a source encoder into Callaba or a local decoder from Callaba, depending on the workflow direction.

What this setup does

This workflow connects Kiloview N60 with Callaba Gateway over SRT. In encoding mode, N60 sends a 4K HDMI source into Callaba. In decoding mode, N60 can receive or pull an SRT stream from Callaba and output HDMI locally.

  • N60 as encoder: HDMI source to SRT, NDI, RTMP or another supported stream.
  • Callaba Gateway: SRT ingest, browser monitoring, recording, playback, routing and restreaming.
  • N60 as decoder: Callaba SRT route to local HDMI output.

N60 as encoder vs decoder

The most important decision is the direction of the stream. Many SRT setup mistakes happen because the device is treated only as an encoder, while the actual job is playback or return-feed decode.

Kiloview N60 encoder and decoder roles with Callaba Infographic explaining two Kiloview N60 roles with Callaba: encode HDMI to SRT into Callaba, or decode Callaba SRT output to HDMI for local playback. N60 has two useful Callaba roles Start by choosing whether N60 is the source encoder or the local playback decoder. Encoding mode 4K HDMI source enters N60. N60 sends SRT to Callaba. Callaba monitors, records, routes, plays back or converts the stream. N60 → Callaba Decoding mode Callaba exposes an SRT source. N60 pulls or receives the stream. N60 outputs HDMI to a monitor, projector, switcher or return display. Callaba → N60
Use encoding mode when N60 is the source. Use decoding mode when Callaba is the source and N60 is the local output.

N60 and N50 workflow notes

N60 and N50 belong to the same newer all-in-one converter family. The practical difference is the physical video interface: N60 is the 4K HDMI path, while N50 is the 12G-SDI path. This article focuses on N60 because the slug and search intent are about the HDMI model.

Device Best Callaba angle Physical video path
Kiloview N60 4K HDMI source to Callaba SRT ingest, or Callaba SRT output to local HDMI playback. 4K HDMI
Kiloview N50 Similar SRT logic, but better fit when the source or output is 12G-SDI. 12G-SDI

Before you start

Prepare the direction first. Decide whether N60 is sending a source into Callaba or receiving a source from Callaba. Then configure SRT roles, ports, codec and output settings around that direction.

Before you start: confirm the exact N60 firmware and stream mode. Firmware changes can affect SRT stream ID support, bitrate behavior, recording support and decoding stability.

Mode Choose encoding mode for HDMI to Callaba. Choose decoding mode for Callaba to HDMI.
Callaba address Use the public IP address or DNS name of the Callaba instance or output route.
UDP port Choose one UDP port for the SRT connection and make sure it is open where needed.
Resolution first test Start with 1080p30, not 4K. This reduces bitrate pressure and helps isolate codec or HDMI handshake issues before moving to 4K workflows.
Codec profile Start with H.264 for the first compatibility test. Move to H.265 after the path is stable.
Audio Confirm whether audio comes from HDMI or analog input and whether Callaba detects it correctly.
Output format For decoding, confirm HDMI output format and display compatibility before live use.

Step 1: create the SRT listener in Callaba

For an N60 ingest workflow, create a new incoming SRT server in Callaba. Callaba opens the UDP port and waits for N60 to connect or push the stream.

  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 10130.
  5. Set latency, for example 200 ms as a starting point.
  6. Add a stream ID if your routing model uses it.
  7. Add the same passphrase that you plan to use on N60, if encryption is needed.
  8. Open the UDP port in your cloud firewall or security group.

Step 2: configure Kiloview N60 SRT encoding

In the Kiloview N60 web interface, switch to or confirm encoding mode, select the HDMI input, and configure the SRT output toward Callaba.

  1. Confirm the HDMI input is locked and visible on N60.
  2. Open the encoding or stream settings.
  3. Choose a conservative codec profile for the first test.
  4. Add or enable an SRT stream service.
  5. Enter the Callaba public IP address or DNS name as the target.
  6. Enter the same destination UDP port that Callaba is listening on.
  7. Set latency, stream ID and passphrase if your Callaba listener expects them.
  8. Start the stream and watch for connection state in Callaba.
Kiloview N60 SRT ingest workflow with Callaba Infographic showing a 4K HDMI source connected to Kiloview N60, SRT sent to Callaba Gateway, and Callaba used for multiview, recording, playback and routing. N60 encoding mode: HDMI to SRT ingest N60 sends the HDMI source. Callaba receives it and runs the cloud workflow. Source 4K HDMI N60 encoder mode SRT / RTMP / NDI Callaba SRT gateway listener Multiview Recorder Playback Routing
In encoding mode, N60 is the 4K HDMI source encoder and Callaba is the cloud ingest point.

Optional: decode a Callaba SRT output on N60

N60 can also sit at the other end of the chain. If you need a local HDMI output from a Callaba-managed stream, create an SRT output route in Callaba and configure N60 in decoding mode to receive that stream.

Pull vs Push in N60 decoding mode:

In the N60 decoding settings, you may see labels such as Pull stream or Push stream. Pull means the device connects to the server, so N60 behaves like the caller and fetches the stream from Callaba. Push means the server sends to the device, so N60 behaves like the listener. For most cloud setups, Pull is simpler because the decoder only needs outbound access to Callaba.

  1. Select the source or program route in Callaba.
  2. Create an SRT output or expose the selected stream as an SRT endpoint.
  3. Open the N60 decoding mode or preset source settings.
  4. Add the Callaba SRT source URL.
  5. Set buffer or latency values for stable playback.
  6. Confirm HDMI output on a monitor before connecting to a switcher or projector.
Kiloview N60 SRT decoding and playback workflow with Callaba Infographic showing Callaba Gateway routing an SRT stream to Kiloview N60 in decoding mode, with HDMI output to a monitor, projector or switcher. N60 decoding mode: SRT playback from Callaba Use this when the local side needs HDMI output from a cloud-managed stream. Callaba SRT output route N60 decoder mode Monitor Switcher Projector HDMI local output
In decoding mode, Callaba is the SRT source and N60 is the local HDMI playback device.

Settings table

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

Kiloview N60 and Callaba SRT settings including resolution, codec and playback role Infographic listing SRT settings to align between Kiloview N60 and Callaba Gateway: role, address, UDP port, stream ID, resolution and frame rate, bitrate, codec and audio. SRT settings to check before going live Match role and transport first. Then verify resolution, media, audio and output. Field Callaba Gateway Kiloview N60 Why Rolelistener or outputencoder or decoderdirection Addresspublic IP / DNStarget or source URLconnection UDP portopen portsame portfirewall Stream IDexpected IDsame valuerouting Resolution/FPSaccepts source formatstart 1080p30bandwidth Bitrateingest capacitysource bitratestability CodecH.264 / H.265same profilecompatibility Audiodetected channelsHDMI or analogmonitoring
Match the SRT role and direction first. Then verify codec, audio, bitrate and output.
Setting Callaba Gateway Kiloview N60 Why it matters
Role Listener for ingest, source/output for decode Encoder mode or decoder mode The workflow direction decides all other SRT values.
Address Public IP or DNS Target address or source URL N60 must reach the correct Callaba endpoint.
Port Open UDP port Same port A wrong or blocked port looks like no connection.
Resolution / FPS Accepts source resolution and frame rate Start with 1080p30 or the known source format Sync and bandwidth issues are easier to isolate before moving to 4K.
Codec H.264 or H.265 received by Callaba Same codec/profile selected on N60 H.264 is the safer first test; H.265 is useful after compatibility is confirmed.
Audio Detected audio channels and format HDMI or analog audio source Audio must be present before recording, playback or monitoring is trusted.

Kiloview N60 multiview workflow with Callaba

N60 does not need to be the multiview surface. It can be the source encoder or local decoder. Callaba can receive the N60 SRT stream, show it in browser multiview, and route the same stream to recording, playback or an output route.

This is useful when a team needs cloud monitoring of N60 sources before deciding what should be recorded, delivered, or sent back to a local decoder.

Interactive check: open the Callaba multiview demo to see how a received source can look after cloud ingest. Your real N60 feed would appear as a live input in your own deployment.

Kiloview N60 recorder workflow: device-side storage vs cloud recording

N60/N50 workflows can include USB or NAS recording, depending on 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
N60 device-side recording The source side, before or near transport. Use it when the operator wants a local or device-side 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 N60 playback workflow with Callaba

Playback can mean browser preview in Callaba, a web player or HLS output for viewers, or physical HDMI output through N60 in decoding mode. Keep those paths separate.

For browser playback, use the player link or HLS URL generated by your own Callaba deployment. For local hardware playback, use an SRT output route from Callaba and decode it on N60.

Typical generated playback links can look like this:

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

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

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

Troubleshooting

Most N60 to Callaba issues come from mixing up direction, mode, SRT role, codec profile, audio source or output target. Check them in this order.

Kiloview N60 to Callaba SRT troubleshooting path Troubleshooting path for Kiloview N60 SRT workflows with Callaba Gateway: check mode, HDMI input, SRT role, destination URL, UDP port, codec, audio and Callaba preview or N60 HDMI output. Debug N60 SRT in this order First confirm mode. Then prove transport. Then prove media and output. 1. Mode encode or decode 2. Source HDMI or SRT URL 3. SRT role caller/listener 4. Port UDP 5. Media codec, profile, audio 6. Buffer latency / stability 7. Output preview or HDMI
Start with N60 mode and source direction. Then check SRT role, media settings and output.

1. No connection in Callaba

  • Confirm N60 is in encoding mode, not decoding mode.
  • Confirm Callaba is listening on the expected UDP port.
  • Check the destination address in N60.
  • Check caller/listener mode and stream ID.
  • Check that the local network allows outbound UDP to Callaba.

2. Connected, but no picture

  • Confirm the HDMI input is locked and visible on N60.
  • Check codec, profile, resolution, frame rate and audio in Callaba.
  • Start with H.264 before testing H.265 or 4K workflows.
  • Check whether the stream has audio; some firmware fixes mention SRT behavior when no HDMI audio input is present.

3. Decoder output is black

  • Confirm N60 is in decoding mode.
  • Confirm the Callaba SRT output route is active.
  • Check source URL, role, port, stream ID and passphrase.
  • Check HDMI output format and display compatibility.
  • Test with a direct monitor before going through a switcher or projector.

3b. No audio after ingest

  • Verify that the HDMI source actually carries audio.
  • Check whether N60 is set to HDMI audio or analog line input.
  • Try a known-good audio source or enable analog audio input temporarily.
  • Check Callaba stream metadata and preview before troubleshooting the player or recording path.

4. 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 or recording support before configuring a production device.

FAQ

Can Kiloview N60 send SRT to Callaba Gateway?

Yes. In encoding mode, N60 can send SRT from a 4K HDMI source to Callaba Gateway. Callaba should usually listen on a public UDP port while N60 connects or pushes the stream.

Can Kiloview N60 decode SRT from Callaba?

Yes. In decoding mode, N60 can receive an SRT source and output HDMI locally. This is useful for return feeds, monitor outputs, projector feeds or local hardware playback.

Should N60 be Caller or Listener when decoding from Callaba?

If N60 pulls the stream from Callaba, set N60 as Caller and Callaba as Listener. If Callaba pushes the stream to N60, reverse the roles and make sure the N60 listener is reachable from Callaba.

Should I test N60 in 4K first?

No. Start with 1080p30 for the first SRT test, then move to 4K after the stream connects, preview works, audio is present and recording or playback is stable.

Can I monitor Kiloview N60 in Callaba multiview?

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

Can Callaba record a Kiloview N60 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 I use H.264 or H.265 first?

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

Does this guide apply to Kiloview N50?

The SRT idea is similar, but N50 is the 12G-SDI model. Use the same Callaba thinking, but check N50-specific I/O, firmware and output settings.

Final practical rule

Decide the direction first. If N60 is sending HDMI to Callaba, configure it like an SRT encoder. If N60 is receiving from Callaba, configure it like an SRT decoder. Do not mix those two jobs in the same test.

Last updated: May 16, 2026

Try Callaba Gateway with your Kiloview N60

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