Stream class

The Stream class lets you manage or republish streams in an application. A Stream object is the server-side equivalent of the client-side NetStream object.

You can’t attach audio or video sources to a Stream object; you can only play and manage existing streams. Use the Stream class to shuffle existing streams in a playlist, pull streams from other servers, and control access to streams. You can also record streams published by a client and record data streams such as log files.

A stream is a one-way connection between a client running Flash Player and a server running Adobe Media Server. A stream can also be a connection between two servers running Adobe Media Server. You can create a stream in Server-Side ActionScript by calling Stream.get(). A client can access multiple streams at the same time, and there can be hundreds or thousands of Stream objects active at the same time. You can record in FLV and F4V format.

Streams can contain ActionScript data. Call the Stream.send() method to add data to a stream. You can extract this data without waiting for a stream to play in real time, such as when you’re creating a log file. You can also use it to add metadata to a stream.

Availability

Flash Communication Server 1

Property summary

Property

Description

Read-only; indicates how long to buffer messages before a stream is played, in seconds.

Read-write; indicates whether 608-708 captions are extracted from the H264 NALU and converted to onCaptionInfo AMF message.

Read-only; the maximum time, in milliseconds, that the live queue can delay transmitting messages.

Read-only; the maximum size, in bytes, that the live queue can grow to before transmitting the messages it contains.

Read-only; contains a unique string associated with a live stream.

Read-only; the query string specified in the stream path when the stream was published.

A boolean value that controls whether the server receives audio (true) or not (false).

A boolean value that controls whether the server receives video (true) or not (false).

Read-only; the number of seconds the stream has been playing. This value is the timestamp of the latest frame that flowed out of the stream.

Method summary

Method

Description

Deletes a recorded file from the server.

Unlinks and cleans up a stream resource.

Flushes a stream.

Static; returns a reference to a Stream object.

Returns an object containing the metadata for the named stream or video file.

Static; returns the length of a recorded stream in seconds.

Controls the data source of a stream with an optional start time, duration, and reset flag to flush any previously playing stream.

Records all the data passing through a Stream object and creates a file of the recorded stream.

Event handler summary

Event handler

Description

Invoked every time the status of a Stream object changes.

Stream.bufferTime

 myStream.bufferTime

Read-only; indicates how long to buffer messages before a stream plays, in seconds. This property applies only when playing a stream from a remote server or when playing a recorded stream locally. Call Stream.setBufferTime() to set the bufferTime property.

A message is data that is sent back and forth between Adobe Media Server and Flash Player. The data is divided into small packets (messages), and each message has a type (audio, video, or data).

Availability

Flash Communication Server 1

Stream.clear()

 myStream.clear()

Deletes a recorded FLV or F4V file from the server.

Availability

Flash Communication Server 1

Returns

A boolean value of true if the call succeeds; otherwise, false.

Example

The following example deletes a recorded stream called playlist.flv. Before the stream is deleted, the example defines an onStatus() handler that uses two information object error codes, NetStream.Clear.Success and NetStream.Clear.Failed, to send status messages to the application log file and the Live Log panel in the Administration Console.

 s = Stream.get("playlist"); 
 if (s){ 
     s.onStatus = function(info){ 
         if(info.code == "NetStream.Clear.Success"){ 
             trace("Stream cleared successfully."); 
         } 
         if(info.code == "NetStream.Clear.Failed"){ 
             trace("Failed to clear stream."); 
         } 
     }; 
     s.clear(); 
 }

Stream.destroy()

 Stream.destroy()

Unlinks and cleans up an instance of the Stream class. When a call to Stream.destroy() destroys a stream, the server stops any NetStream playing the stream and logs the code 440 in the Access log. Publishers are disconnected and recordings are stopped.

Instances of the Stream class are considered live streams. These streams are used as proxy streams, for server-to-sever streaming, direct client playback, and recordings. It can be difficult to determine whether you’ve properly released a live stream that has finished playing. Call Stream.destroy() to unlink and clean up a stream resource.

Availability

Flash Meda Server 3.5.4

Returns

A boolean value of true if the call succeeds.

A boolean value of false if the stream is not found. This case occurs only if the Stream reference has already been destroyed or if an error has occurred.

Example

The following example destroys a stream called streamA:

// Get a stream. 
streamA = Stream.get("clientStream1"); 
// Destroy the stream. 
Stream.destroy(streamA);

Stream.flush()

 myStream.flush()

Flushes a stream. If the stream is used for recording, the flush() method writes the contents of the buffer associated with the stream to the recorded file.

It is highly recommended that you call flush() on a stream that contains only data. Synchronization problems can occur if you call the flush() method on a stream that contains data and either audio, video, or both.

