Streaming over 2 FMS

Hi,
we need to stream a live video over more than one FMS.
We connected a camera to first FMS and publish a live stream.
That works fine.
Now, the second FMS (FMS2) is in a different location and
hosts the videos for our second office . To reduce the bandwidth
over the internet we would like to stream the live stream from FMS1
to FMS2, so that FMS2 can deliver the content in the second
intranet (one to one to many).
I hope you understand this.
Maybe one of you can help me, maybe with a sample.
Thanks in advance!
Friedemann Enderlein

FMS 3 has a feature called "Multipoint Publishing" that will
allow you to do exactly what you described. Using a little bit of
Server-Side Actionscript, you can detect when the stream is first
published to server 1, and republish it to server 2.
More information can be found online at livedocs.adobe.com,
or in the Flash Media Server Developers guide.

Similar Messages

Problem playing remote live stream from FMS

Hello all,
I'm having problems playing remote live streams from FMS (server-side) that I can play with any other player (client-side)
Example of server-side application which plays a remote live stream:
nc = new NetConnection();
nc.connect("rtmp://remoteserver/live");
stream = Stream.get("localStream");
stream.play("remoteStream.flv", -1, -1, true, nc);
This code works only sometimes.
Most of the times, FMS is able to connect to remote string and the localStream dispatches events:
   NetStream.Publish.Strart
   NetStream.Play.Reset
In this case, FMS is publishing the local stream but it is not playing the remoteStrem on it.
The rest of the times, localStream dispatches events:
   NetStream.Publish.Strart
   NetStream.Play.Reset
   NetStream.Play.Start
   NetStream.Data.Start
In this case FMS plays the remoteStream correctly.
Any hint to solve this issue?
Regards.

