What's New in Adobe Media Server

Adobe Media Server version 5.0.10 offers the followings enhancement:

• A month before a DRM certificate expires, the server generates a relevant message in the Apache error logs and on the console. The message is generated only when content is requested by a client and the frequency of this message is only once per hour.
• OpenSSL is updated to version 1.0.2d.

For more information about the release, see the 5.0.10 release notes at www.adobe.com/go/ams_release_notes.

Adobe Media Server version 5.0.9 offers the followings primary features, besides some bug fixes:

• OpenSSL is now updated to version 1.0.2a
• Some enhancements in logging and bug fixes.

For more information about the release, see the 5.0.9 release notes at www.adobe.com/go/ams_release_notes.

Adobe Media Server version 5.0.8 offers the followings primary features, besides some bug fixes:

• The bundled Apache Server has been upgraded to version 2.4.
• Support for Windows Server 2012 R2 (64 bit), CentOS Linux 6.6 (64 bit), and Red Hat® Enterprise Linux 6.6 (64 bit) is added.

For more information about the release, see the 5.0.8 release notes at www.adobe.com/go/ams_release_notes.

Adobe Media Server version 5.0.7 offers the followings new features:

• Support for WebVTT captions in HLS streams

• Timed metadata in RTMP streams available in output HLS streams as ID3 tags

• Update for certificates for the protected streaming workflows (PHDS, PHLS, and PRTMP)

• Bundled Strobe Media Player (SMP)

• Fixes for security vulnerabilities, including Shell Shock and POODLE vulnerabilities

For more information about the release, see the release notes at www.adobe.com/go/ams_release_notes.

The following updates were available with 5.0.6 release of AMS:

• Bundled OpenSSL version has been updated to openssl-1.0.1h.

• Fix for segmentation fault during application reload attempt if the stream has closed captions enabled.

For more information about the release, see the release notes at www.adobe.com/go/ams_release_notes.

AMS 5.0.5 release offered multiple bug fixes that are available in the release notes at www.adobe.com/go/ams_release_notes.

• Protected RTMP onDemand Enhancements

  • Logging improvement for billing: The Adobe Media Server access log supports an additional column "x-sprotection-ver." This is logged with the application and stream events with value "1" if the stream is protected (PRTMP enabled).

  • Integration of common key and white-list access with file-plugin interface: The common key and white-list access in the Protected RTMP on-demand workflow is routed through file adaptor if configured for handling "PRTMP" requests. Following configuration is added to server.xml:

    Root/Server/Plugins/FilePlugin: <!-- This section configures PRTMP common key and file --> <!-- whitelist file operations in present plugin. By --> <!-- default such operations won't be managed by this --> <!-- plugin. --> <Content type="PRTMP">false</Content>

  • DRM refresh: The DRM refresh is needed if there is a change in swf whitelist on runtime or update of common-key. New DRM will be in effect as soon as new clients subscribe in the following scenarios:

    • new whitelist hashes are provided through the auth adaptor or

    • whitelist folder modification time is changed

     

    This is independent of whether the update interval is configured or not. If only the exiting whitelist file is modified and the swf folder modified time is not updated, the new DRM is in effect from the next update interval onwards.

    The existing streams will play with the old DRM.

    You can update F_APP_PRTMP_SWF_WHITELIST or F_APP_PRTMP_AIR_WHITELIST at the time of connect. This updates the swf whitelist for whole application.

   

• Common-key update: Common key can be updated in the same location. The Origin Server flushes the cache and reloads the data.

• Key rotation: You can rotate the key for protected RTMP live playback. You can periodically change the encryption key by specifying the frequency of content encryption key change. Rotated keys are generated dynamically using the common key and content id.

  Added configuration:

  <EnableKeyRotation>true</EnableKeyRotation> <KeyRotationInterval>500</KeyRotationInterval> // in seconds

  Added configuration in Application.xml.

  <Application> <ProtectedRTMP enabled="true"></ProtectedRTMP> <EnableKeyRotation>true</EnableKeyRotation> <KeyRotationInterval>500</KeyRotationInterval> ... </Application>

Closed captioning allows the content provider to display text overlayed on the video content thus providing additional information about the video content to the consumers. Closed captioning is primarily used as an accessibilty tool to show a transcription of the audio portion of the video content as it occurs. The term “closed” in closed captioning indicates that the captions are not made part of the video by default. Hence, the captions have to be decoded/extracted by an external tool. For more information on configuring the server to support closed captions, see Configure closed captioning.

Adobe Media Server 5.0.1 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, called as “late” binding of audio tracks allow 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. For more information on configuring the server to support alternate audio, see Configure alternate audio.

Adobe Media Server 5.0.1 has introduced a few important branding and configuration-level changes. See the following changes: