Cisco Cisco AnyRes VOD Server Leaflet
© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
Page 1 of 5
Data Sheet
Cisco AnyRes Video on Demand Post-Encode
Node
Node
Product Overview
Cisco
®
AnyRes Video on Demand (VoD) helps expand the revenue potential of video content for service providers,
media distributors, and content providers by generating high-quality VoD assets that are compatible with any
device. By eliminating the manual bottlenecks typically involved with high-volume, file-based transcoding workflow,
which prepares video files for set-top boxes, PCs, and mobile devices, Cisco AnyRes VoD helps lower operating
expenses (OpEx). It also produces high-quality assets for every screen with exceptional performance, maximizing
advertising opportunities without compromising the viewing experience.
Post-Encode Node Summary
Within the Cisco AnyRes VoD product suite, the post-encode node performs the following functions:
●
Transwrapping video files into any, or all, of the popular adaptive bit rate (ABR) formats
●
Packaging Adaptive Transport Stream (ATS) assets into a Common Index Format (CIF) to support unique
functions on the Cisco Videoscape
™
Distribution Suite Origin Server (VDS-OS)
●
Checking files for quality
●
Delivering media assets
The post-encode node license is optional for the Cisco AnyRes VoD, but it is required for the tasks listed in the
summary.
Cisco AnyRes VoD streamlines the steps required to target multiple formats. When preparing video for ABR
delivery, one source file is typically encoded into five to ten separate files, in addition to their corresponding
metadata files. Popular examples of HTTP-based ABR formats include Apple HTTP Live Streaming (HLS), Adobe
HTTP Dynamic Streaming (HDS), Microsoft HTTP Smooth Streaming (HSS), and MPEG Dynamic Adaptive
Streaming over HTTP (MPEG-DASH). The ABR formats you choose depend on the devices you are targeting and
the limitations of your transcoding software and hardware. The number of layers, or streams, required in each
ABR format is a choice that is based partly on source resolution and network limitations. It is also based on a
business decision to balance storage costs and the end user's quality of experience (QoE).
For example, you might want to deliver a 30-minute, high-definition video file to Apple devices using Apple HLS,
as well as to personal computers using Adobe HDS. You might also consider Smooth Streaming for Microsoft’s
Xbox. In the conventional method, an encoder would output ten different profiles for each ABR format, for a total of
30 different encodes. These would be spread out across multiple encoding servers. This is CPU intensive, costly,
and in many ways redundant because your target compression profiles are so similar across formats.