Skip to main content
Participating Frequently
February 25, 2008
Question

FMS3: Delay in start of video stream; error

  • February 25, 2008
  • 2 replies
  • 447 views
Hi,

We're setting up an FMS3-based video streaming system for a new website, and have built a player using AS2 (for compatibility with Flash Player v8) and the FLVPlayback componenent which uses FMS3's new native bandwidth checking to provide us with a figure with which we can work out which of 3 streams to play and how long to buffer before playback. The initial NetConnection connection happens pretty much instantly and we get the numbers we're looking for, but it then takes about another 30 seconds before the FLVPlayback component connects to the server and begins to stream the video. There doesn't seem to be anything in the logic of the player to cause this, and when we test on a local deployment of FMS3 we don't get the problem. Furthermore, we had this player working nicely with FMS2 on the remote server until recently, when we upgraded during our development stage. We think the key must be in the errors we get in the FMS server log:

quote:

Mon 09:30:33 AM: Connect : rtmp://OurDomain/OurAppName
Mon 09:30:35 AM: Core (10567) connection to admin accepted.
Mon 09:30:35 AM: Core (10567) sending register cmd to edge. - Player receives BW check numbers here
Mon 09:30:35 AM: (_defaultRoot_, _defaultVHost_) : Application (OurAppName) is not a valid signed application; loading access denied.
Mon 09:30:35 AM: (_defaultRoot_, _defaultVHost_) : Application (OurAppName/A201EB4C-C3F3-4A56-8C42-CA9373F0CA90) is not a valid signed application; loading access denied.
Mon 09:30:35 AM: Connection rejected by server. Reason : [ Server.Reject ] : (_defaultRoot_, _defaultVHost_) : Application (OurAppName/A201EB4C-C3F3-4A56-8C42-CA9373F0CA90) is not a valid signed application; loading access denied.
Mon 09:31:05 AM: Connect : rtmp://OurDomain:1935/OurAppName - Video begins streaming


The GUIDs are the folder names on our server containing the media, and appear here because FMS takes the first part of the path to be the application instance, which has not proved to be a problem before.

I can't find anything about validating or signing applications, but I suspect these errors have something to do with the inexplicable delay before streaming starts. Does anyone know anything about this?

thanks,
Ben
    This topic is closed to new replies. Start a new post to keep the conversation going.

    2 replies

    Participating Frequently
    February 25, 2008
    This was the cause, thanks. We had somehow overlooked this fact about FMS streaming edition, Adobe don't exactly make it clear that you can't do any server-side scripting at all with this edition - luckily the "vod" signed application does what we want.
    February 25, 2008
    Are you using Interactive Server(FMIS) or Streaming Server (FMSS).

    I guess that OurAppName is NOT the server-side application you are using for streaming video as log says that this application was never loaded on server anyways.

    In case you are using Streaming edition, FMSS 3 doesn't allow user created server-side applications,