Skip to main content
January 24, 2011
Question

swf file created with older version of Flash tools doesn't work on FMS4

  • January 24, 2011
  • 2 replies
  • 1169 views

We have some HTML pages that embed a swf file to stream flv videos (code below). It is working on our old FMS 2 server. However, after we installed a new FMS4 server recently, the skin (video player) is still showing up on the HTML page, but the video just doesn't play. The .swf file was created by someone else several years ago, and I suspect that it was developed with older version of Flash tools (not sure which one though), and is not compatible with FMS4. If this is the case, can it be fixed by installing some component that is required by older version of Flash on our new FMS4 server, or will we have to rebuild the .swf file using a newer version of Flash tools? If version compatibility isn't the case, what else could cause the problem? Thanks in advance for any suggestion!

<object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#ve rsion=7,0,0,0" id="videoObj" width="100%" height="100%" >
  <param name="movie" value="/video/myVideoPlayer.swf" />
  <param name="quality" value="high" />
  <param name="name" value="video" />
  <param name="bgcolor" value="#ffffff" />
  <param name="FlashVars" value="playerLogo=/video/myLogo.swf&colorTheme=0x513484&flvPath=rtmp://fms.mydomain.com/sites/&hi8=a5.hi8&lo8=a5.lo8&hi7=a5.hi7&lo7=a5.lo7&capti onUrl=a5.xml"/>

<embed  id="video" name="video" src="/video/myVideoPlayer.swf" bgcolor="#FFFFFF" quality="high" height="100%" width="100%" flashvars="playerLogo=/video/myLogo.swf&colorTheme=0x513484&f lvPath=rtmp://fms.mydomain.com/sites/&hi8=a5.hi8&lo8=a5.lo8&hi7=a5.hi7&lo7=a5.lo7&capti onUrl=a5.xml">
  <h1>You need Flash 7 or higher.<a href="http://www.adobe.com/go/getflashplayer">Get Flash</a>.</h1>
  </embed>
</object>

    This topic has been closed for replies.

    2 replies

    Participating Frequently
    January 25, 2011

    One thing here I can think of is objectEncoding.

    FMS supports both AMF0 and AMF3, but old Flash doesn't support AMF3 specific features so it may cause an issue.

    e.g. lets say a client is publishing a video using AMF3 to FMS and other subscribers are connected using old Flash that supports only AMF0, then these clients wont be able to play the video. Please do a cross-check for your scenario.

    Participating Frequently
    January 25, 2011

    I don't think this should be issue at first place , i mean there won't be case that FMS4 rejects connection or does not respond because its coming from client which is build using older version of Flash Authoring. Is this related to other thread where you stated "sites" folder problem?

    January 26, 2011

    Thanks SE0208 and zarihs!

    Actually the request sent by the HTML page was logged in FMS4's apache log, so it looks like the old video player has no problem sending request to FMS4 server.

    I tried to change the HTML file and replace the old player with StrobeMediaPlayback.swf (the player that comes with FMS4), and the video can be played very well. It's just the old swf has problem playing video on the newly installed FMS4 server.

    One thing I forgot to mention in my last post is, our old swf supports captioning, and supports different resolution ratio. The flashvars is like

    <embed  id="video" name="video" src="/video/myVideoPlayer.swf" bgcolor="#FFFFFF" quality="high" height="100%" width="100%" flashvars="playerLogo=/video/myLogo.swf&colorTheme=0x513484&flvPath=rtmp://fms.mydomain.com/sites/&hi8=a5.hi8&lo8=a5.lo8&a mp;hi7=a5.hi7&lo7=a5.lo7&capti onUrl=a5.xml">. So is it possible that I need to install some components on our new FMS4 server to support captioning before the old swf can work?

    SE0208, this and my earlier post are both related to the upgrade from FMS2 to FMS4. Our goal is not to make any changes to the existing HTMLs, so we need to keep the old video path and keep using the old swf.

    Participating Frequently
    January 26, 2011

    Like zarihs said earlier - it migth be AMF3 issue. Can you look into FMS logs and see if there is any error logged on FMS End - check application.00.logs of concerned application or core.00.logs,edge.00.logs,master.00.logs.

    Also are you publishing live content and trying to subscribe or is it just VOD content?

    Also do you have source of your old content, i mean can you run them standalone in Flash Authoring and see if you get Connection error or something?