There are certain advantages and limitations to each of the three CDN options, depending if you are using Brightcove's CDN, bringing your own provider (BYO CDN), or using remote assets. The Content Delivery Options topic describes these options in detail. Here's a quick chart to help guide you:
|
|
Brightcove CDN
|
BYO CDN
|
Remote Assets
|
|---|---|---|---|
|
content delivery mechanisms
|
PD
Streaming (RTMP with Brightcove TTL) Encrypted streaming (RTMPE) JavaScript SSL for Player Load |
PD
Streaming (RTMP) Akamai TTL Encrypted streaming (RTMPE) (L3 and Akamai only) |
PD
Streaming (RTMP) Akamai TTL Encrypted streaming (RTMPE) (if your CDN supports it) |
|
FTP batch upload
|
|
|
|
|
Media API ingest
|
|
|
|
|
Media module upload
|
|
|
X
|
|
image capture
|
|
Yes, but requires CDN configuration for RTMP
|
Yes for PD only
No for remote RTMP or RTMPE |
|
reporting
|
Bandwidth data for video delivery available in Video and Player reports
|
Bandwidth data and minutes data not available in reports. CDN provider can assist.
|
Bandwidth data and minutes data not available in reports. CDN provider can assist.
|
|
file information
extracted on upload |
|
|
No. Details about the video file (video duration, video codec, etc.) must be specified in the batch manifest. Since Brightcove never receives a copy of the video file, we can not automatically detect these properties.
|
|
content protection
|
Yes, if using streaming delivery option (TTL)
|
Yes, if using RTMPE
|
Yes, if using RTMPE
|
|
CDN relationship
|
Managed by Brightcove. Issues are escalated to Brightcove and managed to resolution.
|
Managed by you
|
Managed by you
|
|
multi-bitrate streaming
|
|
|
Yes, if required information is supplied in the FTP upload process
|