Thanks, I tried your code and it works when playing a remote live stream on another FMS.
But the remote live stream is not on a FMS but on a Wowza Server which re-streams an RTSP stream over RTMP.
With this code:
var nc;
var myStream;
application.onAppStart = function(){
     nc = new NetConnection();
     myStream = Stream.get("localstream");
     myStream.onStatus= function(info){
           trace(info.code);
     nc.onStatus = function(info){
           trace (info.code);
           if(info.code == "NetConnection.Connect.Success" ){
                myStream.play("remoteLive.sdp", -1, -1, true, nc);
     nc.connect("rtmp://remoteServer/live");
Every live stream player I tried was able to play the remote stream "remoteLive.sdp", but FMS play it only sometimes. This is the output log of the FMS application:
NetConnection.Connect.Success
NetStream.Publish.Start
NetStream.Play.Reset        <--------------------------------- Stuck there, stream won't play
Unloaded application instance wowza4/_definst_ <--- Reload app
NetConnection.Connect.Success
NetStream.Publish.Start
NetStream.Play.Reset        <--------------------------------- Stuck there, stream won't play
Unloaded application instance wowza4/_definst_ <--- Reload app
NetConnection.Connect.Success
NetStream.Publish.Start
NetStream.Play.Reset
NetStream.Play.Start       <--------------------------------- Stream is playing just fine
NetStream.Data.Start
Unloaded application instance wowza4/_definst_ <--- Reload app
NetConnection.Connect.Success
NetStream.Publish.Start
NetStream.Play.Reset       <--------------------------------- Stuck there, stream won't play
Any idea? Why FMS won't play it everytime?
Regards

When FMLE stopped,Remote RTMP stream to FMS 4.5 with rtmfp?

When FMLE stopped,Remote RTMP stream to FMS 4.5 with rtmfp?
edit "applications/multicast/main.asc" ?
HELP ME !!! THANKS!!!
* File: main.asc
* The server-side portion of the multicast sample application.
* This app accepts publish and unpublish requests from FMLE, and republishes
* the live stream from FMLE into a target Flash Group.
// General Constants
// "Constants" representing multicast event types.
var TYPE_FUSION = 1;
var TYPE_IP = 2;
var TYPE_P2P = 3;
// StreamContext Description, Constants and Functions
* Type: StreamContext
* This application tracks the context for live streams published to the server
* that are being republished into a Flash Group. The StreamContext "type" used
* for this is just an Object containing the following members:
*   client         - The encoding/publishing client.
*   streamName     - The source Stream name as published by the client.
*   type           - The multicast event type.
*   groupspec      - The groupspec identifying the Flash Group and capabilities.
*   address        - IP multicast address (optional for pure P2P events).
*   netConnection - A loopback NetConnection used for the mcastNetStream.
*   mcastNetStream - The NetStream used to republish the source Stream into
*                    the Flash Group.
*   netGroup       - An (optional) NetGroup handle for the target Group.
*                    Only present for Fusion or P2P events.
*   state          - One of the state constants defined immediately below
*                    this comment.
var STATE_INIT            = 0; // Starting state for a StreamContext.
var STATE_CONNECTING      = 1; // Establishing loop-back connection.
var STATE_CONNECTED       = 2; // Connection established.
var STATE_PUBLISH_PENDING = 3; // Attempting to publish.
var STATE_REPUBLISHING    = 4; // Actively republishing to multicast.
var STATE_UNPUBLISHING    = 5; // Shutting down multicast republish.
var STATE_UNPUBLISHED     = 6; // Unpublished successfully.
var STATE_DISCONNECTING   = 7; // Shutting down loopback connection.
var STATE_DISCONNECTED    = 8; // Connection shut down. Done.
* Registers a source Stream published by the specified client, along with the
* context for the multicast event, as a StreamContext Object.
* @param client - The Client publishing the stream.
* @param streamName - The source Stream name.
* @param params - The parameters resulting from parsing the source Stream's
*                 query string.
* @return The new StreamContext Object for the registered Stream.
function registerStream(client, streamName, params)
    var streamContext = { "client": client,
                          "streamName": streamName,
                          "type": params["fms.multicast.type"],
                          "groupspec": params["fms.multicast.groupspec"] };
if (params["fms.multicast.interface"])
streamContext["interfaceAddress"] = params["fms.multicast.interface"];
    if (params["fms.multicast.address"])
        streamContext["address"] = params["fms.multicast.address"],
    streamContext.state = STATE_INIT;
    updateStreamContextLookups(streamContext);
    trace("Registered multicast context for source stream: " + streamName);
    return streamContext;
* Updates the indexed lookups installed for the passed StreamContext Object
* with the application.
* @param streamContext - The StreamContext Object to (re)index.
function updateStreamContextLookups(streamContext)
    application.streamTable[streamContext.streamName] = streamContext;
    if (streamContext.netConnection)
        application.netConnTable[streamContext.netConnection] = streamContext;
    if (streamContext.mcastNetStream)
        application.mcastNetStreamTable[streamContext.mcastNetStream] = streamContext;
    if (streamContext.netGroup)
        application.netGroupTable[streamContext.netGroup] = streamContext;
* Provides access to the StreamContext Object for a registered source Stream
* by name.
* @param streamName - A registered source Stream name.
* @return The associated StreamContext Object; undefined if the source Stream
*         name is not registered.
function getStreamContextForSourceStream(streamName)
    return application.streamTable[streamName];
* Provides access to the StreamContext Object for a given server-side
* NetConnection hosting a multicast NetStream.
* @param netConnection - A server-side NetConnection.
* @return The associated StreamContext Object; undefined if the passed
*         NetConnection is not indexed to a StreamContext.
function getStreamContextForNetConnection(netConnection)
    return application.netConnTable[netConnection];
* Provides access to the StreamContext Object for a given multicast NetStream.
* @param netStream - A multicast NetStream.
* @return The associated StreamContext Object; undefined if the passed
*         NetStream is not indexed to a StreamContext.
function getStreamContextForMulticastNetStream(netStream)
    return application.mcastNetStreamTable[netStream];
* Provides access to the StreamContext Object for a given NetGroup associated
* with a multicast NetStream.
* @param netGroup - A NetGroup.
* @return The associated StreamContext Object; undefined if the passed
*         NetGroup is not indexed to a StreamContext.
function getStreamContextForNetGroup(netGroup)
    return application.netGroupTable[netGroup];
* Unregisters the StreamContext from the application.
* @param streamContext - The StreamContext Object to unregister.
function unregisterStreamContext(streamContext)
    if (streamContext.netConnection)
        delete application.netConnTable[streamContext.netConnection];
    if (streamContext.mcastNetStream)
        delete application.mcastNetStreamTable[streamContext.mcastNetStream];
    if (streamContext.netGroup)
        delete application.netGroupTable[streamContext.netGroup];
    trace("Unregistered multicast context for source stream: " +
          streamContext.streamName);
// Application callback functions
* Initializes global StreamContext lookup tables.
application.onAppStart = function()
    application.streamTable = {};
    application.netConnTable = {};
    application.mcastNetStreamTable = {};
    application.netGroupTable = {};
* Handles a publish event for the application by validating the request
* and bridging the published stream into a target Flash Group. Invalid
* publish requests are ignored and the publishing client's connection
* is closed.
* @param client - The publishing client.
* @param stream - The published stream.
application.onPublish = function(client, stream)
    //trace("Handling publish request for source stream: " + stream.name);
    var params = parseQueryString(stream.publishQueryString);
    if (!validateStreamParams(params))
        application.disconnect(client);
        return;
    var prevContext = getStreamContextForSourceStream(stream.name);
    if (prevContext)
        forceCloseStreamContext(prevContext);
    // Register source Stream, and kick off the async process that will
    // eventually wire-up the associated multicast NetStream.
    var streamContext = registerStream(client, stream.name, params);
    openMulticastConnection(streamContext);
* Handles an unpublish event for the application by shutting down
* any associated multicast NetStream.
* @param client - The unpublishing client.
* @param stream - The source stream being unpublished.
application.onUnpublish = function(client, stream)
    trace("Handling unpublish request for source stream: " + stream.name);
    var streamContext = getStreamContextForSourceStream(stream.name);
    if (streamContext && (streamContext.state <= STATE_REPUBLISHING))
        destroyStreamContext(streamContext);
// Callback functions for NetConnection and multicast NetStream/NetGroup wiring.
* First step in setting up a republished multicast NetStream; open the loopback
* connection it requires.
* @param streamContext - The StreamContext Object for the publish event.
function openMulticastConnection(streamContext)
    var nc = new NetConnection();
    nc.onStatus = netConnectionStatusHandler;
    streamContext.netConnection = nc;
    updateStreamContextLookups(streamContext);
    streamContext.state = STATE_CONNECTING;
    nc.connect(resetUriProtocol(streamContext.client.uri, "rtmfp"));
* Status event handler for the loopback NetConnection used by the multicast
* NetStream. Advances setup upon successful connection, or triggers or advances
* tear-down as a result of connection loss or an unpublish and clean shutdown.
* @param info - The status info Object.
function netConnectionStatusHandler(info)
    var streamContext = getStreamContextForNetConnection(this);
    trace("Multicast NetConnection Status: " + info.code +
          (streamContext ? ", Source stream: " + streamContext.streamName : ", Not associated with a source stream."));
    if (streamContext)
        switch (info.code)
        case "NetConnection.Connect.Success":
            streamContext.state = STATE_CONNECTED;
            // If event type is Fusion or P2p, wire up a NetGroup for neighbor
            // bootstrapping and maintenance ahead of (re)publishing the stream.
            var type = streamContext.type;
            if (type == TYPE_FUSION || type == TYPE_P2P)
                initNetGroup(streamContext);
            else
                initMulticastNetStream(streamContext);
            break;
        case "NetConnection.Connect.Failed":
        case "NetConnection.Connect.Rejected":
        case "NetConnection.Connect.AppShutdown":
            trace("MULTICAST PUBLISH ERROR: Failed to establish server-side NetConnection for use by multicast NetStream. " +
                  "Status code: " + info.code + ", description: " + info.description + ", Source stream: " +
                  streamContext.streamName);
            streamContext.state = STATE_DISCONNECTED;
            destroyStreamContext(streamContext);
            break;
        case "NetConnection.Connect.Closed":
            if (streamContext.state < STATE_DISCONNECTING)
                trace("MULTICAST PUBLISH ERROR: Unexpected server-side NetConnection close. " +
                     "Status code: " + info.code + ", description: " + info.description + ", Source stream: " +
                     streamContext.streamName);
            streamContext.state = STATE_DISCONNECTED;
            destroyStreamContext(streamContext);
            break;
        default:
            // Ignore.
* Initializes the multicast NetGroup following a successful connection of its
* underlying loopback NetConnection. This hook is optional and only runs for
* event types of Fusion and pure P2P.
* @param streamContext - The StreamContext Object for the multicast publish.
function initNetGroup(streamContext)
    var ng = null;
    try
        ng = new NetGroup(streamContext.netConnection, streamContext.groupspec);
    catch (e)
        trace("MULTICAST PUBLISH ERROR: Failed to construct NetGroup. Error: "
              + e.name + (e.message ? " " + e.message : "") +
              ", Source stream: " + streamContext.streamName);
        destroyStreamContext(streamContext);
        return;
    ng.onStatus = netGroupStatusHandler;
    streamContext.netGroup = ng;
    updateStreamContextLookups(streamContext);
* Status event handler for the multicast NetGroup. Advances to initializing the
* multicast NetStream upon successful NetGroup connect. Otherwise, triggers
* shut down.
* @param info - The status info Object.
function netGroupStatusHandler(info)
    var streamContext = getStreamContextForNetGroup(this);
    trace("Multicast NetGroup Status: " + info.code +
          (streamContext ? ", Source stream: " + streamContext.streamName : ", Not associated with a source stream."))
    if (streamContext)
        switch (info.code)
        case "NetGroup.Connect.Success":
            initMulticastNetStream(streamContext);
            break;
        case "NetGroup.Connect.Failed":
        case "NetGroup.Connect.Rejected":
            trace("MULTICAST PUBLISH ERROR: Failed to connect multicast NetGroup. " +
                  "Status code: " + info.code + ", description: " + info.description +
                  ", Source stream: " + streamContext.streamName);
            destroyStreamContext(streamContext);
            break;
        case "NetGroup.MulticastStream.UnpublishNotify":
            // At this point, multicast publishers will be notified;
            // continue shut down.
            destroyStreamContext(streamContext);
            break;
        default:
            // Ignore.
* Initializes the multicast NetStream following a successful connection of its
* underlying loopback NetConnection.
* @param streamContext - The StreamContext Object for the multicast publish.
function initMulticastNetStream(streamContext)
    var ns = null;
    try
        ns = new NetStream(streamContext.netConnection, streamContext.groupspec);
    catch (e)
        trace("MULTICAST PUBLISH ERROR: Failed to construct multicast NetStream. Error: " +
              e.name + (e.message ? " " + e.message : "") +
              ", Source stream: " + streamContext.streamName);
        destroyStreamContext(streamContext);
        return;
    var type = streamContext.type;
    if (type == TYPE_FUSION || type == TYPE_IP)
var iAddr = (streamContext.interfaceAddress) ? streamContext.interfaceAddress : null;
        try
            trace("Multicast NetStream will publish to IP address: " + streamContext.address +
      " on interface address: " + ((iAddr) ? iAddr : "default") +
                  ", Source stream: " + streamContext.streamName);
            ns.setIPMulticastPublishAddress(streamContext.address, iAddr);
        catch (e2)
            trace("MULTICAST PUBLISH ERROR: Failed to assign IP multicast address and port for publishing. Address: "
                  + streamContext.address + " on interface address: " + ((iAddr) ? iAddr : "default") +
      ", Source stream: " + streamContext.streamName);
            destroyStreamContext(streamContext);
            return;
    ns.onStatus = netStreamStatusHandler;
    streamContext.mcastNetStream = ns;
    updateStreamContextLookups(streamContext);
    streamContext.state = STATE_PUBLISH_PENDING;
* Status event handler for the multicast NetStream. Advances state upon successful
* connect and publish, or upon successful unpublish. Triggers tear-down if we fail
* to attach to a source Stream to republish.
* @param info - The status info Object.
function netStreamStatusHandler(info)
    var streamContext = getStreamContextForMulticastNetStream(this);
    trace("Multicast NetStream Status: " + info.code +
          (streamContext ? ", Source stream: " + streamContext.streamName : ", Not associated with a source stream."))
    if (streamContext)
        switch (info.code)
        case "NetStream.Connect.Success":
            if (!this.attach(Stream.get(streamContext.streamName)))
                trace("MULTICAST PUBLISH ERROR: Failed to attach multicast NetStream to source. Source stream: " +
                      streamContext.streamName);
                destroyStreamContext(streamContext);
    //var stream;
            //stream = Stream.get("liveStream");
                //return;
            }else{
            this.publish(streamContext.streamName, "live");
            break;
        case "NetStream.Publish.Start":
            streamContext.state = STATE_REPUBLISHING;
            break;
        case "NetStream.Unpublish.Success":
            streamContext.state = STATE_UNPUBLISHED;
            // Wait for unpublish notify event if the context has a NetGroup;
            // otherwise continue shut down now.
            if (!streamContext.netGroup)
                destroyStreamContext(streamContext);
                break;
        default:
            // Ignore.
* The common tear-down hook. Other functions that manage or shut down
* the StreamContext Object delegate to this function upon detecting a fatal
* error or during shut down.
* @param streamContext - The StreamContext Object for the source Stream and
*                        (potentially wired-up) multicast NetStream.
function destroyStreamContext(streamContext)
    // Unregister by Stream name immediately; lookups by NetConnection, NetGroup
    // and multicast NetStream remain in place until tear-down is complete.
    delete application.streamTable[streamContext.streamName];
    switch (streamContext.state)
    case STATE_REPUBLISHING:
        streamContext.mcastNetStream.attach(false);
        streamContext.mcastNetStream.publish(false);
        streamContext.state = STATE_UNPUBLISHING;
        return;
    case STATE_CONNECTING:
    case STATE_CONNECTED:
    case STATE_PUBLISH_PENDING:
    case STATE_UNPUBLISHED:
        // Delete status handler callbacks and cleanup in case we arrived here
        // as a result of a force close.
        if (streamContext.netGroup)
            delete streamContext.netGroup.onStatus;
        if (streamContext.mcastNetStream)
            streamContext.mcastNetStream.attach(false);
            delete streamContext.mcastNetStream.onStatus;
        streamContext.netConnection.close();
        streamContext.state = STATE_DISCONNECTING;
        return;
    default:
        // Fall-through.
    // At this point, we either never got to the republishing state or we've
    // proceeded through the clean shut down steps above. Everything for this
    // StreamContext can go away.
    unregisterStreamContext(streamContext);
* Utility function used to force close a StreamContext in the event that we
* start handling a republish of a Source stream before the context for its
* prior incarnation has been torn down.
* @param streamContext - The StreamContext Object for the source Stream.
function forceCloseStreamContext(streamContext)
    trace("Force closing previous multicast context for source stream: " + stream.name);
    prevContext.state = STATE_UNPUBLISHED;
    destroyStreamContext(prevContext);
// Client callback functions
* A no-op. Answers the RPC in the fashion expected by encoders, but the real
* work happens in application.onPublish.
* @param streamName - The name of the stream being published.
Client.prototype.FCPublish = function(streamName)
    this.call("onFCPublish",
              null,
              {code:"NetStream.Publish.Start", description:streamName});
* A no-op. Answers the RPC in the fashion expected by encoders, but the real
* work happens in application.onUnpublish.
* @param streamName - The name of the stream being unpublished.
Client.prototype.FCUnpublish = function(streamName)
    this.call("onFCUnpublish",
              null,
              {code:"NetStream.Unpublish.Success", description:streamName});
* If the client invoker's ip matches what was captured for a currently publishing
* stream, assume it's the same client and reset the stream. Otherwise, ignore.
* @param streamName - The name of the stream being released.
Client.prototype.releaseStream = function(streamName)
    var streamContext = getStreamContextForSourceStream(streamName);
    if (streamContext &&
        (streamContext.client.ip == this.ip) &&
        (streamContext.state <= STATE_REPUBLISHING))
        // Only tear-down an orphaned stream if it's not
        // already shutting down (see state check above).
        destroyStreamContext(streamContext);
// Helper functions
* Validates that a newly published stream has correct metadata (e.g. query
* string parameters) to republish into a Flash Group. This function also
* writes a message to the application log for any validation failures.
* @param params - The quiery string parameters for the source Stream.
* @return true if valid; otherwise false.
function validateStreamParams(params)
    var empty = true;
    for (var param in params)
       empty = false;
       break;
    if (empty)
        trace("MULTICAST PUBLISH ERROR: Stream query string is empty.");
        return false;
    if (!params["fms.multicast.type"])
trace("MULTICAST PUBLISH ERROR: Stream query string does not specify a 'fms.multicast.type'.");
        return false;
    var type = params["fms.multicast.type"];
    if (type != 1 && type != 2 && type != 3)
        trace("MULTICAST PUBLISH ERROR: 'fms.multicast.type' has invalid value: " + type);
        return false;
    if (!params["fms.multicast.groupspec"])
        trace("MULTICAST PUBLISH ERROR: Stream query string does not specify a 'fms.multicast.groupspec'.");
        return false;
    // Fusion and IP require an address:port.
    if ((type == 1 || type == 2) &&
        !params["fms.multicast.address"])
        trace("MULTICAST PUBLISH ERROR: Stream query string does not specify a 'fms.multicast.address'.");
        return false;
    // No obvious validation issues.
    return true;
* Parses the supplied query string, and if valid, returns an Object populated
* with the name-value pairs contained in the query string. The simple processing
* here does not preserve multiple name-value pairings having the same name; the
* last value seen wins. Parameters with no value are mapped to "" (empty String)
* in the returned Object.
* @param queryString - A query string portion of a URI, not including the leading
*                     '?' character.
* @return An Object containing a key-value mapping for each name-value parameter
*         defined in the query string; Object is empty if the query string is
*         invalid.
function parseQueryString(queryString)
    var result = {};
    var decoded = "";
    try
        decoded = decodeURIComponent(queryString);
    catch (e) // Invalid URI component; return empty result.
        return result;
    if (decoded.length)
        var params = decoded.split('&');
        for (var i in params)
            var pair = params[i];
     var sepIndex = pair.indexOf('=');
            if (sepIndex != -1)
                var name = pair.substr(0, sepIndex);
                result[name] = pair.substr(sepIndex + 1);
            else
                result[pair] = "";
    return result;
* Utility function used to swap out the protocol (scheme) portion
* of a given URI with an alternate.
* @param uri - The full URI.
* @param desiredProtocol - The replacement protocol.
* @return The URI with its protocol replaced.
function resetUriProtocol(uri, desiredProtocol)
    var sepIndex = uri.indexOf("://");
    return desiredProtocol + uri.substr(sepIndex);

HELP ME !!! THANKS!!!

Slow streaming over wifi using ipad

Why is streaming over wifi slower than over cellular connection? Other devices don't have the same issue.

generally we all think and expect wifi will be faster than a cell connection. But that will not always be the case. A good uncongested LTE runs pretty fast.
But the wifi should be fast enough that you wouldn't notice any issues unless:
You are using a public wifi spot where the signal is metered. Where I work, they clamp the wifi for guests at 250k.
The wifi cannot run any faster than your internet connection. Is it clean?
Recent stoires here are explaining how verizon and Comcast have been allowing you tube and netflix feeds to become overcongested, in an effort to extract $$ from them for the privilange of sending you the signal.
a good place to start is to get a speed app - like Speed test (there are a bunch in the store) and see what speed your wifi is delivering.
One thing that is almost certain, your wifi is a whole lot cheaper than your cell signal!

HTTP 1.1: Using streams over socket; How ?

Can anyone give me a short example as how to handle streams over a persistent socket-connection ?
I've trouble handling this.
I can't "reget" the stream (create a new input/output stream over an existing socket-connection).
Is there someone who can help me ?
I'm getting confused !!!

Since no one helped I could only try to find out myself:
The problem is I used some example-source that fitted well for HTTP 1.0, but led to erroneous results when applied to HTTP 1.1
It's no problem in HTTP 1.1, but you need to read ALL input (headers and possibly content) before trying to process anything:
From the headers you need to read until an empty line is discovered.... Don't just break on return or newline, this will leave an extra character in the input:
Protocol requires both \r and \n. So you always break 1 char to early when scanning bytes and then concluding on a \r that the line is over.
Then you should possibly read 'contentlength bytes' (I've not tried it out yet) in case of POST.
Flushing is enough to write all data to output.
Open and close can't work. "Regetting" a stream is not possible, so all input for this request must be taken from inputstream before trying to process the next request.

Radio Streaming with FMS (aac, mp3, ogg, wma)

Hi
I use a program that encodes in many audio format (acc, wma,
ogg, mp3, etc) and connects to shoutcast, icecast, windows media
server, live365, to distribute the web radio.
Willing to use FMS as the distribution server, I tried to
send the stream to FMS port but without succes. Online docs doenst
treat the argument.
Is it correct to say that FMS is not set up to accept a
Windows Media, AAC+,MP3 or Ogg incoming stream and redistribute the
radio to swf players?
Best
Jo

I've done a similar setup before for a radio station
(x1fmradio.com)
What we did was setup 2 computers on the studio, one computer
receives the input from console and encodes output to shoutcast and
also outputs audio to the second computer running Flash Media
Encoder 2, which publishes audio to Flash Media Server.
If you want an all-in-one solution I would recommend using a
Digital Rapids system, which is not free, but you only need one
computer and you can publish audio/video to several servers at the
same time, including Flash Media Server.

Archiving live stream at FMS and injecting metadata: VP6 good h264 not

When I record a live stream at FMS, one in which I've injected metadata in my main.asc file, the archived file plays back fine. The metadata plays back too. I'm able to retreive it just fine - if I encode VP6.
If I encode h.264 the file plays back but the metadata does not. The fact that the archived file is created and plays back tells me things are wired correctly. The only thing I changed is the format.
According to FMS docs (http://help.adobe.com/en_US/FlashMediaServer/3.5_SS_ASD/WS5b3ccc516d4fbf351e63e3d11a11afc9 5e-7e42.html#WS5b3ccc516d4fbf351e63e3d11a11afc95e-7f35)
..."The recording format is determined by the filename you pass to the Stream.get()
method."
So my record code looks like the following:
application.onPublish = function(client, stream) {
     trace("onPublish");
     s = Stream.get("mp4:streamname.f4v");
     if(s){
         s.record();
     this.doRepublish(this.nc, stream);
My code that injects the data in to the stream looks like this:
Client.prototype.sendDataEvent = function(data) {
     trace("Call to sendDataEvent...");
     this.newStream = Stream.get("mp4:streamname.f4v");
     this.newStream.send("onTextData",data);
All must be wired correctly because the metadata comes through during the live stream. On play back of the archive though, the metadata doesn't appear to be there.
Any thoughts?
Thanks

My apologies on the s.play() confusion. I had been trying different versions of the code and posted the one without it.
Whether I include s.play() or not the file gets created. Here are the various versions of the onPublish() function I've tried (differences in red):
1.
application.onPublish = function(client, stream) {
    trace("onPublish");
    s = Stream.get("mp4:streamname.f4v");
    if(s){
        s.record();
        s.play("mp4:streamname.f4v");
    this.doRepublish(this.nc, stream);
2.
application.onPublish = function(client, stream) {
    trace("onPublish");
    s = Stream.get("mp4:streamname.f4v");
    if(s){
        s.record();
        s.play(stream);
    this.doRepublish(this.nc, stream);
3.
application.onPublish = function(client, stream) {
     trace("onPublish");
     s = Stream.get("mp4:streamname.f4v");
     if(s){
         s.record();
     this.doRepublish(this.nc, stream);
All produce the same result - an archived file called mp4:streamname.f4v in my streams folder. This file plays back fine but does not play back the commands.
On your other question, about things working fine for VP6, it works fine for FLV. A file called streamname.flv is produced. This file plays back fine and does indeed play back commands baked into the file as well. This is what makes me believe the code is not the problem. If it works perfectly for one format, there would seem to be very little I could do in my code to break things for the other.
Can you try this using the record() code snippets in the live docs Stream.record() section?
http://help.adobe.com/en_US/FlashMediaServer/3.5_SS_ASD/WS5b3ccc516d4fbf351e63e3d11a11afc9 5e-7e42.html#WS5b3ccc516d4fbf351e63e3d11a11afc95e-7f35
All you'd need is the code snippets there to record your live stream and another server side function to inject commands into that live stream. Here is that function:
Client.prototype.sendDataEvent = function(data) {
    trace("Call to sendDataEvent...");
    this.newStream = Stream.get("mp4:streamname.f4v");
    this.newStream.send("onTextData",data);
Do something simple like call onTextData and pass some text in the data parameter. Then on the client side viewer, handle the onTextData method. It will receive the text. Display it in a text area or something.
If you record while injecting this text into your stream, the text should display on playback of the archived file. It will if you encode VP6/FLV, but not if you encode H.264/F4V.
Let me know what you discover.

Publish Live stream to FMS on RTMPE protocol

Hi,
I am trying to publish Live Stream to FMS using FMLE or third party encoders.
Is it possible to have RTMPE or RTMPTE protocol used between encoder and FMS?
Very urgent.
thanks,
Pooja Jain

FMLE can only publish via rtmp or rtmpt.

Playback of low bitrate flv or f4v from live stream in FMS causes player buffer to empty

We are experiencing a consistent issue when playing a low bitrate (300kbps or less) flv in a live stream from FMS. Basically, the player will will start off with the appropriate buffer, say 5 seconds, then begin dropping until it empties out, and will have to rebuffer. We've tried with a variety of flv and f4v files, all that are 300kbps or less, and we consistently get the issue. Is this something Adobe can investigate in FMS? Or are there any suggestions on how we can get around the issue?

hey, i got the similar problem, logging like this
2012-11-12
18:50:12
23434
(e)2661034
Connect failed ( , 5779212 ) : Connect failed: Connection refused (111)
2012-11-12
18:50:54
23434
(e)2661034
Connect failed ( , 5779212 ) : Connect failed: Connection refused (111)
2012-11-12
18:51:36
23434
(e)2661034
Connect failed ( , 1166880400 ) : Connect failed: Connection refused (111)
2012-11-12
18:54:14
23434
(e)2661034
Connect failed ( , 1175301776 ) : Connect failed: Connection refused (111)
2012-11-12
18:54:55
23434
(e)2661034
Connect failed ( , 1164775056 ) : Connect failed: Connection refused (111)
2012-11-12
18:55:37
23434
(e)2661034
Connect failed ( , 16 ) : Connect failed: Connection refused (111)
2012-11-12
19:13:08
23434
(e)2661034
Connect failed ( , 1158459024 ) : Connect failed: Connection refused (111)
it seems that the port number is invalid, but we never use such ports.

Streaming over HTTP

I'm new to streaming, so hopefully this is a quick answer
question.....due to firewall restrictions I would need to STREAM
via HTTP protocol over (80)....I can't use RTMPT (which I was able
to get working) because of protocol restrictions.....however, all
the documentation keeps hinting that you can only progressive
download via HTTP...is this true?
However, other part of the doco say "you can stream via HTTP
if you have APACHE installed". My assumption was that all this was
doing was allowing Apache to serve the http "pages" and progressive
download the files....so, long story short, can a file be streamed
using FMIS over HTTP? Thanks for any help in advance.....

No... I think the docs are just using the term "streaming" so
the author didn't have to go into a long explanation of progressive
video (to save the non-technical users from information overload
maybe). You can't truly stream over HTTP. All HTTP flv delivery is
progressive.
That said, you can deliver a streaming-like experience using
an HTTP application server. See the following:
http://flashcomguru.com/index.cfm/2005/11/2/Streaming-flv-video-via-PHP-take-two

IPhone HE-AAC Streaming over Mobile Network (3G)

Developed an internet radio streamer using utilizing the html5 audio tags with jQuery and with a flash fall back for unsupported browsers, streaming through an icecast2 server. Upon testing the player on the iPhone Safari (iOS 5.0.1), we ran into a very peculiar issue.
When the iPhone is connected to WiFi, it streams perfectly using the HE-AAC V2 stream @ 64kbps 44.1kHz (the preferred codec for apple products). However, when the iPhone is connected to the 3G mobile network (ATT and Verizon), it "stutters/buffers" or stops streaming for 1-2 secs every 1-2 minutes (does not stop streaming completely). The troubling thing is when the iPhone is forced to use a separate MP3 stream at the same bit rate, it does not have this issue and works very well on 3G.

Hi Lawrence,
Thanks for the fast response. I'm confused as to how AAC requires higher bandwidth over MP3 when it can produce higher quality audio at lower bit rates therefore requiring less bandwidth to stream over 3G. Are you referring to the bandwidth of the audio signal itself (at the codec level)?

Bought a Winegard indoor HDTV antenna for streaming over-the-air TV. Will my Apple TV work

FlatWave Mini
FlatWave
I Am considering cutting my cable service and have bought a Winegard indoor HDTV wall mount antenna for streaming over-the air tv? I would appreciate an advice you might give me on this project. Will my Apple TV work with this setup? Thanks so much.

appetv is a media box not a OTA related product in any way
it use the LAN network to play shared media from your computer
and if it has an Internet connection it offer a range of Internet streaming services
read more
http://www.apple.com/appletv/

Recording Live Streams on FMS remotely

Hi,
We're using FMSS 3 to stream live feeds from cameras.
However, we'd also like to have the ability to (via an
administration site) record these live streams and allow the user
to view pre-recorded streams instead of the live ones.
Does anyone know of an example of how I can tell FMS to start
recording a stream (via a web service or AS), and then how to stop
it? Just for clarification - we don't want FMS to record a stream
from the user's own camera. We want to record the live streams that
are already streaming on FMS.
Thanks,
Filip Stanek
bloodforge.com

you can creat an app folder in fms folder which is inside of
ur setup folder,
for details u can mail at [email protected]

Will ipad allow higher quality video streaming over 4G?

Will there be improved video quality on youtube and other video streaming on 4G compared to existing 3G connctions? The ipad appears to dumb down video streaming in 3G compared to streaming the same thing on wifi. It is often highly pixelated and blocky, Will the new ipad allow higher quality video streaming over 4G, i.e. the same quality as wi-fi?

The YouTube app is made by Google. Any suggestions you have about that app should be directed to them.

RTP Streaming over the internet

Having some problems streaming over the internet - probably because im doing it wrong.
I can stream over a network fine using Transmit2.java.
But when i try over the internet cant pick up the stream.
Im using www.whatismyip.com to get the internet IP of the 2 computers im trying to stream to and from - and using these in the code, but nothing happens.
Help?

natdeamer wrote:
Having some problems streaming over the internet - probably because im doing it wrong.That's correct, you're doing it wrong.
Im using www.whatismyip.com to get the internet IP of the 2 computers im trying to stream to and from - and using these in the code, but nothing happens.99% of the time, your public IP actually addresses your router, rather than your computer. That means your computer is not publically addressably by it's IP address alone. You'll need to do something called a "NAT holepunch", which you can look up online. Also, I've included two links to discussions I've had with people about the same issue.
[http://forums.sun.com/thread.jspa?forumID=28&threadID=5355413]
[http://forums.sun.com/thread.jspa?forumID=28&threadID=5356672]

App-V 5.0 Streaming over SCCM 2012 SP1 - High Availability / Load Balancig

Hello Anybody,
the default App-V 5.0 Streaming (SharedContentStoreMode = on) Deployment over SCCM belongs to a HTTP-Streaming over http:\\SCCM-Server\... . The whole content flows from SCCM to the App-V-Client. Is it possible to create there a high availability solution?
Yes, we can set a second distribution point. But in th App-V-Client are always only one Distribution Source.
Is it possible to set there an clustered adress of an other IIS? Is it possible to change the publishing Distribution Source with an SMB-Path to File-Cluster? Is there a trick with Source-Root-Parameter in App-V-Client? Or are ther anything else to create
a high availibility App-V-Streaming-Solution?
Yes, with App-V-Management-Server there is a high availability solution. - But we have only SCCM-Infrastruktur for App-V-Distribution.
Thank you, best regards
Daniel

Daniel, do you found solution?

Streaming over 2 FMS

Similar Messages

Maybe you are looking for