800.885.8886 sales@telvue.com
  • Facebook
  • Twitter
  • Facebook
  • Twitter
TelVue
  • Home
  • Products
    • Playback & Automation
      • HyperCaster®
      • ProVue®
        • ProVue® HD
        • ProVue® GFX
        • ProVue® CC
      • TelVue TeleCastTM 2
    • Streaming/Cloud
      • TelVue CloudCast™
      • TelVue Connect™
      • Media Exchange
      • Mobile & OTT Apps
      • TelVue SmartCaption™
    • Digital Signage
      • TelVue InfoVue™
    • Automatic Captioning
      • SmartCaption™
    • Ad Insertion
      • TelVue AdCaster™
  • Solutions
    • Cable/Telco
    • Community Media
    • Media Companies
  • Support
    • Knowledge Base
    • Webinars
    • Training Videos
    • Documentation
    • Contact Support
  • News
    • Blog
    • Press
    • Awards
  • Client Logins
    • Connect/CloudCast
    • InfoVue
  • Contact Us
    • General & Sales
    • Technical Support
Select Page

HyperCaster

HyperCaster User Manual
    HyperCaster Configuration
    • Config Tab
    • Channel Setup
    • Continuity
    • Live Streams
    • Feed Setup
    • NDI Access Manager
    • ProVue Decoder Configuration
    • Configure In/Out Ports
    • Encode Profiles
    • Manage TeleCasts
    • Streaming Destinations
    • Streaming Rules
    • User Management
    • Content Settings
    • Pro Transcoding
    • Schedule Configuration
    • InfoVue XML
    • Switch Configuration
    • Remote Server Configuration
    • TelVue Connect Configuration
    • Captioning Configuration
    • Server Management
    • NTP, NTP Configuration, and NTP Health
    • Security Configuration
    • Network and Security
    • Setting up SSL/HTTPS on the HyperCaster
    • Backup Settings
    • IPMI
    • Config – Utilities
    • Version and Configuration
    • SNMP Support
    • External Devices
    • Brightcove EPG Integration
    • Add an RTMP Stream
    • Set Up an RTMP Stream in a HyperCaster
    • Set Up an SRT Stream in a HyperCaster
    • Set Up an HLS Stream in a HyperCaster
    • Get Channel Schedule as XML (Detailed)
    HyperCaster Content Management
    • Organize and Add Content
    • Content Management
    • Thumbnail and Table Views
    • Show Content Page
    • Content File Actions
    • Add TBD Program
    • DVD Import
    • Replacement Files Hot Folder
    • How to Trim a Video File (Virtual Trimming)
    • Trim Content (Built-in, Multiple Trim Editing)
    • Tasks
    • Previews
    • Turn On Transcoding
    • Create a HyperCaster Playlist
    • Series & Series Scheduling
    • Record or Capture
    • Upload to Connect/CloudCast
    • Archiving
    • Archive.org integration
    • Content Workflow Rules
    • Preparing Content for the HyperCaster
    • Content RSS Feed
    • Export to CSV
    • Searching
    • Using Third-Party Editing Software
    HyperCaster Programming
    • The Dashboard
    • Programming
    • Calendar View
    • Classic View
    • Search Filters and Event Functions
    • Field Descriptions and Display Options
    • Program Playout Event
    • Program Stream Event
    • Program Record Event
    • Program Input Event (AIO Only)
    • Input Locking
    • Program Switch Event
    • Scheduling a Live Switch Event whose Actual Duration Varies
    • Program Playlist Event
    • Program Overlay Event
    • Program Slide Event
    • Program Ad Trigger Event
    • Unschedule an Event
    • Event Actions
    • Copy Program Blocks
    • Import and Export events
    • Native CSV Formatting
    • Scheduling Conflicts and Ripple
    • Recurring Events
    • Controlling What Appears in the Program Guide
    • Publishing Your Schedule
    • Schedule Ads
    HyperCaster Graphics
    • Graphic Overlays
    • Overlay Rules
    • Bugs
    • Tickers
    • How to Build RSS Tickers
    • Snipes
    • Clocks
    • Program Guides
    • Emergency Notification Console
    • Join in Progress Overlay
    HyperCaster Reports
    • Reports Tab
    • As Run Reports
    • Program Guide Report
    • Missing File Report
    • TelVue Connect Report
    HyperCaster Captioning
    • SmartCaption™ Automatic Captioning Integration
    HyperCaster Streaming
    • Configure In/Out Ports
    • Streaming Destinations
    • Encode Profiles
    • Manage TeleCasts
    • Streaming Rules
    HyperCaster Miscellaneous
    • System Health
    • Backups
    • Safety Requirements
    • Glossary
    HyperCaster Guide to CCMS Plus
    • Guide to CCMS Plus
    • CCMS Plus Setup
    • CCMS Schedule Remote Directory Folder Structures
    • Schedule and Media Imports
    • Verification File Export
    • Tasks Tab
    • E-Mail Notifications of Missing Content
