Installation guide

AsignicantbenetoverbroadcastingdirectfromtheFlashPlayer,FlashMediaLiveEncoder3
allows you to broadcast video using either the VP6 or H.264 codec, and now supports
multi-bit-rateencoding(uptothreesimultaneousstreams).Youalsohavegreateraudio
controlwithbit-rate-ecientNellymoser,MP3,orAACencoding.
FlashMediaLiveEncoderisavailableasafreedownloadfromAdobeat:
www.adobe.com/go/fmle.
Data keyframes
Feature in Flash Media Streaming Server and Flash Media Interactive Server; requires Flash Player
6 or later.
With the data keyframe feature in Flash Media Server 3.5, metadata can be sent whenever a new
subscriber requests the stream. e metadata can also be updated at any time by dispatching a new
datakeyframeviaserver-sideorclient-sideActionScriptorviaFlashMediaLiveEncoder.is
new metadata is then received by all connected clients through the onMetadata event handler.
A data keyframe is a special data message that can be set to a live stream and stored in the memory
oftheserver.Liketheotherdatamessages,adatakeyframecontainsahandlernameandalistof
properties that store the data. ere is no limit to the number of data keyframes that can be set. For
security reasons, only the publisher and the server are allowed to set and clear the data keyframes.
Data keyframes are sent from the client through NetStream.send() or Stream.send() in
the server-side script. Two special methods, @setDataFrame and @clearDataFrame, are
dened to set and clear the data keyframe. To avoid collision with other client dened methods,
an @ sign is added to these methods.
Multipoint publish
Feature in Flash Media Streaming Server and Flash Media Interactive Server; requires Flash Player
6 or later.
Another challenge for live broadcasting is scalability. Due to the limitations of processor resources
or network bandwidth, one server can support only a xed number of subscribers. To support more
simultaneous viewers, some of the trac needs to be handled by other servers. Multipoint publish
allows the broadcaster to publish to multiple servers with only one client-to-server connection.
Inthepast,theAPIintheserver-sidescriptwouldonlyallowstreamingfromaremoteserverin
one direction through the use of server Stream and NetConnection objects. is made it
possible to play a stream from a remote server. However, there was no way to remotely publish
a stream to a remote server or to know which streams were attempting to be published to
anotherserver,unlessone-to-oneconnectionsweremaintainedbetweenallservers.Inaddition,
because of restricted server-side script access on content delivery networks, stream republishing
was not possible.
WiththeAPIsavailableinFlashMediaInteractiveServer3.5,broadcasterscandynamically
redirect streaming data to another server when necessary, without maintaining a persistent
connection betweenserversandwithoutcustomserver-sidecode.Newserver-sidenotication,
Publish and Unpublish events, is now available for those who require additional customization.
Multipoint publishing provides a much-needed degree of exibility, customization, and
scalability to large-scale live video applications. For more details, consult the Flash Media
Server Developer Guide.
Securing content with Flash Media Server 3.5
Whenever content is distributed electronically, there is some risk of it being copied,
misappropriated, or redistributed. Flash Media Server oers several levels of security to protect
your content and server resources that are unobtrusive, intuitive, and convenient to consumers.
52