Adobe Media Server Release Notes

Adobe Media Server 5.0.1 Release Notes

Welcome to the Adobe® Media Server 5.0.1 release! Adobe Media Server completes ten years as a leading Video Streaming product this year.This release contains support for streaming Closed Captions as per FCC guidelines and Adobe Access DRM protection for HLS Streaming. It also includes Branding updates that reflects Adobe Media Server's streaming capabilities to both flash and non flash devices.The product comes bundled with Adobe Media Gateway that connects SIP based telephony devices with Flash based web and desktop applications.

We have also simplified the upgrades pricing for you to update from your older versions.

Minimum system requirements

The Adobe Media Server 5 system requirements are:

Supported operating systems

  • Microsoft® Windows Server® 2008 R2 64 bit
  • Linux CentOS 5.8 64 bit
  • Red Hat® Enterprise Linux® Server 5.5 64 bit
  • Windows 7 64bit (for Adobe Media Server Starter only)

Hardware requirements

  • 3.2GHz Intel® Pentium® 4 processor (dual Intel Xeon® or faster recommended)
  • 64-bit operating systems: 4GB of RAM (8GB recommended)
  • 1Gb Ethernet card recommended (multiple network cards and 10Gb also supported)

What's new in this release

Adobe Media Server is available in following configurations

  • Adobe Media Server Starter (formerly Adobe Flash Media Development Server)
  • Adobe Media Server Standard (formerly Adobe Flash Media Streaming Server)
  • Adobe Media Server Professional (formerly Adobe Flash Media Interactive Server)
  • Adobe Media Server Extended (formerly Adobe Flash Media Enterprise Server)
  • Adobe Media Gateway is a bundled software available with your license

Closed Captioning

Adobe Media Server now supports delivery of caption data embedded in video stream using the following supported streaming techniques:

  • HLS (Live and VOD)
  • HDS (Live and VOD)
  • RTMP (Live and VOD)

Closed captioning in AMS is implemented by repackaging the embedded caption data within the H264 SEI NALU as specified in ANSI/SCTE 128 2010 Section 8 into data messages for HDS and RTMP. No such repackaging is required for HLS. Adobe Media Server supports industry standard 608/708 closed captioning for video streaming to the following output channels/devices:

  • Adobe Flash Player (through the OSMF framework)
  • iOS devices (through HLS)

Alternate Audio

Adobe Media Server has support for including multiple language tracks for HTTP video streams, without requiring duplication and repackaging of the video for each audio track. This feature, referred as alternate audio, allows content providers to easily provide multiple language tracks for a given video asset, at any time before or after the asset’s initial packaging. The initial packaging of the video asset can include an audio track, and the publisher can still choose to provide one or more additional audio tracks for the video. Video players can provide support for allowing the viewers to switch between audio tracks either before or during playback.

New Content Protection options for HLS streaming to native Apple iOS applications

Content protection and Digital Rights Management (DRM) workflows for streaming to both Flash using HTTP Dynamic Streaming (HDS) and native Apple IOS applications using HTTP Live Streaming (HLS) are now supported. With this feature, Adobe Media Server can dynamically segment, encrypt, and deliver standard MP4 assets using the HLS format with Adobe Access DRM policies on native Apple IOS applications (using the Adobe Access Objective C library for Apple IOS). For more details on this feature, please refer to the online documentation.

Adobe Media Server also supports content protection of HLS video streams using Adobe Access protection without requiring a separate license server. This functionality (PHLS) already available for HDS format (PHDS) enables ultimate scalability and cost management. Details on PHLS and PHDS features are available as part of Adobe Media Server online documentation.

Just in Time content protection enhancements

Adobe Media Server enables real time packaging and encryption of your media for HTTP delivery to both Adobe Flash and Apple HLS file formats. This means that your single live source publishing need not be duplicated to serve Adobe Flash and Apple HLS formats, which significantly reduces your storage and stream management requirements. Using dynamic and real time encryption, Adobe Media Server 5 can prepare and encrypt a single live source of F4F recording and deliver the encrypted segments over HTTP to both HDS (Flash) and HLS (Apple iOS).

HLS Offline Segmenter

A new HLS offline segmenter utility (now available under \tools folder as 'hlspackager') converts MP4 video files into the HLS file format and M3u8 manifest for http streaming to devices that support HLS such as the Apple iPad. When used with Adobe Access, the HLS packager can encrypt the HLS file for playback in native IOS applications using the Adobe Access iOS client SDK.

