| |
Since the RealPlayer now supports playing files delivered via HTTP, no
special software is required. This means that streaming audio/video can be
delivered in the same manner as a gif or HTML page. To use this over HTTP,
you need two files, 1) an audio file with the extension .ra and 2) a text
file with the extension .ram. This text file must contain the URL of the .ra
file so that the server can serve it. The contents of the file would be
"http://yourdomain.com/path-to-file/file.ra". If you do not want to do HTTP streaming, you may get your own copy of RealServer and install it for your own domain. Real Server is a product of Real Networks and any issues regarding the Virtual Real System Server should be directed to Real Networks. This following steps should be taken to install Real System Server Basic on your domain. Steps to install for a single domain:
1. First visit:
http://proforma.real.com/rnforms/products/servers/eval/index.html?ulf=bas
2. Complete the form (need to give an e-mail address you actually access)
3. Click through until you reach the final page.
4. Download the .bin file provided
5. Upload this to your account
6. Access your e-mail address that you filled out earlier and retrieve the license.
7. From the command line execute the binary file.
./rs802-linux-20-libc6-i386.bin (You must have SSH access to do this)
8. Follow the installation steps provided (use the default ports that it selects)
That should be it. You should now be able to upload real player files (.ra) to your account for streaming.
Yes, you will be able to stream RealMedia files. You will need to create a .ram file that calls your real audio/video file. The .ram file is a text file with an absolute URL. This URL will need to be:
http://full.domain.name/directory/filename.rm
(2)Is there a difference between streaming using the PNM-protocol and the HTTP-protocol?
If you visit http://www.real.com/, you might come across a term called "pseudo-streaming". According to audiohost.com:
"Pseudo-streaming" is a discriminating name for HTTP-stream. It was invented by the RealAudio promotion to suggest that you need to use the RealAudio server if you want to get "real" streaming. Here's a free translation: "Streaming RealAudio files without using RealAudio server software". That's all there is to it! The RealAudio server actually has some special features that cannot be achieved (in RealAudio) without it. Regarding "streaming" we cannot find a difference between the two protocols.
(3)What are some of the special features of the RealServer?
With the Real Server, you are able to take advantage of "bandwidth negotiation". This feature takes into account the bandwidth of the surfer's Internet connection when clicking on the hyperlink that requests the RealMedia file. Depending on the connection, the RealServer will provide a different version of the RealMedia file that best suits the visitor's bandwidth connection.
You also need the RealServer to broadcast live on the Internet.
(4) How do I get around not having "bandwidth negotiation"?
While encoding, if you set the target audience to 28 K modem, you will be able to reach the largest audience possible. If you want your higher bandwidth connection visitors to receive better quality recordings, you can always create a second link to a RealMedia file that is encoded with a target audience of a higher bandwidth connection.
|
