LAST UPDATED: July 17, 2015
NOTE: In some instances these have been reported as working by customers but have not been directly tested by Teradek.
NOTE: In some instances these have been reported as working by customers but have not been directly tested by Teradek.
Teradek encoders which have RTMP support should be capable with any streaming server, Content Delivery Network (CDN) or Streaming Video Platform / Online Video Platform (SVP / OVP) which also accepts RTMP.
These Teradek encoders include the Bond II, Bond Pro, Cube, Cube Pro, Slice, T-RAX, VidiU, VidiU Mini, and VidiU Pro, as well as the Live:Air app for Apple iOS devices.
Streaming Video Platforms
- Amazon CloudFront
- Bambuser
- Brightcove
- Connesta
- DaCast : refer to the DaCast-provided configuration guide for Cube and for VidiU, as well as the tutorial videos on support.teradek.com; for accounts using Akamai as the backend, please see the notes on Akamai further below
- Dailymotion
- Influxis
- NOTE: Influxis offers an additional benefit for Teradek Bond customers: you may broadcast to the professionally-managed Sputnik servers maintained by Influxis instead of having to own/operate an independent Sputnik streaming server!
- justin.tv
- Kaltura
- Livestream
- NOTE: Cube can stream to BOTH the New Livestream service with Producer accounts as well as the Livestream Platform (original) service with Free and Premium level accounts as of firmware version 6.2.0.
- make.tv
- Media Motion Online (requires firmware version 6.0.3)
- Microsoft Azure Media Services
- NeuLion
- Ooyala
- sermon.net
- Streaming Media Hosting
- StreamMonkey
- StreamVu
- TVoop
- Twitch
- Upper Room Technologies
- Ustream : native integration with Ustream is present in firmware 6.2.0, although more generic RTMP support is still available (see this link for configuration guide)
- Vidaroo
- Wowza Streaming Cloud
- YouTube Live (requires firmware version 6.0.3)
- NOTE: if you stop the broadcast to a YouTube Live event, you must create a new event through the YouTube Live control panel. The stream information should remain unchanged if you've configured YouTube Live with a pre-set for the encoder. Consult YouTube Live's online documentation for the most current information.
- Zencoder
Traditional CDNs
- Akamai Technologies
- NOTE:
- on the RTMP stream settings configuration you must change the User Agent from Teradek to FMLE; if this option isn't shown on the web page, click the Show Advanced Settings button at bottom right
- you must enter the Username and Password for your Akamai account in the appropriate fields
- the Compression Profile needs to changed from the default High profile to Main or Baseline. This option is changed on the Video Setup -> Encoder Settings page; if this option isn't shown on the page, click the Show Advanced Settings button at bottom right. (does not apply to VidiU)
- alternatively, items (1) and (3) above can be skipped if you've selected the Akamai for the Backend Service option on the RTMP stream settings configuration
- BitGravity
- CAUTION: many customers have reported to Teradek that both Cube and Bond are able to stream successfully to BitGravity's service. However, BitGravity has indicated they will not support Teradek products as an encoder for their streaming services. Teradek customers are advised to use other CDNs or SVPs on this list (or any others which accept the standards-compliant RTMP feed generated by Teradek products) to ensure they have full support from their service provider.
- EdgeCast Networks
- Highwinds Network Group
- Level 3 Communications
- Limelight Networks
- NOTE:
- you must manually add "/_definst_" to the end of the Server URL in Cube's RTMP configuration (aka Entry Point shown in the Limelight account settings); for example if your account shows the Entry Point as "rtmp://fmspush.lga.llnw.net/llnw1337", enter "rtmp://fmspush.lga.llnw.net/llnw1337/_definst_" into Cube's RTMP configuration
- the bitrate defined on the Encoder must match what you've configured in the Limelight Networks control panel so that their system can recognize the incoming stream
- the bitrate being sent from the Encoder should be present in the stream name; for example, if 3 bitrates are configured in the Limelight control panel of 500, 750, and 1000 kbps, then the Encoder Stream names used on 3 separate Teradek Encoders should include those bitrates, similar to that shown below:
stream1_500?llnw-live-event=stream1
stream1_750?llnw-live-event=stream1
stream1_1000?llnw-live-event=stream1 - the key frame interval specified on the Encoder must match what has been specified in the Limelight Networks control panel; their default value is one key frame every four seconds, so adjust the Encoder and/or control panel setting as necessary
- it is suggested that you select Limelight for the Backend Service option on the RTMP stream settings configuration
- MaxCDN (NetDNA)
- Voxel (Internap)
Comments
0 comments
Please sign in to leave a comment.