Important Changes in this release

Adobe Media Server 5 has introduced a few important branding and configuration-level changes. We recommend all users to go through below list of changes and prepare their environment accordingly.

  • Executable name changes

    Below is list of executable which has undergone name changes
    • Linux
      • fmsmaster is renamed to amsmaster
      • fmsadmin is renamed to amsadmin
      • fmscore is renamed to amscore
      • fmsedge is renamed to amsedge
    • Windows
      • FMSMaster.exe is renamed to AMSMaster.exe
      • FMSAdmin.exe is renamed to AMSAdmin.exe
      • FMSCore.exe is renamed to AMSCore.exe
      • FMSEdge.exe is renamed to AMSEdge.exe
  • Installer Scripts name changes

    Below is list of Installer Scripts which has undergone name changes
    • fmsmgr is renamed to amsmgr
    • installFMS is renamed to installAMS
    • uninstallFMS is renamed to uninstallAMS
  • Tools name changes

    Below is list of Tools which has undergone name changes
    • fmscheck is renamed to amscheck
    • fms_adminConsole.swf is renamed to ams_adminConsole.swf
  • Service name changes

    Below is list of services which has undergone name changes
    • Linux
      • fmsadmin is renamed to amsadmin
      • fms is renamed to amsadmin
    • Windows
      • FMSAdmin is renamed to AMSAdmin
      • FMS is renamed to AMS
      • FMSHttpd is renamed to AMSHttpd
  • Configuration files name changes
    • fms.ini is now renamed to ams.ini
  • Other important changes
    • Default installed directory on Linux is now /opt/adobe/ams
    • Default installed directory on Windows is now “C:\Program Files\Adobe\Adobe Media Server 5”
    • Default User name is changed from “fms” to “ams” (Linux only)
    • Registered Services reference location on Linux is changed from “/etc/adobe/fms/services” to “/etc/adobe/ams/services”
    • Some of the Content Protection Configurations for HDS and HLS have undergone name changes. Details can be found here

Issues fixed in this release


Any request for non-existent f4m and f4f used to result wrong HTTP Response code of 403.Now proper error response of 404 is sent for requests for non-existent f4m and f4f.


Prior to 5.0.1, user could not install FMS without being root user. AMS 5.0.1 allows non-root users to install FMS on Linux. However, there are certain preconditions which must be completed by the machine administrator for allowing the non-root users to install AMS on that machine. These conditions have been compiled inside a separate script file.


Added License file support for Adobe Media Gateway. Now users can use their trial license files of AMS for AMG by placing them in “licenses” folder of AMG.


Earlier in case you had the same base-names for a media file and a set-level manifest file (for eg., sample.mp4 and sample.mp4.f4m) and a request for sample.mp4.f4m is made via hds-vod module, we used to incorrectly serve set-level manifest. Now we correctly the media file.To avoid this confusion it is recommended to have different base-names for media files and set-level manifest files. Additionally, the modified time of the media file maybe cached. If later you choose to remove the media file (with the same base-name as the set-level manifest file), further requests will not serve set-level manifest file, unless the modified time of the set-level manifest file is more than that of the media file. Users will have to ensure clean/reset caches in such cases.


When one or more of certificates used for Adobe Access configuration are invalid, Apache used to log generic errors that did not give much information. For expired certificates, it used throw the error "Unknown exception when processing " is logged and for corrupt certificates, the error message was "SDK failed to generate drmmeta".We now log proper indicative messages in error log of Apache


In case of incorrect configuration of KeyRotationPath or usage of invalid keys for KeyRotation, there was no appropriate logging in Apache Error logs. We now log indicative error/warning messages in Error log of Apache to help user identify wrong configurations made.


Whenever any request was made for VOD media via HDS-JIT module and if jit.conf was empty or malformed it used to result in Apache crash. We now handle such request reliably returning proper error response without any crash.


We improved the code added in previous releases for handling HDS and HLS failover to enhance CPU performance.


In case of login attempt with incorrect credentials, Admin server was encountering performance issues. We have now fixed the same and Admin server no more will encounter any performance hit in case of wrong login attempts.


In restart of publish scenario, we now check the segment number of the first fragment after append, and if it is different from the last segment before restart, we push the first fragment after restart into the correct segment. All the skips from the last fragment before restart to the current fragment after restart are added to the new segment.


