Skip to main content

Input Settings

The following table lists the Kraken Input settings.

General

Input Setting

Description/Values

Name*

Enter a unique name for the input. This name will be selectable from the list of Inputs when you define a stream.

Note

The Input name is not required. Kraken will use the Input URL as the name if none is provided.

Source* (Transcoding)

Select the Source for the Input:

  • TS over UDP: MPEG2 Transport Stream over UDP (no RTP header, default)

  • TS over SRT: Haivision's Secure Reliable Transport. See SRT (Secure Reliable Transport).

  • TS over TCP: Transmission Control Protocol (TCP) prioritizes accurate transmissions, and requires a handshake connection between the caller (sender) and listener (receiver).
    See the TCP Settings tab for configuration details. 

  • RTSP: (Real Time Streaming Protocol) Select to configure Kraken to interoperate with ISR "sensors" such as wearable IP cameras, which are typically H.264 RTP/RTSP. See NOTE: below.

    • You can specify transport options equivalent to ffplay command line arguments for RTSP input including  TCP, UDP Multicast and HTTP tunneling.

    • As of Release 4.0, you may configure Kraken to transmux RTSP input to TS/UDP or TS/SRT output using Bypass, Transcoder, and Transcoder+Passthru stream modes.

Note

Previous Kraken releases supported RTSP Input for H.264 video only under the following conditions:

  • Stream authentication through RTSP URL (username and password)

  • H.264 video instance selection through RTSP URL

  • Raw Motion JPEG: Allows you to input a Motion JPEG (MJPEG) live stream and transcode the payload into a standard H.264 or HEVC video within an MPEG Transport Stream.

  • MJPEG over HTTP: Allows connection to a remote server to pull JPEG content over an HTTP connection.

  • RTMP: (Real-Time Messaging Protocol)  Select to configure Kraken to input RTMP streams in Bypass, Transcoder, or Transcoder+Passthru modes. See Connecting an RTMP Input Source.

Source *(Encoding)

  • ST2110: Select to  capture and encode SDI input using an SFP (Small Form-factor Pluggable) SDI  to  IP gateway device on Kraken running as a VM on third party hardware.  Setup instructions to route data from the SFP device to Kraken are provided in the  Kraken OVA Deployment Guide . 

  • GigE Vision: Select to support the GigE Vision input (Kraken must be licensed for GigE Vision). 

Note

The GigE Vision standard specifies that only one client can control a GigE Vision device. Please ensure that other software applications are not controlling the GigE Vision device specified in the Kraken input.

  • NDI: Select to support Network Device Interface input (Kraken must be licensed for NDI input). 

  • SDI DeckLink Micro Recorder 1 (Kraken CR or SDI capture card must be installed): Select to capture HD/SD-SDI video for baseband input encoding.

  • Analog Capture 1 (Kraken CR or Analog Composite capture card must be installed): Select to capture Analog Composite Video for baseband input encoding.

URL*

(Source must be TS over UDP, RTSP, or RAW Motion JPEG) Type in the source URL for the Input, for example, udp://239.100.100.100:5000.

Examples of supported input formats:

Note

Kraken input streams may be UDP unicast or multicast, or TCP unicast.

Source Specific Multicast

(Source must be TS over UDP or Raw Motion JPEG) Type in a specific source device IP address.

Note

Kraken supports IGMPv3 Source Specific Multicast reception, which allows input streams to join a multicast group and filter the input streams based on a specific source IP address. Only streams originating from the specified source IP will be forwarded to Kraken. This allows Kraken to quickly and easily select an input stream in environments with many sources sharing a common multicast IP.

When the receiving device specifies a source device IP address, the IGMP protocol will filter out devices that use the same multicast group address and only forward the traffic with the specified source IP address as well the destination IP multicast address to the requesting destination device.

Network Interface*

(Source must be TS over UDP) Select the network (Ethernet) interface for the Input, either:

  • Auto (default): Uses static route, if defined; otherwise uses the default

  • LAN1

  • LAN2

  • ...

