Accessibility
Adobe
Sign in Privacy My Adobe

Flash Media Server Release Notes

Adobe® Flash® Media Server 4.5.5

Welcome to the Flash® Media Server 4.5.5 release! This hotfix release addresses RTMFP related security issue by introducing new handshake protocol. Now only parties having the original plain groupsec can join the group or decode IP multicast packets making the RTMFP Groups feature more secure. This release now also allows for configuring aggregate messages by specifying message duration. For complete list of issues fixed and description, please refer to issues fixed in this release section.

Issues fixed in this release

3317019

Client IP address is logged in edge.xx.log file in case of RTMFP connections to non-existing applications. This information can be used to block spurious clients from sending data to server.

3319112,

3327681

Server now supports creating aggregate messages by specifying duration of the message. MaxAggMsgDuration tag has been added for Live playback and VOD playback of FLV, MP4 and raw formats through origin and edge server. Please check updated online documentation for details.

3344924

Fixed internal error 1026 sometimes reported in Apache logs when processing HLS Segments for a live stream under heavy load.

3328321

RTMFP Group handshake is more robust now with introduction of new server channel and p2p handshake protocol. Set GroupSpecifier.minGroupspecVersion property to 2 in order to use the new handshake mechanism. Please check updated online documentation for details.

3347642

Fixed crash in Apache HLS module when playing malformed mp4 files for which key frames cannot be generated due to missing sync sample box in video track. Now an error code 400 is returned and the error is logged.

3363360

FMSCheck tool crashes on Linux platform when publishing to server. This happens due to heap corruption when launching the publisher thread in the tool.

3362251

Admin API call over http protocol with incorrect credentials may increase handles and memory usage.

3334179

Data corruption in FMSMaster monitor data structure with active registry core. ProcessMonitors under certain circumstances could remove the wrong PID information while reaping the registry core process.

3341386

Linux server now allows cleanup of temporary files without stopping the server. A new script 'cleanup' has been added that can be executed at regular intervals to remove temporary files including proxy files on edge servers.

3222699

Fixed failed HDS recording errors when recording is delayed by duration more than the fragment duration specified in the configuration.

3366410

unary operator expected” warning fixed in installFMS script for Linux when apache service is not installed.

Known Issues

The following are known issues in this release:

3142085

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)

3146582

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

2945043

Non-English URL's are not currently supported

2944919

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.

2929657

Flash Media Server 4.0 inverted the order of delivering NetStream.Unpublish.Success and Connection.Closed messages where now Connection.Closed appears second. This can lead to compatibility issues with previous server script applications.

2910985

When the disk load is high you may see “Failed to swap” warnings in the logs which appear to be a nuance of the Windows file system. This may result in a stale file being returned, but is otherwise harmless, and the HDS Live recording should be unaffected.

2908308

MP4/F4V files that have a negative ctts offset may not play properly via HLS and may exhibit artifacts during playback.

2905444

Changing encoder configurations and appending to an existing recording will result in playback problems. A recording is assumed to be a particular audio/video configuration, and changing it mid stream is unsupported.

2885338

Requests for HLS encryption key from iPad 1(3.2.2) over HTTPS will result in a client authentication failure during the SSL handshake.

2873583

Apple’s MediaStreamValidator tool does not support validating encrypted media. So, validating an HLS encrypted ts file will report errors.

2873133

Calling NetStream.send() immediately after receiving NetStream.Publish.Start status message may intermittently fail due to a race condition when initializing the Stream object in server-side ActionScript on the receiving server.

2870589

When doing HDS Live recording, an “Inserting safety gap” warning is logged to indicate a drift between the ideal configured fragment duration and actual fragment duration. This can happen if the fragment duration is misconfigured and is not a multiple of the encoder’s GOP size, or if the encoder is not able to keep a stable, constant GOP size. When this drift becomes large, a “gap” is inserted in the fragment to represent the drift. It should not result in any observable playback problem.

2859133

Playback issues are seen on iOS device versions 4.3.x when using the HTML5 video source tag and disabling the SlidingWindow configuration on the server (HLSSlidingWindowLength set to 0 - at httpd.conf or at Application.xml or at Event.xml level). Playback stops and clicking the Play button does not resume it. The workaround is to seek to somewhere in the middle of the stream, but seeking to the latest point in playback will also return it to a stopped state. If one tries to resume, playback starts from the beginning instead of the latest point in the timeline. These playback issues are not seen if you put the whole stream URL in the Safari address bar, or on iOS device versions below 4.3.