HyperCaster FAQs
  • How do I access the UI for my HyperCaster?
  • What is the difference between, “enable continuity” and “continuity resume”?
  • Port Forwarding Rules to Allow External Access to the HyperCaster
  • How to Stream a Zoom Meeting to the HyperCaster
  • Extending an IP Capture without Re-Entering Metadata
  • YouTube Live
  • How do I set InfoVue as Continuity on the HyperCaster?
  • How do I embed a HyperCaster Program Guide in my website?
  • Facebook Live
  • What does “ripple” mean?
  • Does the preview player under edit show timecode or full length of video?
  • What is the RSS feed button in the HyperCaster?
  • How to Add a TriCaster Feed to the HyperCaster
  • Mapping the HyperCaster to Your Desktop
  • How to display NOAA weather RSS as HyperCaster Ticker
  • How to Stream a WebEx Meeting to the HyperCaster
  • Is it possible to run a PowerPoint through my HyperCaster?
  • Why is my NTP server showing a critical status?
  • How to Add a LiveU Solo Feed to the HyperCaster
  • TelVue Server LED Status Indicators
  • On the Channel Setup page, what are the “Website Guide Details” checkbox and the “TV Guide Station ID”?
  • Go LIVE from anywhere with a JVC GY-HM200 and a HyperCaster
  • How do I display Program guide?
  • What is MPEG?
  • Prepare Content for HyperCaster with Sorensen Squeeze
  • Use OBS to Live Stream Skype, GoToMeeting, or any Application Window to Your HyperCaster
  • On the “Health” page, was does NTP define?
  • Preparing Content for your HyperCaster Using Telestream Episode Pro
  • Is it possible to run two channels to the same IP address with different ports?
  • Is it possible to run two Ethernet connections out of the HyperCaster? (Additional Card Required)
  • Are 16:9 files automatically letterboxed?
  • Server rooms: some practical advice
  • Is it possible to run background audio from a stream that is different than the video scheduled (ex. Radio Feed)?
  • I am having issues with the overlays. They schedule but won’t play.
  • Loss-of-Video Failover Protection with This Easy Trick
  • On the “Edit Content” page, what does the “Private” checkbox, Location and Contributor fields define?
  • When using FTP are we able to change the password for psguser?
HyperCaster APIs
    HyperCaster API Content Workflow
    • Access All Content Metadata as CSV
    • Import Content (Hot Folder)
    • Uploading Files on Schedule
    HyperCaster API Content Methods
    • Get All Content Metadata
    • Get Content Metadata by Filename (REST)
    • Get Content Metadata by ID (REST)
    • Get Content Thumbnail (REST)
    • Add Content (REST)
    • Edit Content (REST)
    • Delete Content (REST)
    • Add Content (SOAP)
    • Edit Content (SOAP)
    • Delete Content (SOAP)
    HyperCaster API Schedule Workflow
    • Access Playback (As-Run) Log
    • Import Events (Hot Folder)
    HyperCaster API Schedule Methods
    • Get Channel Next Playing (REST)
    • Get Channel Now Playing (REST)
    • Get Channel Schedule as RSS (REST)
    HyperCaster API Channel Management
    • Get Channel Settings (REST)
    HyperCaster API System Management
    • Get System Health as RSS (REST)
    • Get Software Version (REST)
    • Get Network Settings (REST)
  • Home
  • Knowledge Base
  • HyperCaster Knowledge Base
  • HyperCaster
  • HyperCaster User Manual
  • HyperCaster Configuration
  • Add an RTMP Stream

Add an RTMP Stream

The TelVue HyperCaster supports ingest of RTMP (Real Time Messaging Protocol) streams. What follows is a primer on the RTMP protocol and how you might use it.

What is RTMP?

RTMP is a protocol developed by Adobe designed for real-time (live) video streaming across the internet. While Flash streaming has declined over the years, the RTMP protocol remains the primary method for streaming encoders to deliver to CDNs (Content Distribution Networks). Given it is TCP based, and thus stateful, it has built-in resiliency when used as a transport across networks that might have some packet loss, such as the public internet.

RTMP Push vs. RTMP Pull

RTMP has two primary methods of transport- Push, where a streaming encoder delivers the RTMP to a RTMP Server or CDN, and Pull where the client retrieves the stream and plays it back. The TelVue HyperCaster can take RTMP inbound connections both ways, though the “push” process would probably be the more common use case. An RTMP Push process means that if you have a device or application that can output RTMP like a TeleCast 2 streaming encoder, a Teradek Cube, Telestream Wirecast, a NewTek TriCaster, the LiveU Solo, or multiple other hardware or software solutions, you can deliver that feed directly to the HyperCaster via LAN, WAN, or Internet. Once the device is setup and the HyperCaster configured this method will allow you to go live from virtually anywhere that you have a reliable internet connection. This is likely the most common use case for stations using the feature whereby you will be pushing a stream directly to the HyperCaster for ingest and processing.

RTMP Pull, while it’s still the same protocol, uses a slightly different process. In this model the HyperCaster would be reaching out to a RTMP server or CDN on the internet and retrieve a stream to playback. Take, for example, you may need to share a live stream with multiple HyperCasters at once, possibly in geographically different areas. You could configure your RTMP encoder to stream to a CDN such as the TelVue CloudCast player, and then have multiple HyperCasters “tune in” and retrieve that stream. This may be useful if you’ve got a football game that two stations need to simulcast, or perhaps a large community event that needs to be distributed to dozens of places at once. The HyperCaster can also pull using other more modern protocols include HTTP Live Streaming (HLS).

Firewall Considerations

In the RTMP Pull method, firewalls tend to not be an issue. This is because the HyperCaster is requesting a stream from the internet, and thus a stateful firewall would permit that request since it originated from behind the firewall. Think of this like inviting someone into your home. You open the door, invite them in, and they walk through. However, RTMP Push methods are a completely different story. Borrowing our example from above, this method has no invitation; you have to leave the door open for the guest to walk through on their own, otherwise they can’t get in. RTMP operates on TCP port 1935 meaning with a RTMP Push you would have to configure your firewall to permit that traffic into the HyperCaster. Most routers make it fairly easy to add such a rule and many stations have an IT staff (either contracted or full time) that can help you set this up. The majority of modern routers/firewalls call this “Port Forwarding” or “Destination NAT.” Some routers refer to it as “Applications.” Firewall configuration will only be an issue if you’re trying to send the HyperCaster a stream from outside your LAN. IE: if you’re streaming from one side of the station to the other, you likely don’t have to traverse the firewall (since both devices are already behind it.) 

RTMP URL’s and Server Configuration

RTMP URL’s have a standard structure and vary based on several different things, not the least of which is Push vs Pull methods.

RTMP Push: You have to configure both the encoder and the HyperCaster with the proper RTMP URLs to work correctly. Starting with the HyperCaster receive side: 

