Monday, 14 March 2011


KryKey is about to schedule an update to it's Flash Media Server Streaming Software on all servers - next Monday the 21st of March at 3am GMT (UK time) [that is Sunday  20th March 10pm New York time] we will be upgrading the FMS and while this is happening ALL KryKey radio stations will be offline and unavailable. This update is expected to take less than 10 minutes.

Critical vulnerabilities have been identified in Adobe Flash Media Server (FMS) 4.0 and earlier versions, Adobe Flash Media Server (FMS) 3.5.3 and earlier versions, and Adobe Flash Media Server (FMS) 3.0.6 and earlier versions for Windows and Linux. One of the vulnerabilities could allow an attacker, who successfully exploits the vulnerability, to run malicious code on the affected system. Adobe has provided an update to address the reported vulnerabilities and recommends that users update their installations to Flash Media Server 4.0.1, 3.5.5 or 3.0.7 respectively using the instructions provided below

What's new in this release
This release includes fixes for the following three issues. Please see the Adobe Security Bulletin for details.
CVE -2010-3633
In addition to the above bugs, the following are also fixed in this release:
Frequently recording silence into an audio track of an F4V recording could eventually cause a stopped and corrupted F4V file to be recorded.
When SWF Verification version 2 is in use, and a client connects from a file not present in the SWF Verification folder - error message was eWRONG_VERSION not eNO_FILE as expected.
Live stream video when played through a remote edge may repeat several frames on a play, stop, and then play again.
Certain rarely used H264 message types could cause FMS to crash when recording to an F4V/MP4 file
When video-only streams are unpublished and republished again, they may encounter frequent re-buffering.
In FMS Authorization Plugin ignoring the E_DISCONNECT event meant leaking memory for each disconnecting client
Connection: Close specified RTMPT are not honored - instead they do Keep-Alive
Video only streams may drop frames at buffer after buffer is empty at low bandwidth connection.
Known Issues
The following are known issues in this release:
When using Dynamic Streaming with DVR, if you record VP6 and Mp3 content with different frame sizes as an F4V file you'll see artifacts during the transition. Instead, you should record as an FLV file.
When using DVR with Mp4 and RAW files in an Edge/Origin configuration, playback will stall intermittently after some time. The workaround is to refresh the browser.
Video artifacts can be seen when switching between RAW and MP4 files.
MP4 recording of a Screen Sharing stream is unsupported.
Playing a live stream for an extended period of time, with a non-zero client buffer set can result in the stream permanently getting into a stalled state. The workaround is to restart live stream playback once every three weeks.
DVR streams that have long keyframe intervals can result in long delays when switching during Dynamic Streaming.
Actions from the authorization plugin cannot be invoked on a client from the E_CONNECT event.
Live streams which are played for longer than 20 days may stop playing.
SWF Verification User-Agent exceptions don't properly match partially into user agent strings.
Heavy RTMPT traffic can lead to incorrect connection counts and stalled users
Several flvcheck errors should actually be warnings. Warnings mean FMS will load the file successfully, but there may be problems when streaming. But in some cases, an error is thrown even if FMS would continue to load the file.
Invalid F_STREAM_PATH is returned for URI parameters containing colons.
Unpublishing and republishing a live stream may result in messages from a previous stream getting recorded to the new stream, and in messages with “backward” timestamps at the beginning of the new recording.
x-comment is always appended to logging fields
F4V files with large XMP data cause the client to disconnect.
Shared object parsing bug can result in some properties (usually complex objects) disappearing, and clients possibly getting disconnected.
You cannot seek within MP4 and F4V files which do not contain a sync sample box.
FMSCheck tool does not support all codecs supported by FMS. Only Mp3 audio and Sorensen video codecs are supported.
Starting a DVRCast recording for multiple streams (to support Dynamic Streaming) may result in recordings that are out of sync.
Updates of Shared Objects greater than 10MB in size can result in clients being disconnected.
When streaming from Flash Media Server on networks that experience high latency and loss, TCP transmission enforces a lower bandwidth rate. For details on this issue please see:
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 less than or equal to sc-bytes, not always equal to sc-bytes. 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.
Creating an MP4 recording from a server-side playlist of streams containing different codec types may lead to a corrupted MP4.
Corrupted recordings may result if two recordings are in progress from two different fmscore processes, but write to the same physical file. This can happen due to misconfigured virtual directories.
Calling IFCAccessContext::getStats() from the Access adaptor constructor can result in a crash.
First audio packet after append is not getting the correct sample description when the audio codec chosen is AAC. This results in an unnecessary extra file when
processing the recording using the F4V Post Processor tool.
Starting a play using the client-side ActionScript NetStream.play2() API with “append” mode could intermittently result in meta data being discarded, affecting playback. Customers should be advised to not start a record with “append” mode.
Plug-ins built on Red Hat 5.2 must be built as 32-bit shared objects, if necessary by explicitly specifying –m32 gcc option.
1902539 with zero duration for H.264 content may result in black frames.
Users may experience dropped frames when playing live video-only streams in Flash Player. If this occurs, disable live queuing by setting the new configuration in Application.xml to false, . In server side ActionScript, you can also set Stream.maxQueueSize = 0.
When switching between H.264 content during Dynamic Streaming, some frames may be lost resulting in a slight stutter during switch.
You will need to restart the server after entering a serial number via Administration Console.
When playing a server-side stream, a minimum bufferTime must be set on the client side to ensure smooth playback. For more information, please refer to the tech note.
Very low frame rate H.264 videos may take a long time to start if the buffer is set too short.
Pause command in Flash Player 9.0.115 or later versions will not suspend the buffer from getting filled. If the playback is resumed before the buffer is full, pause and unpause events will not be logged in the server’s access.log.
When the server CPU usage is high, a limitation in the Windows operating system can cause the non‐paged pool memory to be exhausted, leading to instability which may require rebooting the system. For more information on this non‐paged pool spike, please see
When streaming audio only, disable the Server.xml node set the EnableAggMsgs propery as follows: false to optimize performance for audio delivery.
The OnImageData event within H264 streams is not supported in this release.
Server-side play does not play if the file size is less than the configured buffer time (MinBufferTime tag in Application.xml), or 2 seconds.
Audio/Visual glitch when switching between videos in a client-side-playlist.
While using AMF0 mode with AS3, If Date (or XML) is being passed as an argument in a Remote Procedure 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.
Use Microsoft .NET 2003 or Microsoft Visual C++ 2005 to compile plug‐ins on Windows. Use GNU Compiler Collection 3.4.x to compile plug‐ins on Linux.
Playing back a file using server-side ActionScript stream can result in the stream being played back faster than normal (i.e. an x sec stream may finish playing in < x secs.) because the server-side stream is a Live stream which may result in messages being dropped.
The Start Screen and Sample video player will not operate

No comments:

Post a Comment