Availability

Flash Media Server 2

Returns

A boolean value of true if the buffer was successfully flushed; otherwise, false.

Example

The following example flushes the myStream stream:

 // Set up the server stream. 
 application.videoStream = Stream.get("aVideo"); 
  
 if (application.videoStream){ 
     application.videoStream.record(); 
     application.videoStream.send("test", "hello world"); 
     application.videoStream.flush(); 
 }

Stream.generateCCInfo

myStream.generateCCInfo

A Boolean value that indicates whether AMS extracts 608-708 captions from the H264 NALU and constructs corresponding onCaptionInfo AMF messages for use in HDS live and RTMP streams. This property overrides the GenerateCCInfo setting in the Application.xml file. The default value is false. A value of true, will enable closed captioning.

Note:

If your video streams are relayed from AMS server to AMS server, only the ingest server can generate captions. Setting Stream.generateCCInfo to true for non-ingest servers has no effect.

For more information, see StreamManager.

Availability

Adobe Media Server 5.0.1

Stream.get()

 Stream.get(name)

Static; returns a reference to a Stream object. If the requested object is not found, a new instance is created. After you call the Stream.get() method, you can call the Stream.record() and Stream.play() methods to publish and record streams.

You can publish and record streams in FLV, F4V, or F4F format. F4F format is for HTTP Dynamic Streaming.

Specify the format in the name parameter you pass to the Stream.get() method. To publish in FLV format, specify only the stream name, for example, Stream.get("footballGame"). To publish in F4V format, prefix the stream name with mp4:. You can optionally specify the file extension, for example, the following code is all legal:

Stream.get("mp4:footballGame.f4v") 
Stream.get("mp4:footballGame.mp4") 
Stream.get("mp4:footballGame")

F4V files behave differently than FLV files. To create a file with a file extension, you must specify a file extension. If you don’t specify a file extension, the file created will not have a file extension.

To record one stream, create a stream with that format when you call Stream.get(). For example, if you want to record the stream “myHomeMovie.mp4”, use code like the following:s = Stream.get("mp4:streamName.mp4"); if(s){ s.record(); s.play("mp4:myHomeMovie.mp4"); }

To record in F4F format for HTTP Dynamic Streaming, do the following:

s = Stream.get("mp4:streamName.mp4"); 
if(s){ 
    s.record(); 
    s.play("mp4:myHomeMovie.mp4"); 
}
s = Stream.get("f4f:streamName.f4f"); 
if(s){ 
    s.record(); 
    s.play("mp4:myHomeMovie.mp4"); 
}

When you add streams to the end of an existing file to make a playlist, you might add streams with different settings and formats. If you record a file in FLV format, the server records the streams encoded with On2 VP6 and ignores streams encoded with H.264. If you record a file in F4V format, you can append any type of content to the stream, including FLV, MP3, MP4, F4V, and live streams.

Note:

To play or edit F4V files recorded by Adobe Media Server in other tools, use the Adobe Media Server F4V Post Processor tool. The tool is available at www.adobe.com/go/ams_tools.

Availability

Flash Communication Server 1

Parameters

name

A string specifying the name of a Stream object.

Returns

A Stream object if the call is successful; otherwise, null.

Examples

The following example publishes and records a video in F4V format. The stream contains 2 videos, one in FLV format, and one in MP4 format.

var s=Stream.get(“mp4:streamName.f4v”); 
if(s) { 
    s.record(); 
    s.play("sample",-2,-1); 
    s.play("mp4:sample_mp4.mp4",-2,-1,false); 
}

Stream.getOnMetaData()

 Stream.getOnMetaData(name)

Static; returns an object containing the metadata for the named stream or video file. The object contains one property for each metadata item. The Flash Video Exporter utility (version 1.1 or later) embeds video duration, creation date, data rates, and other information into the video file.

Availability

Flash Media Server 2

Parameter

name

A string indicating the name of a recorded stream, such as "myVideo". For FLV files, pass the name without a file extension or prefix: "myVideo". For F4V files, pass the name with the prefix mp4: "mp4:myVideo". Append a file extension if the F4V file has a file extension.

Returns

An Object containing the metadata as properties.

Example

The following example lists the properties and values for the metadata for the recorded stream myVideo.flv:

 var infoObject = Stream.getOnMetaData("myVideo"); 
  
 trace("Metadata for myVideo.flv:"); 
  
 for(i in infoObject){ 
     trace(i + " = " + infoObject[i]); 
 }

Stream.length()

<<This
topic needs an additional sample explaining valid strings. SS 7/22>> Stream.length(name[, virtualKey])

Static; returns the length of a recorded file in seconds. If the requested file is not found, the return value is 0.

Availability

Flash Communication Server 1

Parameters

name

A string indicating the name of a recorded stream. To get the length of an MP3 file, precede the name of the file with mp3: (for example, "mp3:beethoven").

virtualKey

A string indicating a key value. Starting with Adobe Media Server 2, stream names are not always unique. You can create multiple streams with the same name and place them in different physical directories. Then, use the VirtualDirectory section and VirtualKeys section of the Vhost.xml file to direct clients to the appropriate stream. The Stream.length() method is not associated with a client, but connects to a stream on the server. As a result, you may need to specify a virtual key to identify the correct stream. For more information about keys, see Client.virtualKey. This parameter is optional.

Returns

A number.

Example

The following example gets the length of the recorded stream file myVideo and assigns it to the variable streamLen:

 function onProcessCmd(cmd){ 
     var streamLen = Stream.length("myVideo"); 
     trace("Length: " + streamLen + "\n"); 
 }

The following example gets the length of the MP3 file beethoven.mp3 and assigns it to the variable streamLen:

 function onProcessCmd(cmd){ 
     var streamLen = Stream.length("mp3:beethoven"); 
     trace("Length: " + streamLen + "\n"); 
 }

The following example gets the length of the MP4 file beethoven.mp4 and assigns it to the variable streamLen:

 function onProcessCmd(cmd){ 
     var streamLen = Stream.length("mp4:beethoven"); 
     trace("Length: " + streamLen + "\n"); 
 }

Stream.liveEvent

 stream.liveEvent

A string indicating the name of an HTTP Dynamic Streaming live event. For more information, see Using Adobe HTTP Dynamic Streaming .

Availability

Flash Media Server 3.8

Example

The following example sets the name of a live event to “myevent”:

application.onPublish = function(clientObj, streamObj){ 
    livestream = Stream.get("f4f:livestream"); 
    livestream.liveEvent = "myevent"; 
    livestream.record("record"); 
    livestream.play(streamObj.name, -1); 
}

Stream.maxQueueDelay

myStream.maxQueueDelay

The maximum time, in milliseconds, that the live queue can delay transmitting messages.

Availability

Flash Media Server 3.5

Example

For an example, see the Stream.publishQueryString property.

See also

Stream.maxQueueSize

myStream.maxQueueSize

The maximum size, in bytes, that the live queue can grow to before transmitting the messages it contains.

Availability

Flash Media Server 3.5

Example

For an example, see the Stream.publishQueryString property.

See also

Stream.name

 myStream.name

Read-only; contains a unique string associated with a live stream. You can use this property as an index to find a stream within an application.

Availability

Flash Communication Server 1

Example

The following function takes a Stream object as a parameter and returns the name of the stream:

 function getStreamName(myStream){ 
     return myStream.name; 
 }

Stream.onPlayStatus()

myStream.onPlayStatus = function(infoObject) {}

Called to provide information about playing a stream.

You can trigger actions when a Stream object has switched from one stream to another in a playlist (as indicated by the information object NetStream.Play.Switch). You can also trigger actions when a Stream object has played to the end (as indicated by the information object NetStream.Play.Complete). To respond to this event, you must create a function to process the information object sent by the server.

Availability

Flash Media Server 2; Flash Player 6.

Parameters

infoObject

An object with code and level properties that provide information about the play status of a Stream object, as follows:

code property

level property

Meaning

NetStream.Play.Complete

status

Playback has completed.

NetStream.Play.TransitionComplete

status

The subscriber is switching to a new stream as a result of a successful NetStream.play2() call. For Flash Player 10 and later and Flash Media Server 3.5 and later.

Adobe Media Server dispatches this event when a transition to a new stream occurs. Prior to this event, the server dispatches an onStatus event with a code of NetStream.Play.Transition to indicate that it processed the command to switch streams.

NetStream.Play.Switch

status

The subscriber is switching from one stream to another in a playlist.

Stream.onStatus()

 myStream.onStatus = function([infoObject]) {}

Invoked every time the status of a Stream object changes. For example, if you play a file in a stream, Stream.onStatus() is invoked. Use Stream.onStatus() to check when play starts and ends, when recording starts, and so on.

Availability

Flash Communication Server 1

Parameters

infoObject

An Object with code and level properties that contain information about a stream. This parameter is optional, but it is usually used. The Stream information object contains the following properties:

Property

Meaning

code

A string identifying the event that occurred.

description

Detailed information about the code. Not every information object includes this property.

details

The stream name.

level

A string indicating the severity of the event.