Note

Network Interface names for Ethernet interfaces may vary, such as LAN1/LAN2/..., eth0/eth1/…, pNp1/pNp2/…, or em1/em2/….

To configure customized names for the network interfaces, as shown in the following example, see "User Description" under  Network Settings.

Warning

Because input multicast listening routes are based on IP addresses, do not reuse the same address even if it is assigned to different NICs. Doing so would produce corrupted output in all associated sessions.

Transport

(Source must be RTSP) Select the transport mode for the Input, either: 

  • Auto (default): 

  • UDP

  • TCP

  • UDP Multicast

  • HTTP

Mode*

(Source must be RTMP) Select either Client or Server depending on the RTMP source. See Connecting an RTMP Input Source.

Port*

(Source must be RTMP and Mode set to Server) Type in the source port number for the Input.

IPv6

(Source must be RTMP and Mode set to Server) Check the checkbox to enable IPv6 addresses. 

SRT Settings

Input Setting

Description/Values

Mode*

Select the SRT Connection Mode:

  • Caller: Kraken acts like a client and connects to a server listening and waiting for an incoming call.

  • Listener (default): Kraken acts like a server and listens & waits for clients to connect to it.

  • Rendezvous: Allows calling and listening at the same time.

Note

To simplify firewall traversal, Rendezvous Mode allows Kraken and the encoder to traverse a firewall without the need for IT to open a port.

Address*

(Caller and Rendezvous Connection Modes) Type in the destination IP address for the SRT stream.

Tip

You can also enter a Fully Qualified Domain Name (FQDN).

Source Port

(Caller Connection Mode) Specifies the UDP source port for the SRT stream. If not filled in, a (default) source port will be assigned.

Note

This simplifies firewall configuration as the firewall/NAT rules can be precisely tailored to the SRT stream.

Destination Port*

(Caller and Rendezvous Connection Modes) Specifies the UDP destination port for the SRT stream.

Port*

(Listener Connection Mode only) Specifies the UDP local port for the SRT stream.

Latency*

Specifies how long Kraken will buffer received packets. The size of this buffer adds up to the total latency. A minimum value must be 3 times the round-trip-time (RTT).

Range = 20-8000 ms; Default = 125 ms

Latency is for the SRT protocol only and does not include the capture, encoding, decoding and display processes of the end-point devices.

Passphrase

(Optional, must match encoder passphrase) This parameter is required if the stream is encrypted and is used to retrieve the cryptographic key protecting the stream.

Range = 10-79 UTF-8 characters

Header Protection TBD

(Only available if Encryption is enabled) Enables Header Protection with Authenticated-Encryption with Associated-Data (AEAD). AEAD not only requires a key (passphrase) to decipher the encrypted stream, but also binds it to certain associated data. This associated data (composed of some non-confidential information about the stream) is integrity-protected, which allows users to determine if their streams have been tampered with or not. 

Options are:

  • None - Default for Caller and Rendez-vous modes. Not available for Listener mode.

  • Auto - Default for Listener mode. Not available for Caller or Rendez-vous modes.

  • AES-GCM - Available for Caller, Listener, and Rendez-vous modes.

Setting the authentication to Auto allows the Listener to accept Callers with authentication set to either None or AES-GCM. Listeners with the authentication set to AES-GCM will only accept Callers which are also set to AES-GCM. 

SRT Access Control ALL TBD

(Mode must be set to Caller) Toggle on to enable SRT Access Control, and configure the access control settings.

Format

Select the format to configure the Stream Publishing ID:  

  • Default: Simplifies defining the Stream Publishing ID. The Stream Publishing ID  field is read-only and auto-fills when you fill in the RES (Resource) Name and User Name  fields.
    Example Default format: #!::u=admin,r=haivision1 ,m=publish

  • Manual: Allows you to enter the Stream Publishing ID using your own format. 

Host

(Default Format only) Enter the host IP address.

RES Name

