What's new in the Adobe Media Server 5.0.11 release is covered in these release notes. Get to know the release, the fixed issues, and the requirements.

Welcome to the 5.0.11 release of Adobe Media Server. This release includes update to the OpenSSL version to 1.0.2h, update to PHDS and PHLS certificates, and fixes for a few bugs listed below.

Issues fixed

Reference number

Issues fixed


Vanilla Encryption for HLS not working.


HLSPackager causing segmentation fault when trying to execute the tool. Issue is getting surfaced on CentOS 6.6.


Relay application wrong time stamps when MessageCache is set to true.

Ingest drops these data packets because it saves the first timestamp of a new stream and expects all subsequent timestamps be greater than the first. The Ingest sees subsequent calculated timestamps start near 0 and then increment up to the first timestamp. So Ingest drops the packets for approximately the same period of time as the first timestamp value.


Apache crashes on requesting HLS Audio-only fragments from mp4 VoD file with no audio.

Known issues

Reference number

Known issues


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


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.

Minimum system requirements

The minimum requirements to run Adobe Media Server 5 are

Supported operating systems

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

Hardware and network requirements

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

Install Adobe Media Server

To install AMS on Windows or Linux computers, follow the instructions provided at https://helpx.adobe.com/adobe-media-server/install/install-media-server.html.

Uninstall Adobe Media Server

To uninstall AMS, follow the instructions provided at https://helpx.adobe.com/adobe-media-server/install/uninstall-media-server.html.

More resources

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy