[Fms]adobe FMS Configuration Implementation (FMS/HLS/HDS) function experience

Adobe's HTTP Dynamic streaming is an HTTP-based streaming solution for Apple's HLS solution, based on its scenario description, which can support both HTTP and rtmp, both on-demand (VOD) and live. Therefore, this scheme is equipped with the following procedures:

Server environment: LINUX x86-64 8G Memory (I chose the test plan is to put the FMS and Apache on the same machine, distributed installation is not table)

Software Environment: (This process is only guaranteed to be configured under the corresponding software version, Adobe's software is constantly changing, other versions of their own research)

Flash Media Server 4.5 for Linux version development

OSMF simple Player for Http Dynamic streaming download Address: Http://www.osmf.org/downloads/OSFMPlayer_zeri2.zip

Apache2 (my Linux x86-64 server comes with a apache2,fms4.5 installation will also install a Apache2, they can coexist, will not conflict)

Http://www.cuplayer.com/PcIOSAndroid/

here is the installation configuration process:

1) Install FMS4.5, install to/opt/adobe/fms/by default

Log in to Linux as root, unzip the FMS4.5 into the./fms4.5 directory, and the CD enters the Linux directory below it,

>TAR-ZXF flashmediaserver4.5_x64.tar.gz

>CD fms_4_5_0_r297 (Note: fms_4_5_0_r297 is the directory extracted from the previous step)

>./installfms

Follow the steps to install, note that 2 points is:

1.1) Choose to install a self-brought Apache (our system also has a Apache2, which will say how to coexist)

1.2) Create a management user and remember the password

FMS4.5 was successfully installed in the/OPT/ADOBE/FMS directory, where this installation directory is represented by Rootinstall, which is convenient for later reference.

2) Download and install OSMF simple player, unzip the downloaded Player and place it in:/opt/adobe/fms/webroot/osfmplayer directory

3) Configuration:

3.1) By default, the FMS listener 80 port receives the traffic and then passes to Apache's 8134 port (the FMS comes in with a listening 8134 port), this delivery process under high Network load will bring performance problems. Therefore, do the following configuration to solve this problem.

Modify the Rootinstall/conf/fms.ini, the Adaptor.hostport =: 1935, 801 lines, changed to Adaptor.hostport =:1935; Do not allow the FMS to monitor 80 ports;

At the same time, it will be httpproxy. HOST =: 81,341 line, instead: Httpproxy. HOST =

This removes the above proxy forwarding process.
3.2) The Listen 81,341 line in the rootinstall/apache2.2/conf/httpd.conf file does not have to change, so that the FMS installed Apache continues to listen on 8134 ports, while Apache in our system still listens on 80 ports, This will not conflict. (Of course, the downside is that any HTTP access to the back needs to take 8134, we try, not too much problem.) )

3.3) HTTP Origin module is not configured, FMS4.5 installed Apache has been configured to support the HTTP Dynamic streaming module, mainly for on-demand and broadcast streaming data to the viewer;

3.4) Find a computer with a webcam (I use WinXP) for the live video encoding end, install Flash Media live Encoder 3.2 to
D:\Program Files\adobe\flash Media Live Encoder 3.2 directory, open its subdirectories conf the following config. edit file, modify/flashmedialiveencoder_config/ The Mbrconfig/streamsynchronization/enable node value is true.

(Use absolute time)
<mbrconfig>
<streamsynchronization>
<enable>true</enable>

3.5) Configure FMS server to use absolute time when broadcasting, open Rootinstall/applications/livepkgr/application.xml, modify/application/streammanager/ The Live/assumeabsolutetime node is true.
<Application>
<StreamManager>
<Live>
<AssumeAbsoluteTime>true</AssumeAbsoluteTime>
</Live>
</StreamManager>
</Application>

3.6 Configuring Rootinstall/conf/server.xml, modifying
<Root>
<Server>
<ResourceLimits>
<RecBuffer>
<MaxFlushTime> 3 <MaxFlushTime>
Change the value of <MaxFlushTime> to 1.

4) Verify live and on-demand
>CD Rootinstall
>./fmsmgr Server FMS Restart--Restart FMS
>./fmsmgr adminserver Restart--restart admin Server

4.1) Verify that the VOD is based on Dynmaic Http streaming

Open http://yourserverip:8134/in Firefox (with FireBug) or Google Chrome browser
You can see the default home page after the FMS server is installed with
1-"Launch Flash Media Administration Console", which allows you to manage FMS server (user name and password created with installation)
2-On the center right side of the home page, there is "(HDS) HTTP Dynamic streaming sample" clicked in, you can see the video playback interface, open the developer tools interface with Firebug or Google Chrome, switch to the network option, You can see that the video is being downloaded by segment, which verifies that the HTTP Dynamic streaming VOD method is successful.

   4.2) Verify Live Success