The following table describes the code and level property values:

Code property

Level property

Description

NetStream.Clear.Failed

error

A call to application.clearStreams() failed to delete a stream.

NetStream.Clear.Success

status

A call to application.clearStreams() successfully deleted a stream.

NetStream.Failed

error

An attempt to use a Stream method failed.

NetStream.MulticastStream.Reset

status

Dispatched when the low-level multicast stream indicates a reset point. This only happens on the subscribe-side of the stream.

NetStream.Play.Failed

error

A call to Stream.play() failed. In Server-Side ActionScript, you can use the NetStream class to publish a stream to a multicast group. You cannot use the NetStream class to play a stream being published into a group.

NetStream.Play.InsufficientBW

warning

Data is playing behind the normal speed.

NetStream.Play.Start

status

Play was started.

NetStream.Play.StreamNotFound

error

An attempt was made to play a stream that does not exist.

NetStream.Play.Stop

status

Play was stopped.

NetStream.Play.Reset

status

A playlist was reset.

NetStream.Play.PublishNotify

status

The initial publish operation to a stream was successful. This message is sent to all subscribers.

NetStream.Play.UnpublishNotify

status

An unpublish operation from a stream was successful. This message is sent to all subscribers.

NetStream.Publish.BadName

error

An attempt was made to publish a stream that is already being published by someone else.

NetStream.Publish.Start

status

Publishing was started.

NetStream.Record.Failed

error

An attempt to record a stream failed.

NetStream.Record.NoAccess

error

An attempt was made to record a read-only stream.

NetStream.Record.Start

status

Recording was started.

NetStream.Record.Stop

status

Recording was stopped.

NetStream.Unpublish.Success

status

A stream has stopped publishing.

Example

The following server-side code attempts to delete a given stream and traces the resulting return code:

 Client.prototype.delStream = function(streamName){ 
     trace("*** deleting stream: " + streamName); 
     s = Stream.get(“streamName”); 
     if (s) { 
         s.onStatus = function(info){ 
             if (info.code == "NetStream.Clear.Success")    { 
                 trace("*** Stream " + streamName + "deleted."); 
             } 
             if (info.code == "NetStream.Clear.Failure")    { 
                 trace("*** Failure to delete stream " + streamName); 
             } 
         }; 
         s.clear(); 
     } 
 }

Stream.play()

 myStream.play(streamName, [startTime, length, reset, remoteConnection, virtualKey])

Controls the data source of a stream with an optional start time, duration, and reset flag to flush any previously playing stream. Call play() to do the following:

  • Chain streams between servers.

  • Create a hub to switch between live streams and recorded streams.

  • Combine streams into a recorded stream.

You can combine multiple streams to create a playlist for clients. The Stream.play() method behaves differently from the NetStream.play() method on the client side. A server-side call to Stream.play() is similar to a client-side call to NetStream.publish(); it controls the source of data coming into a stream. When you call Stream.play() on the server, the server becomes the publisher. Because the server has higher priority than the client, the client is forced to unpublish from the stream if the server calls a play() method on the same stream.

If any recorded streams are included in a server playlist, you cannot play the server playlist stream as a live stream.

Note:

A stream that plays from a remote server by means of the NetConnection object is considered a live stream.

You do not need to wait for "NetStatus.Connection.Success" when connecting to another Adobe Media Server from Server-Side Actionscript. The server waits for the connection to complete before it attempts to use the connection for Stream.play(). However, you may want to monitor the NetStatusEvent so that you can handle a failed connection.

To delete a Stream object, use the delete operator to mark the stream for deletion. The script engine deletes the object during its garbage collection routine.

 // Initialize the Stream object. 
 s = stream.get("foo"); 
 // Play the stream. 
 s.play("name", p1, ... pN);       
 // Stop the stream. 
 s.play(false);                                     
 // Mark the Stream object for deletion during server garbage routine. 
 delete s;

Availability

Flash Communication Server 1

Parameters

streamName

A string indicating the name of the stream. Use the following syntax:

File format

Syntax

Example

FLV

Specify the stream name as a string, without a filename extension.

s.play("fileName")

MP3

Specify the stream name as a string, with prefix mp3: or id3:, respectively, and without a filename extension.

s.play("mp3:fileName")

s.play("id3:fileName")

MPEG-4-based files (such as F4V, MP4)

Specify the stream name as a string with the prefix mp4:. Use a file extension if the file on the server has a file extension. The prefix indicates to the server that the file is in the MPEG-4 Part 12 container format.

s.play("mp4:fileName")

s.play("mp4:fileName.mp4")

s.play("mp4:fileName.f4v")

startTime

