Why would I host my own Adobe Media Server vs. using a CDN for premium video streaming?
Streaming from within your network infrastructure is potentially more cost effective. You can control access and delivery channels, plus manage the load on your network with the origin/edge configuration of Adobe Media Server. You can also deploy deep authentication and interactive solutions that content delivery networks (CDNs) do not support. In addition, you can support more advanced media delivery options including multicast and multicast fusion using encrypted RTMFP.
Does Adobe Media Server support IPV6?
Yes, IPV6 has been supported since Flash Media Server version 3 (2008).
Why would I choose Adobe Media Server over clone servers?
- Adobe product compatibility — Get broad desktop support through Flash Player, coupled with very rapid adoption when new versions are released.
- On-demand HTTP Dynamic Streaming — You can package F4F files in real time from existing MP4 or FLV video files, simplifying the workflow for HTTP delivery and eliminating the need for prepackaging content for Flash Player.
- Easy-to-use content protection — More than 20 CDNs worldwide push over 800 petabytes of video data through Adobe Media Server each year.
- Stronger protection — You can protect adaptive bitrate video on-demand and live streams at the same time to Flash Player -- compatible and iOS devices. Add even more digital rights management (DRM) protection with Adobe Access, with consistent support across desktops, devices and select connected TVs.
- More secure multicast, including multicast fusion — You can support higher quality video in your enterprise without impacting your network, now with enhancements such as stream replication, server-side recording and rebroadcast.
- A more robust experience— With applications like Adobe Connect™ and partners like Akamai constantly driving the technology, Adobe Media Server has real-world deployments that are robust and difficult to duplicate.
- Live video — Adobe Flash Media Live Encoder supports H.264 live streaming and DVR functionality. Streaming via clone servers is not supported with Flash Media Live Encoder.
- Peer-assisted networking— You can reduce your bandwidth costs by using Flash Player to help distribute video and data.
- UDP communication— This feature provides lower latency for real-time communication applications.
- Absolute timecode— This feature enables improved synchronisation options.
- SWF file verification — An important part of protected content and communication delivery is to make sure your SWF files are not compromised.
Are CDNs required to support Adobe Media Server?
No. Adobe Media Server can be configured as a remote origin server for HTTP delivery. If you don't want to run your own origin, Adobe is working closely with CDN partners to enable HTTP and RTMP services. Contact individual partners to learn more about their plans.
Does Adobe Media Server support HTML5?
Yes. Adobe Media Server can deliver content to HTML5 on iOS devices using the HLS streaming format. For other browsers supporting HTML5, you can use Adobe Media Server to deliver progressively.
How many servers do I need for HTTP streaming?
On-demand packaging in Adobe Media Server can support the packaging of hundreds of files at the same time. Once a file has been packaged, it will remain in the HTTP cache for the next person. When used with HTTP caching technologies (such as Varnish or SQUID) and CDNs, scalability increases dramatically. If you are streaming only a few files to a large audience, the demand on Adobe Media Server is low. If you are streaming a large number of different files to an audience, the impact on the server increases. For iOS streaming, there is no additional impact on the server capacity. For streaming with encryption, there is an impact on the number of concurrent files that can be packaged.
Do I need a separate licence for Adobe Access to support Protected HTTP Dynamic Streaming?
No. Protected HTTP Dynamic Streaming requires no additional licences.
Is Adobe Media Server scalable?
Yes, Adobe Media Server supports RTMP edge caching configurations. The origin and edge architecture provides the caching services required for large and distributed installations. You can also use both of these editions to split live streams to multiple locations to improve load balancing.
RTMFP applications are now more easily scalable with the new introduction forwarding features that allow multiple servers to be used to manage your P2 P group.
Are Adobe Media Server applications and configurations compatible with Flash Media Server 3, 3.5, 4 or 4.5?
Adobe Media Server has full backward compatibility with versions 3, 3.5, 4 and 4.5. Customised C++ plug-ins that were written for 3 or 3.5 will need to be recompiled for deployment in 64 bit:
- Client-side ActionScript®: You should test your application to help ensure compatibility.
- Server-side ActionScript: Limited changes have been made to the server-side APIs.
- Configuration files: Configuration files have had significant changes. Back up your previous-version configuration files and transfer to version 4.5 configurations.
- RTMP origin/edge: Mixed version 3.x and version 4.5 origin/edge servers are not supported.
Where can I download maintenance upgrades?
Adobe Media Server maintenance upgrades are available on the updates page.
What support options are available for Adobe Media Server?
You can find extensive online documentation and support files for Adobe Media Server on the resources page, along with a wealth of tutorials and sample code in the Adobe Media Server Developer Centre. If you require a higher level of product support, you can enrol in one of Adobe's support programmes.
Where can I find an expert?
Adobe maintains a directory of Adobe Media Server solution providers. Their services range from encoding and publishing to advertising, delivery and consulting. You can also find helpful experts on Adobe Forums for Adobe Media Server and related discussion lists. Or check the list of resources at the bottom of this page.
- The different versions or pieces of content are synchronised (the video timelines must match)
- Audio or other data in each content stream is synchronised with the video data in that stream
- Ensure that the video keyframe interval (keyframe frequency) and frame rate are consistent across the different versions of content. A shorter keyframe interval lets the server switch streams more quickly, which means the client can have a smaller playback buffer.
- Use a consistent audio bitrate.
- Use a consistent audio sample rate as much as possible. For low-end encodings, you can save bandwidth by using mono audio rather than stereo.
Media communication developer
- Video chat applications
- Video messaging applications
- VoIP applications
- Multiplayer games
- Guest books
- Video messaging
- Webcam snapshot sharing
- Stream recording and listing
- Video bug overlays
- Video uploading and sharing
- And much more