Recent updates
-
Launchpad
Updated onArticlesWith Launchpad, you can configure all of your Ranger devices at once. Available as software for Windows and Mac, Launchpad allows you to pair multiple receivers to your transmitter, select frequencies, and perform firmware upgrades.
Wireless Video Ranger HD and 4K Configuration
-
Info
Updated onArticlesDEVICE INFO
Reset all configurable options to their factory defaults.FIRMWARE VERSIONS
Displays the current firmware versions for all device components.REGULATORY
Displays all compliance certifications relating to radio frequencies used by the TX and RX to communicate.
For complete regulatory information and declarations of conformity, please visit the Regulatory Information section.Wireless Video Ranger HD and 4K Configuration
-
Advanced Settings
Updated onArticlesLOCK KEYPAD
Enabling the Lock Keypad feature prevents the menu joystick from being used to avoid any accidental or unauthorized configurations. There are two ways to lock the keypad:- Navigate to Advanced Settings via the front panel and select Lock Keypad.
- Press and hold the menu joystick upward for 5 seconds.
To unlock, press and hold the menu joystick upwards for five seconds or until the display reads "KEYPAD UNLOCKED."
HDMI (RX only)
Ranger supports all HDMI output modes. You can select from one of the following options:- Auto
- RGB 8bit
- RGB 10bit
- YCbCr 4:4:4 8bit
- YCbCr 4:4:4 10bit
- YCbCr 4:2:2 10bit
- YCbCr 4:2:0 8bit
- YCbCr 4:2:0 10bit
AUDIO (RX only)
Configure Ranger’s Audio settings. If Beep on REC is activated, you will hear a short tone whenever the camera begins or stops recording. The Mute Settings allow you to completely mute the audio or only mute audio while recording.- Beep on REC - Short tone when the camera begins or stops recording
-
Mute Settings- Select an option:
- Off
- Mute while recording
- On
BLUETOOTH
Use the Bluetooth menu to enable or disable Bluetooth communication.- Enable Bluetooth - Allows transmitter and receiver to be paired and communicate with the Launchpad App.
- Use Bluetooth PIN - Enables the use of a PIN for authentication when using the Launchpad App.
- Change PIN - Press the Menu joystick towards the right to change the Bluetooth PIN
NOTE: Bluetooth is disabled by default. To configure your Ranger devices via the Launchpad App, you must first enable Bluetooth.
BACKGROUND COLOR (RX only)
The Background Color feature allows you to select a screen color to be displayed on the monitor when there is no video being received from the transmitter. This is a useful tool that indicates to the crew that a signal has been dropped and the TX and RX need to be synced again.RESET ALL SETTINGS
Reset all configurable options to their factory settings.Wireless Video Ranger HD and 4K Configuration
-
Video Settings Configuration
Updated onArticlesUse the Display Settings to control the OLED display operation. By default, the OLED display will invert every 30 minutes. You can set the display to invert every 30 minutes (lengthens the display life), or it can dim or turn off after either 10 minutes or 10 seconds.
- Rotate 180°
- Invert every 30 min
- Dim every 10 min
- Dim after 10 sec
- Dim after 10 min
- Off after 10 sec
- No Burnin Prevention
Wireless Video Ranger HD and 4K Configuration
-
Pairing and Unpairing
Updated onArticlesRanger devices purchased as a set (TX and RX) are paired by default, requiring no additional configuration. Ranger devices purchased separately need to be paired using the device's front panel (OLED) menu, Launchpad, or the Launchpad App. You will need to use either Launchpad, or the Launchpad App to pair your transmitter with multiple receivers.
NOTE: Before starting either pairing process, ensure that both the transmitter and receiver have the same firmware version and have Bluetooth enabled.Wireless Video Ranger HD and 4K Configuration
-
Wireless Configuration
Updated onArticlesRanger contains several wireless configuration options that allow the system to work at its best in different environments. The system is designed to work adequately using its default, automatic settings, but they may not be ideal for all situations. This section details all available wireless configuration options for the transmitter and receiver.
Wireless Video Ranger HD and 4K Configuration
-
Serv Micro Quick Start Guide
Updated onArticlesServ Micro lets you securely stream live camera feeds and instant recordings to anyone, anywhere, on or off set. See what the camera, editor, and colorist see—from production through final color. Serv Micro can encode up to 1080p60 video with stunning 8-bit 4:2:0 image fidelity, and can be connected to Teradek’s Core Cloud Platform for even more flexibility.
Encoders - Cube, Prism and Vidiu Products Serv Quick Start Guides
-
Server Launch Tutorial
Updated onArticlesBelow you will find the Guide for Hyperion and Helios server launch using Core and the Core App. More details on Launching Transcoding servers on Core plans can be found here.
Cloud Services Core Servers
-
Network communication requirements for using Self-hosted and Cloud Hyperion servers with Core
Updated onArticlesOverview
The tables below list the inbound / incoming and outbound / outgoing network connection requirements for using a self-hosted Hyperion server with the Core management system.
This covers the necessary ports and protocols needed for the following:
- Teradek encoder and app communication with the Hyperion server, as well as inbound video streaming to the Hyperion server.
- Teradek decoder communication with the Hyperion server, as well as decoders, apps or software clients to pull down the MPEG Transport Stream or SRT video hosted from the Hyperion server.
- Outgoing ports needed for a Hyperion server to send out video streams over RTMP or RTMPS to destinations like Facebook Live or YouTube Live, or over MPEG Transport Stream or SRT.
- Outgoing ports needed for a Hyperion server to communicate with the Core management system.
Inbound Network Connections
Inbound connections originate from outside the Hyperion server, and arrive at the Hyperion server on the indicated port.
If the self-hosted Hyperion server is behind a firewall, the necessary ports will need to be forwarded to the internal, private IP address of the Hyperion server.
- 22 (TCP) [optional] : SSH access to the Hyperion server; this is optional and not required in any way for operation with Core. This is under user control, and is recommended that it is disabled unless proper security measures are in place for your self-hosted Hyperion server.
- 443 (TCP) [optional] : HTTPS communication for HLS preview streams. Requires special configuration and use of a TLS/SSL certificate specific to that server.
- 1957 (TCP) [optional] : HTTP communication with the Hyperion Dashboard / Web User Interface (Web UI). This is optional and not required for operation with Core, as all device control is done through the Core Dashboard.
- 1958 (TCP) [optional] : HTTPS communication with the Hyperion Dashboard / Web User Interface (Web UI). This is optional and not required for operation with Core, as all device control is done through the Core Dashboard.
- 5111 (TCP) [REQUIRED] : Communication port used by Teradek encoders and decoders to register with the Hyperion server. Also used as the inbound video port from Teradek encoders and streaming apps (Live:Air Action or Live:Air Solo).
-
5111 (UDP) [REQUIRED]: Inbound video port used by Teradek encoders capable of using the UDP protocol for streaming video to a Hyperion server.
- Streaming with the UDP protocol is available on a Cube + Bond (original), Bond II, Bond Pro, or 600 / 700 / 800 series encoders, and the streaming protocol is changed from the default TCP to UDP.
- This does not apply to a standalone Cube (1st or 2nd gen), Slice encoder (1st gen), T-RAX encoder, or apps.
-
5200-5299 (TCP) [optional]: Video ports registered by the Core management system to allow hardware decoders, software decoders (e.g. VLC Media Player, vMix or Wirecast) , or Teradek apps (Core TV, Core app for iOS, or VUER) to pull down the video stream directly from a Core-controlled Hyperion server using the MPEG-TS protocol over TCP.
- MPEG-TS is used as the default stream output by default (the checkbox for Secure Streaming is not selected).
- If MPEG-TS video streams are not being pulled down by remote decoders (e.g. only outbound RTMP or SRT streaming is being pushed out to remote destinations), these ports are optional.
-
5500-5599 (UDP) [optional]: Video ports registered by the Core management system to allow decoders or remote sources to pull down the video stream directly from a Core-controlled Hyperion server using the SRT protocol over UDP.
- SRT is used for the stream output instead of MPEG-TS when an encoder in Core is placed in the Secure Streaming mode.
- If SRT video streams are not being pulled down by remote decoders (e.g. only outbound RTMP or SRT streaming is being pushed out to remote destinations), these ports are optional.
-
5600-5699 (TCP) [optional] : Video ports registered by the Core management system to allow decoders or remote sources to pull down the video stream directly from a Core-controlled Hyperion server using the RTSP/RTP protocol over TCP.
- RTSP/RTP is shown as a stream output (in addition to MPEG-TS when an encoder in Core is placed not in the Secure Streaming mode.
- If RTSP/RTP video streams are not being pulled down by remote decoders or software clients (e.g. only outbound RTMP or SRT streaming is being pushed out to remote destinations), these ports are optional.
- 8643 and 7011 (TCP) : For Prism, Prism Flex, Wave and Serv 4K to connect.
Outbound Network Connections
Outbound connections are initiated by the Hyperion server, and arrive at the remote destination on the indicated port.
If firewalls are in place that block outbound traffic, the necessary ports need to be allowed for outbound connectivity to ensure proper communication with the Core management system and streaming to different destinations.
If firewalls are in place with content filtering, those content filters may block access to some sites categorized as related to social networking; content filter restrictions would need to be removed for the Hyperion server to be able to send out RTMP/RTMPS streams to those destinations.
- 80 (TCP) : Upgrades of the Hyperion server by the Core management system. This same port is also used for RTMP streams sent over port 80 to Periscope Live, but the destination addresses will be for Periscope's streaming servers.
- 443 (TCP) : Software upgrades of the Hyperion server, as well as command/control communication to the Core management system. Also used for RTMPS streams to Facebook Live, but the destination addresses will be for Facebook's streaming servers.
-
1935 (TCP): RTMP streams sent to common online video platforms / CDNs like YouTube Live or Akamai. If RTMP streaming is not being used (e.g. only streaming between encoders and decoders), this port is optional.
- NOTE : if RTMP streams are being sent to a third party device, server or hosted service on a port other than the default 1935, that port would likewise need to be permitted through any outbound firewalls that are filtering traffic based on the destination port.
- 6000 (TCP) : Additional communication channel between the Hyperion server and the Core management system.
- 7000 (TCP) : Transfer of recorded video archives from the Hyperion server to the Core management system / archive repository.
- 7001 (TCP) : Additional communication channel between the Hyperion server and the Core management system (required as of Hyperion Core Client version 2.3.0 and later).
- 7002 (TCP) : Additional communication channel between the Hyperion server and the Core management system (required as of SHyperion Core Client version 2.3.0 and later).
-
9710 (TCP): MPEG Transport Streams sent over the TCP protocol; this port is configurable in the Core system, so if you're sending to a different port this must be allowed by any outbound firewalls.
- If you're not using outbound MPEG-TS streaming (e.g. only using outbound RTMP or RTMPS, or using MPEG Transport Stream or SRT pulled down directly from the Hyperion server) then this port is optional.
-
9710 (UDP): MPEG Transport Streams or SRT streams sent over the UDP protocol; this port is configurable in the Core system, so if you're sending to a different port this must be allowed by any outbound firewalls.
- If you're not using outbound SRT or MPEG-TS streaming (e.g. only using outbound RTMP or RTMPS, or using MPEG Transport Stream or SRT pulled down directly from the Hyperion server) then this port is optional.
- 30443 (TCP) : TLS-secured communication channel for real-time logging between the Hyperion server and the Core management system (logbay.teradek.com)
Cloud Services Core Network communication requirements
-
Network communication requirements for using Teradek Encoders with Core
Updated onArticlesOverview
Teradek encoders and apps require the following network ports for use with the Core management system.
Inbound Network Connections
No incoming connections are needed from either the Core management system or a Hyperion server.
Outbound Network Connections
Outbound connections are initiated by the Teradek encoder or app, and arrive at the remote server on the indicated port.
If the Teradek encoder or app is behind a firewall, and that firewall blocks or filters outbound traffic, the necessary ports must be open to allow communication and streaming.
- 80 (TCP) : Communication with the Core management system.
- 443 (TCP) : Communication with the Core management system.
- 5111 (TCP) : Communication with a Core-deployed Hyperion server, or a self-hosted Hyperion server using the default port. Also used by encoders or apps streaming video with the default TCP protocol. This includes Cube + Bond (original), Bond II, Bond Pro, the Cube / Bond / Slice 600 and 700 series encoders, VidiU Go, and Prism encoders. This also includes a standalone Cube Encoder, Slice Encoder, or T-RAX Encoder.
-
5111 (UDP): Used by encoders capable of using the UDP protocol for streaming video to a Hyperion server.
- Streaming with the UDP protocol is available on a Cube + Bond (original), Bond II, Bond Pro, 600 and 700 series encoders, and Prism encoders. The streaming protocol is changed from the default TCP to UDP.
- This does not apply to a standalone Cube (1st or 2nd gen), Slice encoder (1st gen), T-RAX encoder, or apps.
- 1024-65535 (TCP) : Communication and video streaming to an On Demand Hyperion server from devices and apps using the default TCP protocol. If On Demand Hyperion servers are not being used, this port range is optional. See this article for additional information.
- 1024-65535 (UDP) : Communication and video streaming to an On Demand Hyperion server from devices which support the UDP protocol. If On Demand Hyperion servers are not being used, this port range is optional. See this article for additional information.
- 8643 and 7011 (TCP) : For Prism, Prism Flex, Wave, Serv 4K to connect to Core.
Cloud Services Core Network communication requirements