A number indicating the playback start time, in seconds. If no value is specified, the value is -2. If startTime is -2, the server tries to play a live stream with the name specified in streamName. If no live stream is available, the server tries to play a recorded stream with the name specified in streamName. If no recorded stream is found, the server creates a live stream with the name specified in streamName and waits for someone to publish to that stream. If startTime is -1, the server attempts to play a live stream with the name specified in streamName and waits for a publisher if no specified live stream is available. If startTime is greater than or equal to 0, the server plays the recorded stream with the name specified in streamName, starting from the time given. If no recorded stream is found, the play() method is ignored. If a negative value other than -1 is specified, the server interprets it as -2. This parameter is optional.

length

A number indicating the length of play, in seconds. For a live stream, a value of -1 plays the stream as long as the stream exists. Any positive value plays the stream for the corresponding number of seconds. For a recorded stream, a value of -1 plays the entire file, and a value of 0 returns the first video frame. Any positive number plays the stream for the corresponding number of seconds. By default, the value is -1. This parameter is optional.

reset

A boolean value, or number, that flushes the playing stream. If reset is false (0), the server maintains a playlist, and each call to Stream.play() is appended to the end of the playlist so that the next play does not start until the previous play finishes. You can use this technique to create a dynamic playlist. If reset is true (1), any playing stream stops, and the playlist is reset. By default, the value is true.

You can also specify a number value of 2 or 3 for the reset parameter, which is useful when playing recorded stream files that contain message data. These values are analogous to false (0) and true (1), respectively: a value of 2 maintains a playlist, and a value of 3 resets the playlist. However, the difference is that specifying either 2 or 3 for reset returns all messages in the specified recorded stream at once, rather than at the intervals at which the messages were originally recorded (the default behavior).

remoteConnection

A NetConnection object that is used to connect to a remote server. If this parameter is provided, the requested stream plays from the remote server. This is an optional parameter.

virtualKey

A string indicating a key value. Starting with Adobe Media Server 2, stream names are not always unique; you can create multiple streams with the same name, place them in different physical directories, and use the VirtualDirectory section and VirtualKeys section of the Vhost.xml file to direct clients to the appropriate stream. Because the Stream.length() method is not associated with a client, but connects to a stream on the server, you may need to specify a virtual key to identify the correct stream. For more information about keys, see Client.virtualKey. This is an optional parameter.

Returns

A boolean value: true if the call is accepted by the server; otherwise, false. If the server fails to find the stream, or if an error occurs, the Stream.play() method can fail. To get information about the Stream.play() method, define a Stream.onStatus() handler.

If the streamName parameter is false, the stream stops playing. A boolean value of true is returned if the stop succeeds; otherwise, false.

Example

