App Cloud
- Overview and general topics
- Product Updates
- Glossary
- The App Cloud SDK
- Creating an app template
- Tutorials
- Content optimization
- Development tips and best practices
- Packaging a template
- Creating apps from a template
- Publishing an app
- Delivering ads
- Push Notifications
- Analytics
- Managing users and accounts
Player Debugger
Resources
Encoding for Mobile Delivery
This topic discusses how to choose the best transcode settings for delivery to mobile devices.
Because customized transcode settings are available only to Video Cloud Pro and Enterprise publishers, this information is not relevant for Video Cloud Express publishers.
Codecs and containers for mobile devices
Different mobile devices support different codecs and containers for video. Here's a summary:
Android OS devices
Flash Player 10.1 is supported on devices that run Android OS 2.2 and up, and therefore videos in the FLV container will play back on those Android devices. However, for greatest flexibility and quality, you are better off using the H.264 codec and MP4 container.
Apple iOS devices
Apple iOS devices (iPhone, iPad, iPod Touch) do not support Flash or the FLV container. To deliver your video to an Apple iOS device, you need to make sure your video:
- uses the H.264 codec
- uses either the MP4 container (for HTTP delivery) or the M2TS container (for Apple HTTP Live Streaming)
For iOS devices, the player uses an Apple HTTP Live Streaming rendition if available, and otherwise plays an MP4 rendition.
For more details on Apple's recommendations, see this document.
Content delivery options for mobile video
Apple iOS devices like the iPad, iPhone, and iPod Touch support only Apple HTTP Live Streaming and HTTP (progressive download) for delivery of video files FMS-based RTMP streams are not supported. That means that you need to ensure either that your videos have one or more available renditions that work with Apple HTTP Live Streaming, or that your account is set up to permit HTTP based delivery. Read about Setting Video Delivery Options.
Using Apple HTTP Live Streaming
Video Cloud supports video delivery to Apple iOS devices using Apple HTTP Live Streaming. To use this method for video delivery, a video must have one or more available renditions that use the M2TS container. The iTunes App Store rules call for the use of Apple HTTP Live Streaming for long form video content (greater than 5 Mb or 10 minutes). For more infomation, see Delivering Videos with Apple HTTP Live Streaming.
Enabling HTTP (progressive download) delivery
Your Video Cloud account is usually configured for progressive download (PD) (HTTP), streaming (FMS) (RTMP) based delivery, or universal delivery service (UDS), which enables either PD or FMS delivery. To check that your account is configured for UDS:
- In the Video Cloud Studio, go to Account Settings > Publishing Settings.
- Under Universal Delivery Service, see if it shows Universal Delivery Service: Enabled. If not, click Edit to enable it.
To check what delivery mechanism a particular file is using:
- In the Media module, select a video and click Edit.
- In the Video Files tab of the Edit Video dialog, check the Delivery Type of your renditions. If the Delivery Type is Progressive Download, the rendition can be delivered by progressive download (HTTP).
Encoding recommendations for maximum flexibility
If you are like most publishers, you won't want to restrict themselves to just one type of video delivery or just one type of device. You'll want your videos to be available and to look good on every device your viewers might choose desktop computers, mobile phones and tablets, and TV sets. Using Video Cloud's multiple renditions feature, you can create enough renditions of each of your videos so that there are available renditions optimized for each device and situation.
In addition to making sure you use a supported codec, you will want to deliver the videos at an encoding rate that can be expected to play back reasonably well on a mobile device. You need to find a balance that will not take too long to buffer while still delivering a high quality viewing experience.
The encoding settings in the following table provide a broad range, but are just suggestions. The exact settings you choose can depend on the quality of your source files, the nature of the video content, and the ways your viewers consume your content.
Note: The first entry in your Multiple Renditions settings is the Primary Rendition, the first one to be generated in the transcoding process. This should not be an iOS rendition (using the M2TS container), as this will delay the availability of your videos for general playback on other platforms.
| Quality | Codec Profile, Container |
Video Bitrate (kbps) |
Audio Bitrate (kbps) |
Dimension (WxH)1 | Frame Rate |
Bitrate Type |
Description |
|---|---|---|---|---|---|---|---|
| Good quality | H264_MAIN, MP4 |
800 | 96 | 640x360 640x480 |
Source | VBR | |
| Cell fallback for audio only | H264_BASE, M2TS | 962 | 40 | 50x502 | Source | CBR | For iOS devices: iPhone, iPod Touch, and iPad. iPads with lower bandwidth will stretch lower resolution videos to fit the device dimensions; iPhones with higher bandwith will concentrate any higher resolutions videos to fit device dimensions. |
| Low quality | H264_BASE, M2TS3 | 110 | 40 | 400x224 400x300 |
Source | CBR | |
| Medium quality | H264_BASE, M2TS3 | 200 | 40 | 400x224 400x300 |
Source | CBR | |
| Higher quality & resolution | H264_BASE, M2TS3 | 400 | 40 | 640x360 640x480 |
Source | CBR | |
| Average quality | H264_MAIN, MP4 |
150 | 64 | 400x224 400x300 |
Source | CBR | For non-iOS mobile devices |
| Low quality | H264_MAIN, MP4 |
300 | 64 | 480x270 480x360 |
Source | VBR | For desktop machines and non-iOS tablets and devices |
| Average quality | H264_MAIN, MP4 |
512 | 80 | 480x270 480x360 |
Source | VBR | |
| Very good quality | H264_HIGH, MP4 |
1100 | 128 | 720x405 720x540 |
Source | VBR | |
| High quality | H264_HIGH, MP4 |
1672 | 128 | 1280x720 1280x960 |
Source | VBR |
1. The dimensions are given for both 16:9 and 4:3 aspect ratios. For more information about the relationship between the source file dimensions and the transcode settings dimensions, see Width and Height in Setting Your Transcoding Options.
2. Note that an audio-only rendition will not really have a video bitrate or dimensions, but the Video Cloud Studio does not permit you to set values lower than these. The video bitrate and dimension settings will be ignored for an audio-only rendition.
3. When setting renditions for iOS devices, be sure to use the BASE codec container setting, not the MAIN or HIGH settings or the player will report a "This movie cannot be played" error.
We recommend a keyframe rate of 2 in most applications, and two-pass transcoding for all but audio-only renditions.
Uploading video for mobile delivery
When you upload a video, the settings you choose for the upload can override the transcode settings you chose for your account. Therefore, it's important when you upload a video to make sure your upload settings are consistent with your transcode settings. Let's review how to upload a video in the Media module:
- Click the Upload Videos button in the Media module.
- Browse and select one or more videos to upload from your local hard drive.
Note the Edit Settings link toward the bottom of the Upload dialog.
- Click the Edit Settings link. For mobile delivery, make sure you have selected H.264 (MP4) for your output options. Your H.264 (MP4) renditions will be created only if this output option is selected. Regardless of what you select, if your account's transcode settings include one or more renditions with the M2TS container, those renditions will be created.
Related information
- Setting Your Transcoding Options
- Delivering Videos with Apple HTTP Live Streaming
- Standard Transcode Settings Reference
- Delivering Video with HTML5 and Smart Players
