Input Settings

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.

Select the Source for the Input:

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

  

  Note

  On networks with multiple sources targeting the same Kraken TS over UDP Input on either:

  1. the same multicast address and port simultaneously, or,
  2. the address and port of the Kraken instance simultaneously,

  Kraken will automatically latch onto one available source and ignore the other sources. If the current latched source is idle for 10-15 seconds, Kraken will select an alternate source. This functionality applies to both unicast and multicast reception. 

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

• 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.

  • As of Release 3.1, you may configure Kraken to transmux RTSP input to TS/UDP or TS/SRT output using Bypass mode.  

    

    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

  • As of Release 3.2, you can  select transport options equivalent to ffplay command line arguments for RTSP input including  TCP, UDP Multicast and HTTP tunneling.

• 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. 
  
• RTMP: (Real-Time Messaging Protocol)  Select to configure Kraken to  input RTMP streams in Bypass mode. See Connecting an RTMP Input Source.  

• MJPEG over HTTP: Allows you to input MJPEG video streaming over HTTP.
  To configure MJPEG over HTTP, select MJPEG over HTTP as the Source and then enter the URL. Both IPv4 and IPv6 URLs are supported, and they must contain either 'http://' or 'https://' as part of the string. 
  

Note

MJPEG over HTTP inputs are only compatible with transcoder mode, and cannot be used in a stream if the mode is set to Transcoder+Passthru or Bypass.

• 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). To select the appropriate port for your NDI input, consult the following table: 
  

  Port Number	Type	Use
  5353	UDP	Standard mDNS port used to scan for NDI hosts on the local network and report their hostnames.
  5959	TCP	Used by NDI Discovery Server as an alternate means to mDNS.
  5960	TCP	NDI hosts listen on this port for configuration/status. Used for remote queries of NDI sources on this listening host.
  5961+	TCP	Base TCP connection for each NDI stream for configuration/status. One port is used for each current connection.
  5960+	UDP	Used for reliable UDP connections for configuration/status. Port range also used in NDI Connection Sharing.
  6960+	TCP/UDP	NDI hosts receive data from one port within this range for each connection.
  7970+	TCP/UDP	NDI hosts send from this one port within this range for each connection.

  

  NDI Sources

  NDI sources may interfere with Kraken inputs from other sources. For best performance we recommend running NDI streams on a separate Kraken appliance, or using a port range beneath 5959 to allow the dynamic port range usage of NDI to co-exist with other streams.

• 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.

(Source must be TS over UDP, RTSP, RAW Motion JPEG, or MJPEG over HTTP) Type in the source URL for the Input, for example, udp://239.100.100.100:5000
Examples of supported input formats:

• udp://239.100.100.100:5000 = multicast UDP to 239.100.100.100 port 5000
• udp://:5000 = unicast UDP. Allows an inbound stream to be sent to this server's IP address on port 5000

• tcp://10.66.132.20:4045 = unicast TCP on 10.66.132.20 port 4045

• rtsp://10.66.162.133/axis-media/media.amp = RTSP input

• http://192.168.0.202:9000 = MJPEG over HTTP input to 192.168.0.202 on port 9000

• rtmp://mediaserverdemo.leadtools.com:80/vod/sample.mp4 

  

  Note

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

(Source must be TS over UDP or Raw Motion JPEG, and source IP address must be IPv4 ) 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.

(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
• eth0
• eth1
• ...

Note

Network Interface names for Ethernet interfaces may vary, such as 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.

Caution

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.

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

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

(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.

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

Displays the connection status as the remote source device address (gigevis_address) when connected to a stream.  

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

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

• Autodetect (default)

  

  Note

  DeckLink inputs start up and match the input regardless of whether Autodetect is set or the chosen inputs match. When set to Autodetect, 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

  Autodetect 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 Autodetect mode when possible and when it works, and use the manual mode selection if necessary. Also, some capture cards do not support “Autodetect” in which case only the supported modes of the capture card will be listed and can be selected.

• Manually select the resolution. 

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

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