When you produce RealAudio or RealVideo clips using Helix Producer, you can use a utility that embeds clip information and HTML URLs directly in the clip. This lets you add many of the features available through a Ram file directly to your streaming audio or video clip.
|For More Information: See Helix Producer User's Guide for information about additional parameters that you can encode into a clip. You can turn a RealVideo clip into an image map, for example. You can download Helix Producer from http://www.realnetworks.com/products/producer/index.h tml, and display the user's guide from the Help menu.|
The RMEvents utility runs on all Windows operating systems, as well as Linux and the Macintosh. Any version of RMEvents can encode the information described in this chapter, so you can use a utility that predates RealOne Player, such as the one that comes with RealSystem Producer 8.5. The URL-encoding method is backwards-compatible with earlier versions of RealPlayer. If a viewer has RealPlayer 8, for example, the encoded URLs display in the viewer's default browser.
Because this production technique encodes URLs directly into the clip, it is not recommended if you want the HTML pages associated with clips to change. (RMEvents preserves the original copy of your clip, though, so you can always change the URLs by running RMEvents again.) Additionally, it's easier to use SMIL links, as described in Chapter 6, if your RealAudio or RealVideo clip will be part of a multiclip presentation.
To use RMEvents, you first create an events file, which is a plain text file that
uses the standard text extension of
.txt. This file describes events that occur as
the clip plays. You write each event on a separate line, and you can use a pound
#) to start a comment line. Each event line follows this format:
The flag indicates the type of event, which can be either to display clip information, or to open a URL in an HTML pane automatically. The starting time and ending time are relative to the start of clip playback. You indicate the time value with the following format, in which only the seconds field is required:
|Note: As with a Ram file, define each event on a single line within the events text file. Do not press Enter to wrap long lines manually.|
When opening a URL automatically in an HTML pane, you use the
flag. The event syntax looks like this:
The URL must be a fully qualified HTTP URL. For the parameters, you can
rpcontextwidth when sending a URL to the related info
target, use one of the following:
||Display the URL in the related info pane.|
||Display the URL in the media browser pane.|
||Display the URL in a secondary browsing window.|
The following is a sample events file that opens two URLs in the related info pane at different times, and two URLs in the media browser pane at different times:
# Open a URL in the related info pane when the clip starts, and size the pane.
Note the following about this sample:
1:00minutes, but no later than
1:59.9minutes. If a viewer starts the clip and immediately seeks to its 3-minute mark, for example, the URL doesn't display because the clip never plays at any point between the URL's start and end times.
Using RMEvents, you can encode the Ram file
clipinfo parameters described in
"Setting Clip Information". As with a Ram file, separate the subvalues with
vertical lines, or "pipes." The following example shows an events file line that
specifies clip information, using
i as the event flag:
i 00:00:00.0 00:00:10.0 clipinfo:title=My Presentation|artist name=Pat Morales|...
For clip information, you can specify the start time as the clip's starting time
00:00:00.0). Specifying an end time is required, but the actual end time
doesn't matter because the clip information will display throughout the
length of the clip playback. In the example above, the end time is set to 10
seconds after the clip starts.
|Note: You can also encode into a clip the title, author, and copyright information described in "Overriding Title, Author, and Copyright Information". Typically, you add this information through the Helix Producer interface when encoding a clip, but you an also add it later through the RMEvents utility. For more information, see Helix Producer User's Guide.|
After you write your events file, you use the RMEvents utility to merge the events file with your clip. The following are instructions for doing this on Windows operating systems. For instructions on running RMEvents on Linux or the Macintosh, as well as for information about additional command options, refer to your Helix Producer User's Guide.
|To merge an events file with a RealAudio or RealVideo clip on Windows:|
C:\Program Files\Real\Helix Producer Basicor
C:\Program Files\Real\Helix Producer Plus.
Here is an example:
C:\>cd "C:\Program Files\Real\Helix Producer Basic"
.rmis the path and name of the input clip
.rmis the path and name of the output clip
.txtis the path and name of the events file
|Tip: Always choose a new output name so that you can save your original clip without any encoded events.|
|View it now!
(requirements for viewing this sample)
This sample plays a video clip that has an encoded URL event. Five seconds after the clip begins to play, it opens a Web address in the media browser window. You can also view the events file.
After you have encoded events into your RealAudio or RealVideo clip, you can
stream the clip by transferring it to your server and linking it to a Web page
through a Ram file, as described in Chapter 3. Note that you can also add
parameters to the Ram file. If you have encoded HTML URLs or
information into your clip, you shouldn't also use these parameters in the
Ram file. But you may want to use other Ram file parameters, such as
screensize=double, for instance, to open the clip at twice its encoded size.
©2002 RealNetworks, Inc. All rights reserved.
For more information, visit RealNetworks
Click here if the Table of Contents frame is not visible at the left side of your screen.