media server logo
PricingAPI docsLaunch SRT server

Kiloview N50 SRT setup: 12G-SDI 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 N50 is a 12G-SDI bi-directional converter for professional IP video workflows.

The practical Callaba path has two directions: use N50 in encoding mode to send a 12G-SDI source to Callaba Gateway over SRT, or use N50 in decoding mode to turn a Callaba-managed SRT route back into local SDI output.

This guide is written for the search intent behind Kiloview N50 SRT, Kiloview N50 encoder, Kiloview N50 decoder, Kiloview N50 12G-SDI, Kiloview N50 multiview, Kiloview N50 recorder, Kiloview N50 playback, Kiloview N50 NDI and Callaba SRT Gateway.

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

For ingest, create an SRT server in Callaba Gateway in Listener mode, open the selected UDP port, then configure Kiloview N50 in encoding mode to send SRT to the Callaba public IP or DNS name. For SDI playback, create or select a Callaba SRT output route, then configure N50 in decoding mode to receive that SRT stream and output it over 12G-SDI.

Kiloview N50 to Callaba Gateway using SRT Infographic showing Kiloview N50 12G-SDI bidirectional converter sending SRT to Callaba Gateway for multiview, recording and playback, or decoding a Callaba SRT route back to SDI output. Kiloview N50 ↔ Callaba Gateway 12G-SDI SRT encode/decode workflow for cloud production Kiloview N50 12G-SDI · 4Kp60 · H.264/H.265 Encode to SRT Decode from SRT Callaba Gateway ingest, route, record, play SRT ingest SRT decode Recorder Multiview
N50 can sit on either side of the Callaba workflow: SDI to cloud, or cloud back to SDI.

What this setup does

This workflow connects a 12G-SDI source or destination to Callaba Gateway through Kiloview N50. In encoding mode, N50 sends the SDI feed to Callaba over SRT. In decoding mode, N50 receives a Callaba-managed SRT stream and outputs SDI locally.

  • N50 as encoder: 12G-SDI source into Callaba for monitoring, recording, playback and routing.
  • N50 as decoder: Callaba SRT route back to local 12G-SDI output.
  • Callaba Gateway: receives, monitors, records, routes and prepares the live stream for downstream workflows.

N50 encoder vs decoder roles

The most important choice is not only the protocol. It is the role. Are you bringing SDI into Callaba, or are you taking a Callaba stream back out to SDI?

Kiloview N50 role map for Callaba workflows Infographic showing Kiloview N50 as a 12G-SDI encoder sending SRT to Callaba and as a 12G-SDI decoder receiving an SRT route from Callaba. N50 has two practical Callaba roles Use encoding mode for cloud ingest. Use decoding mode for local SDI output from a cloud route. N50 as encoder 12G-SDI input → SRT stream Send to Callaba for multiview, recording, playback and routing. SDI → cloud N50 as decoder Callaba SRT route → 12G-SDI output Use for monitors, projectors, switchers or local SDI handoff. cloud → SDI
Keep encoding and decoding workflows separate during setup. This avoids mixing up source direction, SRT roles and SDI ports.
N50 role Callaba angle First test recommendation
Encoding mode 12G-SDI contribution into Callaba Gateway over SRT. Start with 1080p30 H.264 before 4Kp60, 10-bit, HDR or H.265.
Decoding mode Callaba-managed SRT route to local 12G-SDI output. Start with one known SRT source and one local SDI monitor.

Before you start

Prepare the SRT connection before changing production settings. N50 is a high-quality 12G-SDI device, so the temptation is to start with the highest format. Do not do that for the first network test.

Before you start: confirm the exact N50 firmware and whether you are testing encoding mode or decoding mode. A successful SRT socket is not enough. You still need to verify SDI signal, codec, color format, bitrate, audio and downstream behavior.

Workflow role Decide first: N50 as encoder into Callaba, or N50 as decoder from Callaba.
Callaba 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 4Kp60. This helps isolate codec, SDI or network issues.
Codec first test Start with H.264. Move to H.265, 10-bit, 4:2:2 or HDR after the path is stable.
Bitrate Keep bitrate below real uplink capacity. 12G-SDI source quality does not remove network limits.
Audio Confirm SDI embedded audio or configured audio input and check that Callaba detects audio after ingest.

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 10170.
  5. Set latency, for example 200 ms as a starting point.
  6. Add a stream ID if your routing model uses it.
  7. Open the UDP port in your cloud firewall or security group.

Step 2: configure N50 as SRT encoder

Use this path when the source is local 12G-SDI and Callaba should receive it in the cloud.

N50 encoding mode: 12G-SDI to Callaba N50 sends the SDI source. Callaba receives it and runs the cloud workflow. N50 encoding mode: 12G-SDI to Callaba N50 sends the SDI source. Callaba receives it and runs the cloud workflow. 12G-SDI source format, audio, timing N50 encoder SRT + H.264/H.265 Callaba Gateway monitor, record, route SRT 12G-SDI record / playback
N50 encoding mode sends the SDI source to Callaba, where it becomes available for monitoring, recording, playback and routing.
  1. Confirm the 12G-SDI input is locked and visible in N50.
  2. Choose a conservative H.264 profile for the first SRT test. Start with Main or Baseline. Avoid High profile for the first test if preview issues appear.
  3. Add or enable an SRT output stream.
  4. Set N50 to Caller for the first cloud ingest test.
  5. Enter the Callaba public IP address or DNS name as the destination.
  6. Enter the same UDP port that Callaba is listening on.
  7. Start the stream and watch for connection state in Callaba.

Step 3: configure N50 as SRT decoder

Use this path when Callaba already manages the live stream and you need a local SDI output.

N50 decoding mode: Callaba route to SDI output Callaba manages the cloud stream. N50 restores it as local 12G-SDI output. N50 decoding mode: Callaba route to SDI output Callaba manages the cloud stream. N50 restores it as local 12G-SDI output. Callaba route format, audio, timing N50 decoder SRT + H.264/H.265 12G-SDI output monitor, record, route SRT 12G-SDI record / playback
N50 decoding mode is useful when a Callaba-managed source needs to return to a local SDI monitor, projector, router or switcher.

Caller / Listener example: if N50 pulls the stream from Callaba, use a caller-style URL such as srt://YOUR_CALLABA_IP:10170?mode=caller. If Callaba pushes the stream to N50, set Callaba as caller and N50 as listener, then make sure the N50 listener address and UDP port are reachable.

  1. Switch N50 to decoding mode.
  2. Create or select the SRT output route in Callaba.
  3. Choose whether N50 pulls from Callaba or receives a push from Callaba.
  4. Enter the matching URL, port, stream ID and passphrase if used.
  5. Connect the SDI output to a monitor, router, switcher or projector.
  6. Verify picture, audio, format and stability locally.

Settings table

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

Kiloview N50 and Callaba SRT settings table Infographic listing SRT settings to align between Kiloview N50 and Callaba Gateway: role, mode, address, UDP port, stream ID, passphrase, resolution, bitrate, codec and audio. SRT settings to check before going live Match transport first. Then verify SDI, codec, resolution, bitrate and audio. FieldCallaba GatewayKiloview N50Why Roleinput or output routeencoder or decoderdirection ModeListener for ingestCaller for ingesthandshake Addresspublic IP / DNStarget or source URLconnection UDP portopen listener portsame target portfirewall Stream IDexpected IDsame value if usedrouting Passphrasesame passphrasesame key if usedencryption Resolution/FPSmatches sourcestart 1080p30debugging Bitrateingest capacitybelow uplinkstability CodecH.264 / H.265start H.264compatibility Audiodetected audioSDI or analogmonitoring
Match role, mode, address, port, stream ID and passphrase first. Then verify SDI format, codec, bitrate and audio.
Setting Callaba Gateway Kiloview N50 Why it matters
Role SRT input or SRT output route Encoding mode or decoding mode This controls the direction of the workflow.
Mode Listener for ingest Caller for ingest One side waits, the other side connects.
UDP port Open listener 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.
Passphrase Same passphrase if encryption is used Same key if encryption is used Required for encrypted SRT sessions.
Resolution / FPS Must match what N50 sends or receives Start with 1080p30 Easier to isolate before 4Kp60.
Codec / audio H.264/H.265 and detected audio Start H.264 and confirm SDI/analog audio Media compatibility matters after SRT connects.