(Default Format only) Enter the resource name. The resource name facilitates resource selection, should the listener party be able to serve multiple resources.

User Name

(Default Format only) Enter the user name. The user name is picked up by the listener to determine which password should be used for the connection.

Stream ID

(Default Format) Read-only/auto-filled when Resource Name and User Name fields filled in.

(Manual Format) Enter the Stream Publishing ID using your own format. 

TCP Settings

Input Setting

Description/Values

Mode*

Select the TCP connection Mode:

  • Caller (default): Kraken acts like a client and connects to a server listening and waiting for an incoming call.

  • Listener: Kraken acts like a server and listens & waits for clients to connect to it.

Address*

(Caller Mode) Type in the destination IP address for the TCP stream.

Tip

You can also enter a Fully Qualified Domain Name (FQDN).

Port*

In Caller Mode – Specifies the destination port for the TCP stream.

In Listener Mode – Specifies the local port for the TCP stream.

Values can be between 1025 and 65535.

Network Interface*

(Listener Mode only) Select the network (Ethernet) interface for the Input, either:

  • Auto (default): Uses static route, if defined; otherwise uses the default

  • LAN1

  • LAN2

  • ...

Note

Network Interface names for Ethernet interfaces may vary, such as LAN1/LAN2/..., eth0/eth1/…, pNp1/pNp2/…, or em1/em2/….

To configure customized names for the network interfaces, as shown in the following example, see "User Description" under  Network Settings.

Warning

Because input multicast listening routes are based on IP addresses, do not reuse the same address even if it is assigned to different NICs. Doing so would produce corrupted output in all associated sessions.

Encoding Settings

Input Setting

Description/Values

ST2110 Capture

Address*

(Source must be ST2110) Type in the IP address or hostname of the SFP SDI→ IP gateway. 

IP Port*

(Source must be ST2110) Type in the IP Port of the SFP SDI→ IP gateway. Range: 0, 65535

Device Port*

(Source must be ST2110) Type in the Device Port of the SFP SDI→ IP gateway. Range: 1,4

GigE Vision Capture 

Device Address*

(Source must be GigE Vision) Type in the GigE Vision camera IP address or hostname. Kraken then registers the device and populates the Video Mode and Chroma options. Note that there can only be one input configuration per device (camera). 

Video Mode

(Source must be GigE Vision) Select the video mode from the drop-down list of available resolutions and frame rates, or use the current camera settings.

Chroma

(Source must be GigE Vision) Select the chroma value from the drop-down list, or use the current camera settings.

NDI (Network Device Interface)

NDI Source Name

(Source must be NDI) Select the NDI source name from the drop-down list of NDI devices (discovered on the network).

SDI DeckLink Capture

DeckLink Mode*

(Source must be DeckLink) Select the capture card mode, either:

  • Auto (default)

Note

DeckLink inputs match the SDI source input regardless of whether Auto is set or the chosen inputs match. When set to Auto, Kraken attempts to detect the input resolution and frame-rate. If the input resolution and frame-rate cannot be detected, then you have the option of providing a resolution and frame-rate hint to the DeckLink card so as to allow the DeckLink card to lock on the input signal. The selected DeckLink input resolution and frame-rate must match the actual input resolution and frame-rate for the signal to be correctly recognized and processed.

Tip

Auto may not work correctly for some cameras. For instance, the capture card may detect a wrong mode. Also the capture card may not detect all sources for all modes. For instance, it may correctly detect a certain camera when it is in 720-60p but not when it is in 720-50p. Therefore, we recommend that you use Auto mode when possible and when it works, and use the manual mode selection if necessary. Also, some capture cards do not support “Auto” in which case only the supported modes of the capture card will be listed and can be selected.

  • Manually select the resolution.  

Analog Capture

Analog Capture Mode*

(Source must be Analog Capture) Select the capture card mode, either:

  • Auto (default)

  • Manually select the display system (NTSC, PAL, etc.)

Note

An asterisk (*) next to a field indicates that it is required.

Related Topics

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.

Contact Support Close