2426933

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.

2476494

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

2850151

FMS fails to startup if IPv6 is enabled, but OS doesn’t support IPv6

2849944

The LiveCast application edge node does not reconnect to origin node application properly.

2674905

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.

2633530

CGI not supported in the Flash Media Server Apache installation.

2501913

Authorization and Access plugins have compilation warnings that are harmless. Removing the warnings now would require an interface change breaking compatibility with pre-existing plugins that were built using the current interface. To maintain compatibility and not require users to have to rebuild and retest their existing plugins, we have decided not to fix these warnings at this time.

2275665

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. The sum total of all sc-stream-bytes for a particular client will usually be. 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.

1931450

The MP4/F4V format delivers XMP text under the wrong tag. Specifically MP4/F4Vs parsed by Flash Media Server or Flash Player (via Progressive Download Playback) will produce onXMPData messages containing their XMP text under the tag onXMPData/data. The correct tag is onXMPData/liveXML as specified by XMP definitions. FLV container format renders this data correctly. Users should be prepared for this difference in XMP reporting according to file format change.

Note: customers should test the new XMP ActionScript libraries at:

http://www.adobe.com/devnet/xmp

1630621

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

1611644

The OnImageData event within H264 streams is not supported.

1525751

While using AMF0 mode with AS3, If Date (or XML) is being passed as an argument in a Remote Procedure Call (NetConnection.call, NetStream.send or SharedObject.send), it should be passed as the last argument. No argument should be sent as reference after a Date or XML has been added to the argument list of an RPC. Using AMF3 with AS3 is recommended.

2751666

x-suri-stem is missing x-sname in publish and unpublish event entries

3022151

The server records an error “Error from libf4f.dll: Unable to create sample descriptor for message “ in the server logs when doing a multi-point publish from a f4v file to a livepkgr applications. This has to be addressed by detaching a source stream from the server NetStream and re-attach a source stream as in the example below:

ns.attach(false); // detach from the source stream

ns.attach(application.sourceStream); // re-attach and resubscribe to the source stream

ns.publish(streamURI); // republish

3052723

As of 4.5.4 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.

3056535

Recording of PRTMP protected content is not supported as DRM metadata expires and cannot be persisted in a file. Therefore, a server side stream object cannot be used for recording if it is playing protected content from a VoD file.

3015244

When performing HDS Live, appending HDS content to an existing stream/file that is over two days old will result in an error, "Restarting the recording after 2.000000 days is not allowed and it’s Stopping the recording. Please change the config parameter<MaxRestartGap> under <Recording> in event.xml if you would like to increase this." And the recording will fail. This is an expected behavior as it is not the intent to append to a content that is not of the same timeline. Clear such contents from the streams folder and restart the HDS stream.

3020294

NetStream object cannot be used to play a different stream when PRTMP is enabled. If a NetStream is used to play a single stream, and is reused to play a different stream later, the second play will fail. To workaround this problem, a new NetStream object can be created for each stream play instead of reusing the same NetStream for multiple streams. We have also confirmed that playing multiple streams on the same NetStream with client side playlist still works as expected.

3004381

When HLS encryption is enabled, it is observed that the HLS client on MAC OS X 10.6.x skips nearly one segment length of media during playback. This is not observed on iDevices.

3060434

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

Minimum system requirements

The Adobe Flash Media Server 4.5 system requirements are :

Supported operating systems

  • Microsoft® Windows Server® 2008 R2 64 bit
  • Linux CentOS 5.5 64 bit
  • Red Hat® Enterprise Linux® Server 5.5 64 bit
  • Windows XP 32bit (for Flash Media Development Server only)
  • Windows 7 64bit (for Flash Media Development Server 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)

Install your software

