Recent updates
-
Bolt App
Updated onArticlesUse the Bolt App to remotely manage and monitor every parameter of Bolt 6 including pairing, frequency selection, and 3D LUTs.
Wireless Video Bolt 6 Bolt App
-
Device Placement
Updated onArticlesBolt 6 XT/LT devices have a 1/4”-20 threaded hole (additional 3/8”-16 threaded hole on the receiver) on the bottom for mounting the included light stand adapter or any other mounting accessory.
Wireless Video Bolt 6 Mounting
-
Device Operation
Updated onArticles- Keep the transmitter and receiver at close range for 60 seconds after powering on the devices. This allows them to scan for and select the best wireless frequency.
- For best results when using multiple Bolt systems in the same area, place the transmitters and receivers a few feet apart from each other.
- Operation of other wireless equipment may interfere with the Bolt. Try to separate other wireless transmitters and receivers as much as possible.
Wireless Video Bolt 6 Getting Started
-
Transcoding between HEVC streamed input to H.264 streamed output in Core
Updated onArticlesOverview
Core allows real-time transcoding between an HEVC / H.265 input stream to an H.264 / AVC output stream.
This allows an HEVC stream from an encoder to be converted and delivered to hardware decoders or clients that only accept H.264 streams or the use of streaming protocols that only support H.264.
The RTMP streaming protocol is not compatible with HEVC, but the MPEG-TS protocol and SRT protocols both support the HEVC codec in addition to the older H.264 codec.
NOTE: if transcoding is not activated, the incoming HEVC stream from the encoder will be left at HEVC by the Hyperion server and will not be converted to H.264. This means that both the outbound streams sent from a Core-controlled Hyperion must be capable of supporting the HEVC codec, and the destination must also be capable of receiving HEVC.
Transcoder Settings
At this time, there are no configurable settings for the transcoder and all settings are determined automatically.
The transcoded video output resolution, key frame interval, and video frame rate will match the input.
The transcoded video bitrate is based on the video resolution (height and width), encoded frame rate, and encoded key frame interval of the input, based on this formula:
29*w*h*(1+(g-1)*0.2)/gSubstitute w and h for width and height in pixels, and g for the key frame interval (GOP size) in frames. For example, if your encoded video frame rate is 60 and your key frame interval is 2 seconds, the GOP size is 120 (60*2). For 30 fps and 2 seconds, the GOP size is 60 (30*2).
For convenience, online calculations can be done using Wolfram Alpha (clickable link).
These transcoder settings apply for both the VidiU Go and the 700 series encoders.
Cloud Services Core Servers
-
Helios Streaming Server: What's the Purpose and the difference between Generic Helios and Backup Switcher?
Updated onArticlesHelios is a server that provides extra features not found on Hyperion. It’s a great set of features that can provide reliability (Backup Switcher) and more flexibility (Generic ingest) for your live streams.
Key Helios features are:
Generic Ingest:
- bring in video feeds from 3rd party sources or Teradek encoders via RTMP, SRT, MPEG-TS Push or Pull;
NOTE: Supports only 1 input.
- playback already recorded files via Core Archive or Custom URL;
NOTE: Supported file types for playback: MKV, MP4, FLV, MPEG-TS
- Stream using your Webcam via WebRTC input.
Backup Switcher:
- bring in video feeds from 3rd party sources or Teradek encoders via RTMP, SRT, MPEG-TS Push or Pull;
NOTE: Supports up to 5 inputs.
- playback already recorded files via Core Archive or Custom URL;
NOTE: Supported file types for playback: MKV, MP4, FLV, MPEG-TS-Auto-failover and manual switching between network streams or video files;
(Path redundancy allows you to automatically or manually switch to a back up stream or video file when your main video feed fails or disconnects).
The Backup Switcher will only work properly if each input has identical video properties: codec, resolution, pixel format, codec profile, and level. Only AAC audio is supported at this time. H.264 feeds with B-frames are not supported.
Both Generic and Backup Switcher are:- Supporting the following stream modes:MPEG-TS, SRT, FLV, and RTMP/S (including Youtube, Facebook, Twitch, Vimeo, IBM Video Streaming, LinkedIn, Wowza, Livestream, EasyLive.io)Note: HLS and RTMP/S requires the output stream be H.264
- Restreaming H.264/H.265 video with AAC audio at any resolution and bitrate
- Web browser streaming (H.264 only)If the input stream is H.265 and you require web browser playback support, then you will need to select for a server upgrade.
- Cloud recording and file downloading;
- CoreTV streaming with voice and text chat collaboration;
- Supporting Teradek apps (Click here for more info).
Cloud Services Core Servers
-
On-demand, Cloud Hyperion and Self-hosted Hyperion: What's the Difference?
Updated onArticlesHyperion is just a fancy term for our streaming server software that sits in the cloud. Hyperion servers are the basis for many of the things you can do in Core, including multi-destination streaming, remote configuration, and bonding. A Hyperion server is required for general operation on our cloud. We have implemented these servers in a few different ways:
On-Demand: Everybody gets an On-Demand server automatically when their encoder connects to Core. You don’t even have to think about it. These servers are designed to be efficient so they spin up / shut down as the user needs them. The IP address of the server is dynamic so it may change every time a new On-Demand server is spun up. If you require a fixed IP address, take a look at a Cloud Hyperion. On-Demand Hyperion servers cannot use the Share Stream function for CoreTV.
Cloud-Hosted Hyperion: These are nearly identical to On-Demand servers in functionality, but have a different implementation. Each instance supports up to 5 simultaneous encoders, allows the “Share Stream” function for CoreTV, gives output links to connected encoders and comes with a dedicated IP address. These are generally more reliable than On-Demand servers because they are a dedicated resource just for you. Cloud Hyperion cost depending on your Core Subscription.
Self-Hosted Hyperion: Also identical to the other two servers, these are for installation at your data center or facility. Self-hosted servers do not come with data charges because the customer is providing all of the bandwidth. However, these servers are leased for a monthly fee and require separate fees to keep them connected to Core. If you’re a business with a dedicated gigabit fiber line and plan to put a lot of traffic through Core, this is a good option for you.
NOTE: Self-hosted/On-Premise Hyperion Servers are available for Enterprise Plan only. If you would like to upgrade your plan, please, reach out to our Sales department at [email protected] or Mon-Fri 9am to 6pm +1 (888) 941-2111 or +1 (949) 743-5780Cloud Services Core Servers
-
Using older generation Teradek encoders with Core
Updated onArticlesApplies to:
- 1st / 2nd generation Cube encoder
- 1st generation Slice encoder
- Bond / Bond II / Bond Pro
- 1st generation T-RAX encoder
Overview
When using older generation units with Core, it can take 3 to 4 minutes for the device to boot up and appear online in the Core interface and be ready to stream, even when using the recommended 7.3.14 firmware release.
Additional steps are sometimes required to have the video encoding and preview images appear properly or to start a stream.
Workarounds / Troubleshooting
Firmware version 7.3.14 is recommended for these older devices instead of later versions such as 7.3.16 or the final 7.3.18 release.
The 7.3.14 version has been found to have the most consistent performance and results when used with Core.
This firmware version is available at the respective product's download page (direct link here, or go to teradek.com > Support > Downloads, choose the product, then click the Show Previous Versions button).
If the encoder has been connected for 5 to 10 minutes in Core and instead of preview images shows "Waiting for Control", "Initializing Video", or other messages in the preview area, or it gives an error when trying to start a stream, try the following troubleshooting steps in this order:1) Restart the Hyperion server
- if you are using a dedicated Hyperion server, then restart the Hyperion server using the Core interface (do not use the older Hyperion Dashboard, use the option in the Core interface under Engines for that specific Hyperion server).
- If you are using the default / On Demand Hyperion servers then you are unable to restart as they are a shared resource with no direct control. You can try switching to a different On Demand Hyperion server group, then back to the original.
2) Restart the video encoding process
- on the 2nd generation Cube / Slice / Bond II / Bond Pro encoders, use the display and menu buttons on the side of the unit: press the red button to access the Quick Action, menu scroll to the bottom and select Restart Encoder. This will take approximately 30 seconds, but is faster than rebooting the entire unit and can help if you see it waiting in Initializing Control or other states in the preview area of the Core interface.
- on 1st generation Cube or the 1st generation T-RAX encoder, or any other device where you don't have physical access to the unit you can use the device's local web interface or the option within the Core interface to restart the video encoding process on the Cube from within the Core UI under the settings for the device.
3) Reboot the encoder
- reboot the encoder using the power switch on the device, the local web interface or the option through the Core interface, and then try the steps above if needed.
Cloud Services Core Workflow Guides
-
Network communication requirements for using Teradek Decoders with Core
Updated onArticlesOverview
Teradek decoders and some apps and software clients require the following network ports for use with the Core management system.
Inbound Network Connections
In the standard scenario for using Teradek Decoders with Core, no incoming connections are needed from either the Core management system or a Hyperion server.
However, if you are sending a stream from an external Hyperion server to a standalone Teradek decoder or third party decoder using a supported streaming protocol (e.g. MPEG Transport Stream / MPEG-TS, or SRT) those connections would originate from the IP address of the Hyperion server and would need to reach the decoder on the custom port you have specified.
Be sure to configure firewalls and routers for any port forwarding needed in these circumstances.
Outbound Network Connections
Outbound connections are initiated by the Teradek decoder or app or software client, and arrive at the remote server on the indicated port.
If the Teradek decoder/app/software client 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 over TCP.
- 5111 (UDP) : Communication with a Core-deployed Hyperion server, or a self-hosted Hyperion server using the default port over UDP. This is optional, and only possible on the 600, 700 and Prism series and decoders.
- 5200-5299 (TCP) : This port range is used by default to pull down MPEG-TS video streams from a Core-deployed Hyperion server or a self-hosted Hyperion server. These ports are also used by apps like the Core app for iOS, or software clients like VLC Media Player or vMix or Wirecast to pull down the stream from a Hyperion server.
- 5500-5599 (UDP) : This port range is used to pull down SRT video streams from a Core-deployed Hyperion server or a self-hosted Hyperion server when the encoder source is switched to the secure streaming mode. These same ports are also used by apps like the Core TV app for iOS, or software clients like VLC Media Player or vMix to pull down the SRT stream from a Hyperion server when the encoder is in that mode.
- 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.
Cloud Services Core Network communication requirements
-
Network communication requirements for using On Demand Hyperion servers in Core
Updated onArticlesOverview
When an On Demand Hyperion server is used, the server is handled differently by Teradek encoders, decoders, or apps compared to using a dedicated Hyperion server that is hosted by Core, or a self-hosted Hyperion server that is associated with a Core account.
Network port ranges and IP addresses used by the On Demand Hyperion can change between each use of the service. Teradek devices and apps are able to automatically obtain the current IP address and port for the On Demand Hyperion region.
In comparison, a dedicated Hyperion server allows a consistent IP address and range of ports to always be available.
Core Subscription Levels
On Demand Hyperion servers are accessible at any Core subscription level.
Since the IP address and ports used with an On Demand Hyperion server can change, there are some scenarios where it may not be possible to use an On Demand Hyperion server. For example:
- If there are stringent security requirements on a network -- e.g. a static destination IP address or limited port range must be approved for outbound connections through a business firewall.
- Another use case which would require a dedicated Hyperion server is the use of 3rd party streaming software like Telestream Wirecast or vMix. Third party products cannot determine the On Demand Hyperion server's address or ports, and are not supported for use with On Demand Hyperion servers.
If you have similar requirements on a network, you would not be able to use the On Demand Hyperion servers and would need to choose a subscription plan that allows a dedicated Hyperion server.
Network Port Requirements
The following port ranges must be allowed for connections to an On Demand Hyperion server:
Inbound Network Connections
No incoming connections are needed from either the Core management system or an On Demand Hyperion server to allow a Teradek encoder, decoder or app to communicate.
Outbound Network Connections
-
1024-65535 (TCP). This port range is used for the following:
- Streaming from a Teradek encoder or app to the On Demand Hyperion server using the TCP protocol.
- Receiving / pulling down MPEG Transport Stream from the On Demand Hyperion server back to a Teradek decoder. This type of pulled MPEG-TS connection always uses the TCP protocol.
-
1024-65535/UDP : This port range is used in the following scenarios:
- By Teradek encoders capable of using the UDP protocol for streaming video into an On Demand 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.
- By Teradek hardware decoders or Teradek apps (Core TV for iOS or macOS, or VUER for Android, iOS or macOS) capable of using the SRT protocol to receive video from an On Demand Hyperion Server.
- By Teradek encoders capable of using the UDP protocol for streaming video into an On Demand Hyperion server.
If these outbound port ranges are blocked then it may not be possible for the encoder or decoder to make a connection to the On Demand Hyperion server on that particular network interface (Ethernet, USB modem, or Wi-Fi).
Outbound port blocking may be encountered on shared network connections at public venues (hotels, airports, coffee shops) or at facilities with restrictive security settings such as school, government, or business networks.
Cloud Services Core Network communication requirements
-
Point-to-Point Overview with Teradek Core (video)
Updated onArticlesCloud Services Core Video Tutorials