Due to an Apple bug, whenever an iOS client used to subscribe to a stream and encounter rollover at server end during a 24x7 Live Streaming workflow, iOS Player used to stop playback. We have now added EXT-X-DISCONTINUITY tag in playlist to work around this situation.

For Issues fixed in AMS 5 and previous 4.x.y releases – please refer “Issues fixed” section of older release notes at - Release Notes on

Known Issues

The following are known issues in this release:


For certain files you may observe audio-video sync issue during seeking on iOS 5.0.1 client when TS duration is configured below 8 seconds.


When audio only stream is used for PHDS, there may be no audio playback for the first few seconds of the media. This is Flash Player issue tracked as Bug 3307392


While enabling the caption generation from the configuration, please make sure your content doesn't captions in multiple forms. For example, both as ATSC Nalu Data and as onCaptionInfo messages. If captions are present in multiple forms, this config may generate additional onCaptionInfo messages that can interfere with original onCaptionInfo messages.


HLS Failover - In case there are fragment discontinuities (which may happen if key-frames are not found at fragment boundaries resulting into fragments bigger than one fragment duration) then the healthy packager may return a 503 after failover resulting in playback stall


HLS Failover - If recording is not yet started on one packager, requests for TS URLs directed to this packager won’t failover (the packager would return a 400 instead of a 503)


Letting RTMPT traffic proxying through Apache reduces the quality of service for RTMPT connections.


As of 4.5.2 release, RTMPT can be tunneled through Apache listening on port 80. This is to allow both RTMPT as well as HDS to work over port 80. As a result, it means that RTMP[e] connections on port 80 would fail to connect. This may affect Edge/Origin environments where clients connect to the Edge server over RTMPT on port 80. The Edge server would try to connect to the Origin on the same port. However, the protocol between Edge and Origin is RTMP (or RTMPS), and hence would fail to connect.

To avoid this, you could do one of the following:

1. Configure the Origin to have FMS listen on 80; this means that you cannot run both RTMPT and HDS over port 80.

2. Configure <RouteEntry>*:80;*:1935</RouteEntry> in the Edge server’s Vhost.xml to remap connections to 80, to 1935 instead.

3. Rewrite the Edge client connection url to replace port 80 with 1935 so that the Edge will attempt to use 1935 instead of the port the client connected on.


When doing HDS and HLS live streaming, if audio or video is received after the first fragment has been created can lead to a "Track not found" error that results in a recording error. To ensure this does not happen, audio and video should start at the same time.


In an n-tier deployment where multiple live streams with different bitrates are being multi-point published from the ingest node to a downstream node, (and synchronized keyframes as required for seamless switching when dynamic streaming), if the streams are being recorded at the downstream node with the intention of utilizing them as DVR streams, the value of "AssumeAbsoluteTime" configuration in application.xml should be set to "true" for the application at the downstream node where the recording is taking place.


Authorization and Access plugins may result in compilation warnings. These warnings are harmless. Removing the warnings now, would require an interface change, and will break plugins built using the current interface. To maintain compatibility we have decided not to fix these warnings at this time. This will allow users to use their existing plugins without having to rebuild and retest.


When enabling stream logging via the admin commands logLiveStream and logNetStream, the log directory is always created in the default log directory under the FMS installation directory, regardless of what configured in fms.ini and Logger.xml


The File Plugin API getAttributes() may be called before the E_FILENAME_TRANSFORM event has been processed. As a result, the wrong file attributes may be returned.


sc-stream-bytes measures the bytes per stream sent from server to client for a particular client. Note that when compared with sc-bytes, which measures all bytes sent from server to client for a particular client, users may notice a discrepancy. There are a number of situations that could trigger this discrepancy, but users are advised to take note of this if trying to use sc-stream-bytes for billing purposes. Billing should be done based on sc-bytes when possible.


Very low frame rate H.264 videos may take a long time to start if the buffer is set too short.


The OnImageData event within H264 streams is not supported.

Install your software