N50 multiview workflow with Callaba

N50 does not need to be your multiview system. It can be the 12G-SDI contribution or return device. 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 source can look after cloud ingest. You can also read more about browser multiview.

N50 recorder workflow: device-side recording vs cloud recording

N50 workflows can include device-side recording to USB storage or NAS, 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
N50 USB / NAS recording The device-side or source-side workflow before cloud transport. Use it when the local team needs an on-site copy or a source-side backup.
Callaba cloud recording The received workflow side, after SRT reaches Callaba. Use it when you need proof of what actually arrived at the gateway and what downstream systems received.

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

N50 playback workflow with Callaba

Playback has two meanings in this workflow. Browser playback means Callaba creates a web player, HLS output or review link after ingest. Hardware playback means Callaba routes SRT back to N50, and N50 outputs SDI locally.

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

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

Where the links come from: Callaba generates these links after you create a web player or HLS packaging path for the incoming N50 stream. Depending on your configuration, player or HLS links may include temporary tokens, for example ?token=....

Troubleshooting

Most N50 to Callaba SRT issues come from role confusion, SDI signal, SRT mode, stream ID, passphrase, codec profile, audio source, bitrate, or route assignment. Check them in this order.

1. No connection in Callaba

  • Confirm N50 is in encoding mode if you are sending SDI into Callaba.
  • Confirm Callaba is listening on the expected UDP port.
  • Check receiver address, stream ID and passphrase if used.

2. Connected, but no picture

  • Confirm the SDI input has a valid video signal.
  • Start with H.264 before testing H.265, 10-bit, 4:2:2 or HDR workflows.
  • If preview fails, try H.264 Main or Baseline and restart the stream.

3. N50 does not output SDI in decoding mode

  • Confirm N50 is in decoding mode.
  • Confirm the Callaba SRT route is active and reachable.
  • Check whether N50 should pull from Callaba or receive a push from Callaba.
  • Check output resolution and the receiving monitor, router or switcher.

4. No audio after ingest

  • Verify that the selected SDI source actually carries embedded audio.
  • Check N50 audio input settings: embedded SDI audio, analog audio or USB audio, depending on the workflow.
  • Check Callaba stream metadata and browser preview before troubleshooting the player, recording or SDI output path.

Official references used for this guide

Use these if you need exact Kiloview N50 model details, protocol support, firmware notes, SRT behavior, recording support or encoding and decoding specs before configuring a production device.

FAQ

Can Kiloview N50 send SRT to Callaba Gateway?

Yes. In encoding mode, N50 can send a 12G-SDI source as an SRT stream to Callaba Gateway. For the simplest cloud ingest setup, Callaba listens and N50 connects as caller.

Can N50 decode a Callaba SRT route back to SDI?

Yes. In decoding mode, N50 can receive an SRT route and output SDI locally, provided the codec, resolution, audio and SRT role settings match the Callaba output route.

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 monitor Kiloview N50 in Callaba multiview?

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

Final practical rule

Make the first Kiloview N50 → Callaba SRT connection boring. One role, one SDI source or one SDI output, one SRT route, one UDP port and one Callaba listener. When that is stable, add H.265, 4Kp60, HDR, 10-bit, recording, multiview, NDI, playback or downstream SDI routing.

Last updated: May 16, 2026

Try Callaba Gateway with your Kiloview N50

Create an SRT listener in Callaba, send a 12G-SDI N50 stream to the gateway, and monitor the feed before routing it to recording, restreaming, multiview, playback, player delivery or SDI output workflows.

See SRT server setup Open multiview demo Explore N50 NDI workflows