The following example shows how streams can be chained between servers:

 application.myRemoteConn = new NetConnection(); 
 application.myRemoteConn.onStatus = function(info){ 
     trace("Connection to remote server status " + info.code + "\n"); 
     // Tell all the clients. 
     for (var i = 0; i < application.clients.length; i++){ 
         application.clients[i].call("onServerStatus", null,  
         info.code, info.description); 
     } 
 }; 
 // Use the NetConnection object to connect to a remote server. 
 application.myRemoteConn.connect(rtmp://movie.com/movieApp); 
 // Set up the server stream. 
 application.myStream = Stream.get("foo"); 
 if (application.myStream){ 
     application.myStream.play("Movie1", 0, -1, true, application.myRemoteConn); 
 }

The following example shows how to use Stream.play() as a hub to switch between live streams and recorded streams:

 // Set up the server stream. 
 application.myStream = Stream.get("foo"); 
 if (application.myStream){ 
     // This server stream plays "Live1",  
     // "Record1", and "Live2" for 5 seconds each. 
     application.myStream.play("Live1", -1, 5); 
     application.myStream.play("Record1", 0, 5, false); 
     application.myStream.play("Live2", -1, 5, false);  
 }

The following example combines different streams into a recorded stream:

 // Set up the server stream. 
 application.myStream = Stream.get("foo"); 
 if (application.myStream){ 
     // Like the previous example, this server stream  
     // plays "Live1", "Record1", and "Live2"  
     // for 5 seconds each. But this time,  
     // all the data will be recorded to a recorded stream "foo". 
     application.myStream.record(); 
     application.myStream.play("Live1", -1, 5); 
     application.myStream.play("Record1", 0, 5, false); 
     application.myStream.play("Live2", -1, 5, false); 
 }

The following example calls Stream.play() to stop playing the stream foo:

 application.myStream.play(false);

The following example creates a playlist of three MP3 files (beethoven.mp3, mozart.mp3, and chopin.mp3) and plays each file in turn over the live stream foo:

 application.myStream = Stream.get("foo"); 
 if(application.myStream) { 
     application.myStream.play("mp3:beethoven", 0); 
     application.myStream.play("mp3:mozart", 0, false); 
     application.myStream.play("mp3:chopin.mp3", 0, false); 
     application.myStream.play("mp4:file1.mp4", -1, 5, false); 
 }

The following example plays F4V files:

 application.myStream = Stream.get("foo"); 
 if(application.myStream) { 
     application.myStream.play("mp4:beethoven", 0); 
     application.myStream.play("mp4:mozart", 0, false); 
 }

In the following example, data messages in the recorded stream file log.flv are returned at the intervals at which they were originally recorded:

 application.myStream = Stream.get("data"); 
 if (application.myStream) { 
     application.myStream.play("log", 0, -1); 
 }

In the following example, data messages in the recorded stream file log.flv are returned all at once, rather than at the intervals at which they were originally recorded:

 application.myStream = Stream.get("data"); 
 if (application.myStream) { 
     application.myStream.play("log", 0, -1, 2); 
 }

A server-side stream cannot subscribe to itself. For example, the following code is invalid:

 // Client-side code 
 var ns = new NetStream 
 ns.publish("TestStream"); 
  
 // Server-side code 
 st = Stream.get("TestStream"); 
 st.play("TestStream");

Stream.playFromGroup()

 myStream.playFromGroup(ingest)

Plays an multicast stream that was ingested into a NetGroup.

For information about ingesting a multicast stream, see NetGroup.getMulticastStreamIngest().

To get information about the Stream.playFromGroup() method, define a Stream.onStatus() handler.

If the server fails to find the stream, or if an error occurs, the Stream.playFromGroup() method can fail.

Availability

Flash Media Server 4.5

Parameters

ingest

A MulticastStreamIngest object that is ingesting a multicast stream from a source Flash group, or a boolean value of false to stop playback from a group.

Returns

A boolean value: true if the call is accepted by the server; otherwise, false.

If the ingest parameter is false, the stream stops playing. A boolean value of true is returned if the stop succeeds; otherwise, false.

Example

The following example shows how streams can be chained between servers:

 application.myRemoteConn = new NetConnection(); 
 application.myRemoteConn.onStatus = function(info){ 
     trace("Connection to remote server status " + info.code + "\n"); 
     // Tell all the clients. 
     for (var i = 0; i < application.clients.length; i++){ 
         application.clients[i].call("onServerStatus", null,  
         info.code, info.description); 
     } 
 }; 
 // Use the NetConnection object to connect to a remote server. 
 application.myRemoteConn.connect(rtmp://movie.com/movieApp); 
 // Set up the server stream. 
 application.myStream = Stream.get("foo"); 
 if (application.myStream){ 
     application.myStream.play("Movie1", 0, -1, true, application.myRemoteConn); 
 }

The following example shows how to use Stream.play() as a hub to switch between live streams and recorded streams:

 // Set up the server stream. 
 application.myStream = Stream.get("foo"); 
 if (application.myStream){ 
     // This server stream plays "Live1",  
     // "Record1", and "Live2" for 5 seconds each. 
     application.myStream.play("Live1", -1, 5); 
     application.myStream.play("Record1", 0, 5, false); 
     application.myStream.play("Live2", -1, 5, false);  
 }

The following example combines different streams into a recorded stream:

 // Set up the server stream. 
 application.myStream = Stream.get("foo"); 
 if (application.myStream){ 
     // Like the previous example, this server stream  
     // plays "Live1", "Record1", and "Live2"  
     // for 5 seconds each. But this time,  
     // all the data will be recorded to a recorded stream "foo". 
     application.myStream.record(); 
     application.myStream.play("Live1", -1, 5); 
     application.myStream.play("Record1", 0, 5, false); 
     application.myStream.play("Live2", -1, 5, false); 
 }

The following example calls Stream.play() to stop playing the stream foo:

 application.myStream.play(false);

The following example creates a playlist of three MP3 files (beethoven.mp3, mozart.mp3, and chopin.mp3) and plays each file in turn over the live stream foo:

 application.myStream = Stream.get("foo"); 
 if(application.myStream) { 
     application.myStream.play("mp3:beethoven", 0); 
     application.myStream.play("mp3:mozart", 0, false); 
     application.myStream.play("mp3:chopin.mp3", 0, false); 
     application.myStream.play("mp4:file1.mp4", -1, 5, false); 
 }

The following example plays F4V files:

 application.myStream = Stream.get("foo"); 
 if(application.myStream) { 
     application.myStream.play("mp4:beethoven", 0); 
     application.myStream.play("mp4:mozart", 0, false); 
 }

In the following example, data messages in the recorded stream file log.flv are returned at the intervals at which they were originally recorded:

 application.myStream = Stream.get("data"); 
 if (application.myStream) { 
     application.myStream.play("log", 0, -1); 
 }

In the following example, data messages in the recorded stream file log.flv are returned all at once, rather than at the intervals at which they were originally recorded:

 application.myStream = Stream.get("data"); 
 if (application.myStream) { 
     application.myStream.play("log", 0, -1, 2); 
 }

A server-side stream cannot subscribe to itself. For example, the following code is invalid:

 // Client-side code 
 var ns = new NetStream 
 ns.publish("TestStream"); 
  
 // Server-side code 
 st = Stream.get("TestStream"); 
 st.play("TestStream");

Stream.publishQueryString

myStream.publishQueryString

The query string specified in the stream path when the stream was published.

Use the Stream.publishQueryString, Stream.maxQueueDelay, and Stream.maxQueueSize properties to configure the live queue for live streams. These Server-Side ActionScript properties override the values set in the Application/StreamManager/Live/Queue/ section of the Application.xml configuration file. The live queue, also known as live aggregate messages, batches multiple messages into a single composite message to increase server performance. Dynamic streaming depends on the values of maxQueueDelay and maxQueueSize to determine when to switch to a higher or lower bitrate stream. Set maxQueueDelay to a value long enough to produce a large burst of data.

When you publish a stream, you can specify a query string in the stream path with parameters that specify how to configure the live queue. Access the publishQueryString property (for example, from inside the application.onPublish() function) to access the query string. Parse the string to get the configuration parameters. Use the values from the configuration parameters to set the Stream.maxQueueDelay and Stream.maxQueueSize properties.

Note:

Flash Media Live Encoder 3 supports adding query strings to stream names. Earlier versions of Flash Media Encoder did not support query strings.

Availability

Flash Media Server 3.5

Example

The following client-side code publishes a stream with a query string:

ns.publish 
("exampleVideo?com.adobe.ams.maxQueueDelay=4000&com.adobe.ams.maxQueueSize=10240"); 
}

The following server-side code gets the query string, extracts the delay and size, and configures the live queue by setting the maxQueueDelay and maxQueueSize properties:

application.onPublish = function(clientObj, streamObj){ 
    trace("queryString : " + streamObj.publishQueryString); 
    // the helper function extracQueryStringArg() is defined below 
    delay = extractQueryStringArg(streamObj.pubishQueryString, "com.adobe.ams.maxQueueDelay"); 
    size = extractQueryStringArg(streamObj.publishQueryString, "com.adobe.ams.maxQueueSize"); 
    trace("old maxQueueDelay : " + streamObj.maxQueueDelay); 
    streamObj.maxQueueDelay = delay; 
    trace("new maxQueueDelay : " + streamObj.maxQueueDelay); 
    trace("old maxQueueSize : " + streamObj.maxQueueSize); 
    streamObj.maxQueueSize = size; 
    trace("new maxQueueSize : " + streamObj.maxQueueSize); 
} 
function extractQueryStringArg(queryString, arg) 
{ 
    var retVal = ""; 
    temp = arg + "="; 
    i = queryString.indexOf(temp); 
    if (i != 0) 
    { 
        temp = "&" + arg + "="; 
        i = queryString.indexOf(temp); 
    } 
    if (i != -1) 
    { 
        retVal = queryString.substr(i+temp.length); 
        i = retVal.indexOf("&"); 
        if (i != -1) 
        { 
            retVal = retVal.substr(0, i); 
        } 
    } 
    return retVal; 
}

See also

Stream.receiveAudio

myStream.receiveAudio()

A Boolean value that indicates whether the server receives the audio in a stream (true) or not (false). The default value is true.

Availability

Flash Media Server 4.5

Stream.receiveVideo

myStream.receiveVideo

A Boolean value that indicates whether the server receives the video in a stream (true) or not (false). The default value is true.

To use Apple HTTP Live Streaming to stream content over a cellular network, Apple requires that one stream be audio-only. To create an audio-only stream, set the Stream.receiveVideo property to false. The Adobe Media Server livepkgr application (rootinstall/applications/livepkgr) includes this code.

Availability

Flash Media Server 4.5

See also

Stream.record()

 myStream.record(flag, [maxDuration, maxSize])

Records the data passing through a Stream object and creates a file of the recorded stream. You can use this method to do the following:

  • Call Stream.record() to record a new file or to overwrite the data in an existing file with the recorded data.

  • Call Stream.record("append") to append the recorded data to the end of an existing file.

  • Call Stream.record("appendWithGap") to append the recorded data to the end of an existing file, while maintaining the gaps in the stream being recorded. Use this mode only when the AssumeAbsoluteTime configuration is true and the publisher is sending absolute time. See Using DVR with dynamic streaming.

  • Call Stream.record(false) to stop recording.

You can record or append in F4V or FLV format. To record a file with multiple codecs, record the file in F4V format.

Before you call the Stream.record() method, call the Stream.get() method to create a Stream object. The recording format is determined by the filename you pass to the Stream.get() method.

Note:

To play or edit F4V files recorded by Flash Media Server in other tools, use the Adobe Flash Media Server F4V Post Processor tool. The tool is available at www.adobe.com/go/fms_tools.

When you record a stream, the server creates a file with the name you passed to the Stream.get() method. The server automatically creates a “streams” directory and subdirectories for each application instance name. If a stream isn’t associated with an application instance, it is stored in a subdirectory called “_definst_” (default instance). For example, a stream from the default lecture application instance would be stored here: applications\lectures\streams\_definst_. A stream from the monday lectures application instance would be stored here: applications\lectures\streams\monday.

To append a live stream to a file, the stream name passed to the Stream.get() method must be different from the live stream name in the client NetStream.publish() method. In other cases, the client-side and server-side Stream names can be the same.

Availability

Flash Communication Server 1

Parameters

flag

One of these values: "record", "append", "appendWithGap", or false. If the value is "record", the data file is overwritten if it exists. If the value is "append" or "appendWithGap", the incoming data is appended to the end of the existing file. If the value is false, any previous recording stops. The default value is "record". For more information about using "appendWithGap", see Using DVR with dynamic streaming.

maxDuration

An optional parameter specifying the maximum duration (in seconds) for a recording. The default value, -1, uses the value of <MaxDurationCap> in the Application.xml configuration file. The default value of <MaxDurationCap> is -1, which means that there is no maximum duration; the recording length is unlimited.

Set this parameter to -2 or 0 to use the value of <MaxDuration> in the Application.xml configuration file as the limit.

maxSize

An optional parameter specifying the maximum size (in kilobytes) for a recording. The default value, -1, uses the value of <MaxSizeCap> in the Application.xml configuration file. The default value of <MaxSizeCap> is -1, which means that there is no maximum size; the recording file size is unlimited.

Set this parameter to -2 or 0 to use the value of <MaxSize> in the Application.xml configuration file as the limit. The default value is -1.

When a recorded file exceeds the duration or size, the recording stops and when recording stops the "NetStream.Record.DiskQuotaExceeded" message and then a "NetSteam.Record.Stop" message are sent to the stream's onStatus handler.

Returns

A boolean value of true if the recording succeeds; otherwise, false.

Example

The following example shows a client publishing a live stream, a server recording the stream, and a client subscribing to the recorded stream.

First, the client publishes a live stream:

myNetStream.publish("clientStream", "live");

Next, the server opens a stream named serverStream and stores it in the Stream object s. The server-side code plays and records the stream published by the client in F4V format. The name of the recorded file is “serverStream.f4v”, which is the name passed to the Stream.get() method.

//Start recording 
s = Stream.get("mp4:serverStream.f4v"); 
if (s){ 
    s.record(); 
    s.play("clientStream"); 
} 
// Stop recording. 
s = Stream.get("serverStream"); 
if (s){ 
    s.record(false); 
}

Clients can use client-side code to subscribe to the live stream that was published by the client and recorded on the server:

someNetStream.play("mp4:serverStream.f4v");

The following example passes the -1 for maxDuration and maxSize. This value sets an unlimited duration and size for the recording. These values override the Application.xml values for <MaxDuration> and <MaxSize>. However the duration and size of the recording cannot exceed the values of <MaxDurationCap> and <MaxSizeCap> set in the Application.xml file.

Stream.record("record", -1, -1);

The following example sets maxDuration to 50 seconds and uses the <MaxSize> setting from Application.xml. The duration and size of the recording cannot exceed the values of <MaxDurationCap> and <MaxSizeCap> set in the Application.xml file.

Stream.record("record",50,-2)

See also

Stream.time

myStream.time

Read-only; the number of seconds the stream has been playing. This value is the timestamp of the latest frame that flowed out of the stream.

Note:

The Stream.time property is limited to 32-bit uint maximum value. This property resets in 49 days.

Availability

Flash Media Interactive Server 3.5 and Flash Media Development Server 3.5

Get help faster and easier

New user?