To install Flash Media Server on Windows:

  1. Double-click the installer application and follow the on-screen instructions.
  2. Enter a serial number. If you don’t enter a serial number, Flash Media Development Server installs.
  3. During the installation process you will be asked to enter a user name and password for the first valid server administrator. The user name is written to fms.ini file and the password is written to Users.xml those are located under the conf folder after installation (You can use the Administration Console to add other administrators later).
  4. It is optional to install Apache 2.2 with Flash Media Server. If you have chosen to install Apache, you will be asked if you would like for Apache to listen on port 80. If not, FMS will be using port 80 instead. (If Apache is listening on port 80, all the RTMPT traffic will be proxying through Apache by default. And it is highly recommended user to enter the interface (IP address) FMS is listening on. This is to ensure an IP address is included in HTTPIdent2 tag returning to the player, so that player can use the specified IP address instead of the original hostname when making the RTMPE connection through Apache. And the Ident2 tag can be found in Adaptor.xml). Also, note that letting the RTMPT traffic proxying through Apache, will reduce the quality of service for the RTMPT connections.
  5. Accept the default server ports or enter new port numbers.
  6. The final installation step gives you the opportunity to view the Readme.htm file, start Flash Media Server, and select the option to start Flash Media Server manually when you reboot your computer. Select any options you'd like, and click Finish.

The installation is complete. If you configured it to start automatically, the Flash Media Server service starts. To start the server manually, select Start > Programs > Adobe > Flash Media Server 4.5 > Start Adobe Flash Media Server 4.5 and Start Adobe Flash Media Administration Server 4.5

To open the Flash Media Administration Console, select Start > Programs > Adobe > Flash Media Server 4.5 > Adobe Flash Media Administration Console.

To install Flash Media Server on Linux:

  1. Log in as a root user (recommended to install Flash Media Server). To install as non-root user, please check updated documentation.
  2. Open a shell window and switch to the directory with the installation file, FlashMediaServer4.5_x64.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: ./installFMS
  6. The installation program starts and displays a welcome message.
  1. Press Enter to start the installation. Follow the installation instructions on your screen. During the process you will be asked to
  2. Enter a serial number. If you don’t enter a serial number, Flash Media Development Server installs.
  3. Enter the installation directory and ports which the server will use
  4. It is optional to install Apache 2.2 with Flash Media Server. If you have chosen to install Apache, you will be asked if you would like for Apache to listen on port 80. If not, FMS will be using port 80 instead. (If Apache is listening on port 80, all the RTMPT traffic will be proxying through Apache by default. And it is highly recommended user to enter the interface (IP address) FMS is listening on. This is to ensure an IP address is included in HTTPIdent2 tag returning to the player, so that player can use the specified IP address instead of the original hostname when making the RTMPE connection through Apache. And the Ident2 tag can be found in Adaptor.xml). Also, note that letting the RTMPT traffic proxying through Apache, will reduce the quality of service for the RTMPT connections.
  5. Enter an administrative user name and password for the first valid server administrator. These values are written to the fms.ini file which is located inside of the conf folder after the installation.
  6. Enter a user for Flash Media Server processes to run as. The default is the "nobody" user. (The user you select is also the owner of the Flash Media Server files.) Your choices are written to the fms.ini file. You can edit the fms.ini file to modify this and other security properties later, if needed.
  7. Review the summary of the installation options you have chosen, which are displayed in the installer.
  8. To start the server manually, go to the installation directory (default is /opt/adobe/fms/). Use the command “./fmsmgr server fms start” to start Flash Media Server and “./fmsmgr adminserver start” to start Flash Media Administration Server.

The installation is complete. If you configured it to start automatically, the Flash Media Server service starts.

Uninstall your software

To uninstall Flash Media Server on Windows:

  1. Select Start > Programs > Adobe > Flash Media Server 4.5 > Uninstall Adobe Flash Media Server 4.5
  2. In the confirmation dialog box, click Yes to uninstall Flash Media Server.
  3. Flash Media Server is removed from your computer. A second confirmation dialog box appears when the process is complete

To uninstall Flash Media Server on Linux: :

  1. Log on to the server where Flash 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/fms.
  4. By default, /opt/adobe/fms is the directory where Flash Media Server is installed. If you installed the server in a different directory, replace /opt/adobe/fms with the actual installation location.
  5. Execute the uninstall script. /uninstallFMS.
  6. Follow the displayed uninstall instructions.

Other resources

Flash Media Server Documentation Center

Flash Media Server Product Home

Flash Media Server Developer Center

Flash Media Server End User License Agreement

Flash Media Server Online Forums

Flash Media Server Hands-on Training

Flash Media Server Blog

Flash Media Server User Group

Flash Video Streaming Service

Flash Media Solutions Providers

Flash Player Product Home

Copyright © 2012 Adobe Systems Incorporated.