Encoding and hosting Real Media files on the cheap from Windows.
You don't need a Streaming Media Server or the Expensive version of Real Producer to get good results with streaming Real Media files.
You don't even need to install Real Player to watch them. And it works on Linux, Windows and Mac. [real alternative is the alternative player, click here to download]
Software needed.
Step 1 : Capture / Save your project as a DV avi
You need to capture / export your video a DV avi.
Step 2 : Resize your File using Virtual Dub -
You need to resize it before you use Real Producer Basic as that feature is disabled in the free version.
Open up Virtual Dub - Select Video > Compression
Select the Cinepak Codec and choose a compression rate of 95 percent
Then add a couple of filters.
Select - Video > Filters
The deinterlace filter can help remove blurring due to movement.
Add another filter to resize the image.
Select - Video > Filters
Resizing is Essential. 240 x 192 should be good for European Pal Video users.
You shouldn't need to change any other settings including the audio.
Just Select File > Save As Avi -
And choose an appropriate name.
Step 3: Encode file with Real Producer
Open the program
Browse for the file.
Then click on Audience Settings
I reccomend doing 2 files.
First encode one for people on Dial up connections. Choose 56k Dial up setting
1 - Then make sure there is only one Setting in the Window on the right. You may need to delete other settings. Make sure it is only single rate.
2- Exit this screen
You are now ready to encode!
If you want you can repeat the last stage for a better file version for
Dsl-Cable 256k
4. Uploading the Files.
You can now upload the files to indymedia or your own server
If you want them to work as streaming, click and watch files then read this page about creating metafiles.
The page has been edited and simplified below
Once you a piece of video digitized in the RealMedia format, you need a way of displaying it for public consumption. The most obvious way to do this is to create a web page. You cannot directly link your video from the web page, however. First you must create a 'metafile' for your video file.
Creating Metafiles - The Old Way
Metafiles are used for linking and embedding the RealPlayer from a web browser. Metafiles can have any name, but must either have the extension '.ram' or '.rpm.' RAM metafiles allow you to create a link in your web page which when clicked causes a stand-alone player to play your video. RPM metafiles allow you to embed your video within the web page itself, loading the player into a space defined in the HTML.
Metafiles are usually small text files that contain the location of your RealMedia file. A metafile can contain some additional information as well, such as a start and end time. They usually contain text similar to the following:
rtsp://media2.bmrc.berkeley.edu/beowulf/lecturer1.rm
The lines that specify the RealMedia file follow the URL format. First the transport protocol is specified, in this case This is followed by the hostname of the RealServer on which the file resides, and the path to the file. The paths cannot be relative, the entire path must be hard coded into the file.
There are other parameters you can specify as part of the metafile. The format for specifying these parameters also follows the URL specs, namely, the path of the file is followed by a question mark and then a list of key=value pairs, each pair seperated by an ampersand. For example:
rtsp://media2.bmrc.berkeley.edu/beowulf/lecturer1.rm?start="0:01:14.0"&end="0:01:33.5"
In this example, a start and end time different from the original start and end time are specified for this clip.
Creating Metafiles - The New Way (RamGen)
The above method is useful if you are are trying to link multiple RealMedia files into one presentation. However, if you only have one RealMedia file, which will most likely be the case, the following method should make your life easier. Part of the RealServer is a virtual directory named 'ramgen'. By creating a link in your web page to this directory, followed by the path to your RealMedia file, the metafile creation process is sidestepped. Here is an example of a metafile and its RamGen equivalent. (Note: media2... = media2.bmrc.berkeley.edu)
Metafile:rtsp://media2.../beowulf/lecturerG2.rm
RamGen:
<A HREF="http://media2...:8080/ramgen/beowulf/lecturerG2.rm>...</A>Specifying the proper port (typically, port 8080) is important, as the RealServer is the program which dynamically generates the metafiles, not the web server.
Any of the parameters which could be specified in the metafile can be specified in the RamGen URL. For example, you could specify a new start and end time for your clip with the following link:
<A HREF="http://media2...:8080/ramgen/beowulf/lecturerG2.rm">...</A>
The Stand-alone Player
Now with intimate knowledge of metafiles and the ramgen URL, we can begin to create web pages with our RealVideo. The easiest way is to simply create links that bring up a stand-alone RealPlayer. Below is an example of this method, and the HTML code which accomplishes this.
My Favorite Video<A HREF="http://media2...:8080/ramgen/people/craigw/CRW-BenKillYou.rm">My Favorite Video</A>
When using a metafile, just replace the reference to the ramgen directory with the location URL (relative or literal) of the RAM metafile which describes the video.