To install Adobe Media Server on Windows:

  1. Log on to the server as an administrator.
  2. Double-click the installation file, AdobeMediaServer_5_LS1_win64.exe, and follow the prompts in the installation wizard.
    This file is on your installation DVD or you can download it from
  3. Read and accept the License Agreement to continue the installation process.
  4. If an existing Adobe Media Server installation is found, choose whether to remove the old version and upgrade to the new version or remove the old version only.
  5. Enter a serial number.
    If you don't enter a serial number, Adobe Media Server Starter gets installed. You can enter a serial number or a license file after you install the server.
  6. Accept the default installation location or enter a new location.
  7. Select whether to install Adobe Media Server and Apache HTTP Server (Full installation), or just Adobe Media Server (Compact installation).
    Note: To use Adobe® HTTP Dynamic Streaming and Apple® HTTP Live Streaming, you must install Apache HTTP Server from the Adobe Media Server installer.
  8. Accept the default location for the Adobe Media Server program shortcuts or enter a new location.
  9. Enter a user name and password for the first valid server administrator. These values are written to the ams.ini file which is located inside of the conf folder after the installation
    After installation, use the Administration Console to reset the password and add other administrators if required.
  10. Accept the default server ports. Alternatively, if desired, enter new values.
  11. Review your installation choices. Click Back to make any necessary changes.
  12. Click Install.
    Note: Microsoft Visual C++ 2005 Redistributable Package and Microsoft Visual C++ 2008 Redistributable Package also install.
  13. Select any final options and click Finish. The installation is complete. By default, Adobe Media Server installs to C:\Program Files\Adobe\Adobe Media Server 5
  14. If you have an Adobe Media Server 5 license (LIC) file, place it in the rootinstall/licenses folder.
  15. Verify your installation.

To install Adobe Media Server on Linux:

  1. Log in as a root user (required to install Adobe Media Server).
  2. Open a shell window and switch to the directory with the installation file, AdobeMediaServer_5_LS1_linux64.tar.gz
  3. Unzip and untar the installation file. A directory with the installation program is created.
  4. Switch to the directory that was just unzipped.
  5. Start the installation program with the following command: ./installAMS
  6. The installation program starts and displays a welcome message.
  7. Press Enter to start the installation. Follow the installation instructions on your screen. During the process you will be asked to
  8. Enter a serial number. If you don't enter a serial number, Adobe Media Starter Server installs.
  9. Enter the installation directory and ports which the server will use
  10. Enter an administrative user name and password for the first valid server administrator. These values are written to the ams.ini file which is located inside of the conf folder after the installation.
  11. Enter a user for Adobe Media Server processes to run as. The default is the "ams" user. (The user you select is also the owner of the Adobe Media Server files.) Your choices are written to the ams.ini file. You can edit the ams.ini file to modify this and other security properties later, if needed.
  12. Review the summary of the installation options you have chosen, which are displayed in the installer.
  13. To start the server manually, go to the installation directory (default is /opt/adobe/ams/). Use the command ".amsmgr server ams start" to start Adobe Media Server and "./amsmgr adminserver start" to start Adobe Media Administration Server.
  14. The installation is complete. If you configured it to start automatically, the Adobe Media Server service starts.

Uninstall your software

To uninstall Adobe Media Server from a Windows computer:

Uninstalling the server on Windows removes all files installed by the Adobe Media Server installer unless the files were modified. Any folders and files that you added or modified after installation are not removed. The configuration files and Apache configuration files are backed up, and the log files are not deleted.

  1. Back up existing data
  2. Do one of the following:
    • Select Start > Programs > Adobe > Adobe Media Server 5 > Uninstall Adobe Media Server 5
    • Choose Start > Control Panel > Uninstall a program, select the version of Adobe Media Server you want to remove and click Uninstall.
  3. In the confirmation dialog box, click Yes.
    Adobe Media Server is removed from your computer. A second confirmation dialog box appears when the process is complete.

To uninstall Adobe Media Server from a Linux computer:

  1. Log on to the server where Adobe Media Server was installed.
  2. Switch to the root user, or a user with root permissions. Normally you would use su - root to switch to the root user.
  3. At the UNIX shell prompt, enter cd /opt/adobe/ams.
  4. By default, /opt/adobe/ams is the directory where Adobe Media Server is installed. If you installed the server in a different directory, replace /opt/adobe/ams with the actual installation location.
  5. Execute the uninstall script ./uninstallAMS.
  6. Follow the displayed uninstall instructions.

Other resources

Adobe Media Server Product Home

Adobe Media Server Documentation Center

Adobe Media Server End User License Agreement

Adobe Media Server Online Forums

Adobe Media Server User Group

Flash Media Encoding Providers

Copyright © 2012 Adobe Systems Incorporated.