In this instance the HyperCaster is actually acting as it’s own RTMP server, hence we’ve put in 127.0.0.1 (“localhost” would also work here since it’s the same thing.) “telvue-rtmp” is the application name that we’ve applied to any feeds that the HyperCaster is being pushed. This is a static name and cannot be changed. Finally you’ve got the “Stream Name” which is a dynamic setting that you, the user, can choose. In this example the stream name is “fmle” but this designator could be “studio-a” or “town-hall-feed.” Pick something descriptive, but know that all stream names MUST be unique. This is especially important if you’ve got multiple RTMP streaming encoders pushing simultaneous feeds to the HyperCaster as this is how the server will distinguish which stream is which. Make sure to write it down for when you go to configure the encoder. One note here, you can’t use any special characters, with the exception of the “@.” or spaces in the stream names. Letters, numbers, dashes, and underscore are all permissible. The stream and application names are case sensitive.

To add the RTMP feed to the HyperCaster:

  1. Click on Config. Under Feeds click on Live Streams.
  2. Click on the small icon in the bottom-left of the table to add a new stream source
  3. Change the type to RTMP. Enter a name and description of your choosing.
  4. Enter the address address of the RTMP stream.
  5. Optionally enable Stop on Loss of Signal. By selecting this checkbox, any stream/record event created using this feed will automatically end when the source signal is lost. You can set a tolerance, for example to deal with noisy networks or the Internet, to allow some number of seconds of signal loss without considering a loss and time to stop via the Schedule Configuration settings.
  6. Optionally enable Start on Trigger. By selecting this checkbox and Manual Trigger Type from the pulldown, any stream/record event created using this feed will only start after it is manually triggered from the dashboard by clicking the Trigger action button HC Trigger Action Button from the Now Playing / Now Recording sections. For live stream events, the channel will display Continuity while waiting for the trigger.
  7. Click Save.
  8. You can preview the stream within the HyperCaster web interface, if the stream is running, by clicking on the blue link under URI.
  9. The RTMP stream can now be scheduled as you would schedule any other stream in the Programming tab, either Calendar or Classic view. RTMP streams can also be used as sources in Series Scheduling for automatically scheduling reoccurring and episodic events.

Once you’ve configured the HyperCaster you now must configure your RTMP Encoder. Since every encoder is slightly different you may have to refer to the specific manual. Below are two examples from Wirecast and Flash Media Live Encoder (FMLE). Note the URL structure here mirrors the above URL but has two key differences:

1- The Address of the RTMP Source is the address of the HyperCaster
2- The stream name is a separate text entry block. Not all RTMP Encoders do this.

Wirecast here also shows you the fully concatenated URL which mirrors the structure below.

Once the streamer is fired up and running, you’ll see a bitrate appear in the HyperCaster feed configuration page.

RTMP Pull: Since the stream is “ready to pull” all you have to do is configure the HyperCaster to go retrieve that stream and pull it into the system. The example below would mirror the format for how the CloudCast system works using an Akamai style URL.

Once the stream has been added to the HyperCaster it will begin pulling it in, if it’s available. You will see a bitrate listed if the stream is present. Note: the stream is ALWAYS pulling regardless of it’s status on a channel unless it’s “stopped.” This means if you have limited download bandwidth at the station you need to be aware of how many active streams, both push and pull (but especially pull) are active at any given time.

Mux Rate and Streaming in IPTV Plants

The HyperCaster will transmux incoming RTMP feeds to a Transpport Stream with an efficient, variable mux rate. Customers using the RTMP feature in an IPTV plant need to be especially careful of mux rate as the downstream gear in your facility may not handle variable mux rate. Additionally, you need to take extra consideration regarding the matching of elementary stream codecs and resolution. Most RTMP encoders are going to output H.264 and AAC audio at a resolution of your choosing. If this matches the channel you intend to push the stream out on, then you’re in good shape, if not, there could be issues with downstream splicers, groomers, transcoders, stat muxes, and STB’s receiving and transitioning between regular programming and a feed coming from the RTMP encoder as streamed by the HyperCaster. Customers using a TelVue ProVue decoder, or models such as the HyperCaster AIO on the channel that’s outputting the RTMP feed do not need to take this into consideration as the decoder will be able to handle in-stream changes to the bitrate, muxrate, and resolution without issue.

Latency