Launch the above installed Flash Media Live Encoder 3.2, choose Preset Custom, video selection H264,29.9fps, resolution 352x288, Code rate optional 3, 350,h264 can be set every 2 seconds a key frame, etc., choose MP3 do audio and so on.
in the right stream to Flash Media server FMS URL: RTMP://YOURSERVERIP/LIVEPKGR, fill in the Stream column: livestream%i?adbe-live- Event=liveevent (if the above selected MBR3 bit rate live), if only a bit rate live is selected to fill in: Livestream?adbe-live-event=liveevent
and then click the start to publish live.

Use the browser to open the osmfplayer:http://yourserverip:8134/osfmplayer/osmfplayer.html installed above
You can then use Osmfplayer to play the following address to see the live Image:
HTTP://YOURSERVERIP:8134/HDS-LIVE/LIVEPKGR/_DEFINST_/LIVEEVENT/LIVESTREAM.F4M (a bit rate SBR live)
Or three bit rate live (MBR), enter one of the following three
http://yourserverip:8134/hds-live/livepkgr/_definst_/liveevent/livestream1.f4m
http://yourserverip:8134/hds-live/livepkgr/_definst_/liveevent/livestream2.f4m
http://yourserverip:8134/hds-live/livepkgr/_definst_/liveevent/livestream3.f4m

Using Firebug or Google Chrome to open the developer tools interface and switch to the network option, you can see that the video is downloaded by segment, which verifies that the HTTP Dynamic streaming live mode is successful.

Video data files generated while live are stored in the rootinstall/applications/livepkgr/streams/_definst_/directory
The control file is saved in the Rootinstall/applications/livepkgr/events/_definst_/liveevent directory

5) The role of several documents
*.f4m--Flash Media Manifest file. Contains information about codec, resolution, and the availability of multi-bitrate Files. m3u8, similar to the Apple HLS scheme, is the mainfest index file, which includes encoding, resolution bitrate, etc.

*.f4x--Index file. Contains the location of specific fragments within a stream.

*.F4F--A segment. The tool outputs one or more F4F files. Each file contains a segment of the source file. Each segment contains one or more fragments of content. A player can use a URL to address each fragment.

Note: The above configuration is HTTP dynamic streaming--note that the video Publisher uses the RTMP protocol to publish the video to the FMS server, the viewer player osmf to download the video and play the watch through the HTTP protocol segment;

Based on the above FMS server, there is also a configuration and implementation is the use of rtmp to live, that is, video publishers with the RTMP protocol to the video published to the FMS server, the viewer through another support rtmp protocol player to download video through rtmp. The configuration is as follows:

On the basis of the above configuration,

1) Copy the Videoplayer directory under the Rootinstall/samples directory to rootinstall/webroot/, which is a Flash player that supports RTMP protocol playback, similar to the OSMF player above.

2) Fill in the FMS URL in Flash Media Live Encoder3.2 there: rtmp://yourserviceip/live

Fill in the livestream in the stream below.

3) Viewer open with browser: http://yourserverip:8134/videoPlayer/videoPlayer.html, then enter the stream URL at the bottom of the page:

Rtmp://yourserverip/live/livestream and Tick live, then click Play Stream to watch.

The viewers here use the rtmp download method instead of the HTTP download method. That's the difference.

：

Server environment: LINUX x86-64 8G Memory (I chose the test plan is to put the FMS and Apache on the same machine, distributed installation is not table)

Software Environment: (This process is only guaranteed to be configured under the corresponding software version, Adobe's software is constantly changing, other versions of their own research)

Flash Media Server 4.5 for Linux version development

OSMF simple Player for Http Dynamic streaming download Address: Http://www.osmf.org/downloads/OSFMPlayer_zeri2.zip

Apache2 (my Linux x86-64 server comes with a apache2,fms4.5 installation will also install a Apache2, they can coexist, will not conflict)

Here is the installation configuration process:

1) Install FMS4.5, install to/opt/adobe/fms/by default

Log in to Linux as root, unzip the FMS4.5 into the./fms4.5 directory, and the CD enters the Linux directory below it,

>TAR-ZXF flashmediaserver4.5_x64.tar.gz

>CD fms_4_5_0_r297 (Note: fms_4_5_0_r297 is the directory extracted from the previous step)

>./installfms

Follow the steps to install, note that 2 points is:

1.1) Choose to install a self-brought Apache (our system also has a Apache2, which will say how to coexist)

1.2) Create a management user and remember the password

FMS4.5 was successfully installed in the/OPT/ADOBE/FMS directory, where this installation directory is represented by Rootinstall, which is convenient for later reference.

2) Download and install OSMF simple player, unzip the downloaded Player and place it in:/opt/adobe/fms/webroot/osfmplayer directory

3) Configuration:

3.1) By default, the FMS listener 80 port receives the traffic and then passes to Apache's 8134 port (the FMS comes in with a listening 8134 port), this delivery process under high Network load will bring performance problems. Therefore, do the following configuration to solve this problem.

Modify the Rootinstall/conf/fms.ini, the Adaptor.hostport =: 1935, 801 lines, changed to Adaptor.hostport =:1935; Do not allow the FMS to monitor 80 ports;

At the same time, it will be httpproxy. HOST =: 81,341 line, instead: Httpproxy. HOST =

This removes the above proxy forwarding process.
3.2) The Listen 81,341 line in the rootinstall/apache2.2/conf/httpd.conf file does not have to change, so that the FMS installed Apache continues to listen on 8134 ports, while Apache in our system still listens on 80 ports, This will not conflict. (Of course, the downside is that any HTTP access to the back needs to take 8134, we try, not too much problem.) )

3.3) HTTP Origin module is not configured, FMS4.5 installed Apache has been configured to support the HTTP Dynamic streaming module, mainly for on-demand and broadcast streaming data to the viewer;

3.4) Find a computer with a webcam (I use WinXP) for the live video encoding end, install Flash Media live Encoder 3.2 to
D:\Program Files\adobe\flash Media Live Encoder 3.2 directory, open its subdirectories conf the following config. edit file, modify/flashmedialiveencoder_config/ The Mbrconfig/streamsynchronization/enable node value is true.

(Use absolute time)
<mbrconfig>
<streamsynchronization>
<enable>true</enable>

3.5) Configure FMS server to use absolute time when broadcasting, open Rootinstall/applications/livepkgr/application.xml, modify/application/streammanager/ The Live/assumeabsolutetime node is true.
<Application>
<StreamManager>
<Live>
<AssumeAbsoluteTime>true</AssumeAbsoluteTime>
</Live>
</StreamManager>
</Application>

3.6 Configuring Rootinstall/conf/server.xml, modifying
<Root>
<Server>
<ResourceLimits>
<RecBuffer>
<MaxFlushTime> 3 <MaxFlushTime>
Change the value of <MaxFlushTime> to 1.

4) Verify live and on-demand
>CD Rootinstall
>./fmsmgr Server FMS Restart--Restart FMS
>./fmsmgr adminserver Restart--restart admin Server

4.1) Verify that the VOD is based on Dynmaic Http streaming

Open http://yourserverip:8134/in Firefox (with FireBug) or Google Chrome browser
You can see the default home page after the FMS server is installed with
1-"Launch Flash Media Administration Console", which allows you to manage FMS server (user name and password created with installation)
2-On the center right side of the home page, there is "(HDS) HTTP Dynamic streaming sample" clicked in, you can see the video playback interface, open the developer tools interface with Firebug or Google Chrome, switch to the network option, You can see that the video is being downloaded by segment, which verifies that the HTTP Dynamic streaming VOD method is successful.

4.2) Verify live broadcast success
Launch the above installed Flash Media Live Encoder 3.2, choose Preset Custom, video selection H264,29.9fps, resolution 352x288, the rate can be selected 3, 2, 350,h264 can be set to a key frame of every five seconds, etc., Choose MP3 to do audio and so on.
In the right stream to Flash Media server FMS URL, fill in: rtmp://yourserverip/livepkgr, in the stream column: livestream%i?adbe-live-event= Liveevent (if the above selected MBR3 bit rate live), if only one bit rate live, fill in: livestream?adbe-live-event=liveevent
Then click Start to publish the live broadcast.

Use the browser to open the osmfplayer:http://yourserverip:8134/osfmplayer/osmfplayer.html installed above
You can then use Osmfplayer to play the following address to see the live Image:
HTTP://YOURSERVERIP:8134/HDS-LIVE/LIVEPKGR/_DEFINST_/LIVEEVENT/LIVESTREAM.F4M (a bit rate SBR live)
Or three bit rate live (MBR), enter one of the following three
http://yourserverip:8134/hds-live/livepkgr/_definst_/liveevent/livestream1.f4m
http://yourserverip:8134/hds-live/livepkgr/_definst_/liveevent/livestream2.f4m
http://yourserverip:8134/hds-live/livepkgr/_definst_/liveevent/livestream3.f4m

Using Firebug or Google Chrome to open the developer tools interface and switch to the network option, you can see that the video is downloaded by segment, which verifies that the HTTP Dynamic streaming live mode is successful.

Video data files generated while live are stored in the rootinstall/applications/livepkgr/streams/_definst_/directory
The control file is saved in the Rootinstall/applications/livepkgr/events/_definst_/liveevent directory

5) The role of several documents
*.f4m--Flash Media Manifest file. Contains information about codec, resolution, and the availability of multi-bitrate Files. m3u8, similar to the Apple HLS scheme, is the mainfest index file, which includes encoding, resolution bitrate, etc.

*.f4x--Index file. Contains the location of specific fragments within a stream.

*.F4F--A segment. The tool outputs one or more F4F files. Each file C