As is true with any encoded video, there is latency involved with the RTMP receive feature of the HyperCaster. In our testing we’ve found there is between a few and 15 seconds of latency, depending on the encoder and network conditions, between “real time” and “channel delivery.” Latency should be expected and accommodated when scheduling and going live while using the RTMP ingest feature of the Hypercaster. This may mean you schedule the event to start later than it actually does, or you start your live shoot earlier than the actual start time. If you’re not using a direct connection to the Hypercaster (push process), and are instead pulling a stream from a CDN or OPV (Online Video Platform), latency could be considerably greater.

A Bit About the Internet and Video Transport

We’ve talked a bit about video transport across the public internet in the past. Here’s a blog post discussing it a bit more in depth: https://telvue.com/2013/10/28/video_backhaul/.

For the purposes of this document we do however need to discuss a few very important things about live streaming across the internet:

The internet was not really designed for low latency video transport: it’s architecture is extremely complicated and inherently latent. We take a lot of things for granted, as in recent years it has become significantly more viable to move live video across the web, but there are still quality issues that can be encountered. Know that as you’re using this feature, while we’ve done everything we can to ensure the server performs well, there are many, many things outside the control of the HyperCaster that can cause the stream to fail, drop, pixelate, or respond erratically.

If you’re experiencing issues with a link that has worked in the past, and none of the settings in either the HyperCaster or the streaming encoder have been modified from their “known working” configurations, the the problem is very likely the link and NOT the streaming encoder or the HyperCaster. Never forget there are NO guarantees that a stream will be able to transmit across the internet cleanly or with 100% reliability.

As such, we’ve included the ability to restart an individual RTMP stream on the HyperCaster side. We’ve guarded against every error we can, but invariably, when dealing with the complexity of the internet, something’s going to go wrong. As the end user, if a stream is in peril, you can login to the HyperCaster interface, go to the Config → Feeds page and click the “power button” and restart the RTMP stream process. In some cases this may fix the issue you were having, in others it may not have any effect on the RTMP stream. See image below highlighting the “restart” process button.

Tips for “Best Results”

Always test the RTMP streams in advance of use, especially RTMP Push streams. Regardless of “It’s always worked here before” mentality.

Do some comprehensive testing of the encoder before going live for the first time. This will ensure you’ve got the settings tuned for optimal transmission.

Run some speed tests on your local internet connection to verify how much download bandwidth you’ve got available.

Run speed tests on the remote internet connection to ensure the remote location has enough upload bandwidth.

Share This Article :
  • Facebook
  • Twitter
  • LinkedIn
  • Pinterest
Still stuck? How can we help?

How can we help?

Updated on December 1, 2022
Brightcove EPG IntegrationSet Up an RTMP Stream in a HyperCaster

PRODUCTS

  • Playback & Automation
    • HyperCaster®
    • ProVue®
      • ProVue® HD
      • ProVue® GFX
      • ProVue® CC
    • TelVue® TeleCastTM 2
  • Streaming/Cloud
    • TelVue CloudCast™
    • TelVue Connect™
    • Media Exchange
    • Mobile & OTT Apps
    • TelVue SmartCaption™
  • Digital Signage
    • TelVue InfoVue™
  • Automatic Captioning
    • SmartCaption™
  • Ad Insertion
    • AdCaster™

SUPPORT

  • Contact Support
  • Knowledge Base
  • Training Videos
  • Product Documentation

ABOUT

  • Contact Us
  • TelVue News for Hyperlocal Broadcast, PEG news, and TV Technology
  • Press Releases
  • Executive Profiles
  • Sales Team
  • Company
  • Partners

BLOG POSTS

  • FreightWaves Taps HyperCaster AIO for Flexible Ad Integration with Brightcove
  • HyperCaster Integrated Streaming & Social Streaming Automation
  • Live Dual-language Captioning, Multiple Trim Editing, and Multistreaming Automation with HyperCaster™ 8.3
  • AIO Integrated Streaming, Program Guide & Clock Overlays with HyperCaster™ 8.2
  • Channel Streaming Rights Management with HyperCaster™ 8.1
  • Facebook
  • Twitter
16000 Horizon Way, Suite 100, Mt. Laurel, NJ 08054 - TelVue Corporation ® All Rights Reserved 2020