throbber
9/27/13
`
`servi cereal .com/hel p/l i brary/bl uepri nts/85codecs/htmfi |es/producer2.html
`
`4-»
`
`Choosing SureStream or Single Rate Encoding
`
`When you encode a clip with RealSystem Producer, the most important decision you make is whether to create
`
`a single-rate clip or use SureStream to generate a multi—rate clip. This choice is simple:
`
`0 To stream a clip with RealServer, choose SureStream
`
`0 To host a clip on a Web server, choose the single rate option.
`
`However, to use RealSystem Producer eflectively, you should understand what SureStream is. This will help you
`
`later ifyou decide to change the RealSystem Producer encoding defaults.
`
`What is SureStream?
`
`Introduced with RealSystem G2, SureStream technology gives the best p0ss1ble playback experience for
`
`difierent types ofnetwork connections. With SureStream, you can encode your source file for optimum
`
`streaming over, for example, 28.8 Kbps modems, 56 Kbps modems, and 112 Kbps dual ISDN connections, as
`
`illustrated in Figge 1. Users with 28.8 Kbps modems receive the stream at the lowest bit rate, while users with
`
`fister connections get a stream with better quality because ofthe extra bandwidth. RealSystem Producer Basic
`
`encodes two speeds per clip, RealSystem Producer Plus up to eight speeds.
`
`Figure 1: SureStream Clip Encoded for Several Bandwidths
`
`RealF'lay-ers “Q U.
`. "
`23.3 Kbps
`
`I
`
`SureSlream
`
`cup @ 4..
`
`. O
`. . . ,. . . . .
`
`‘0.
`
`“Ia
`
`‘1' a
`
`55 Kbps
`
`Q.*'l
`.
`a Q a
`112 Kbps
`
`A SureStream clip can also "downshift" when a connection gets bogged down. Suppose a viewer starts out
`
`receiving a higher bit rate stream through a 56 Kbps modem Ifthe connection starts to sputter as the network
`
`gets crowded, RealServer automatically downshifts to a lower bit rate stream The audio or video quath drops
`
`with the lower rate stream, but the clip keeps playing. When the interference clears, RealServer upshifis to the
`
`higher rate stream RealPlayer doesn't need to rebufier during this shifting.
`
`Why SureStream won't Work with Web Servers
`
`SureStream works only with clips streamed with RealServer. Because SureStream wraps several streams into a
`
`single clip, a server has to know how to extract just one stream from the clip. RealServer can do this, but Web
`
`servers, which don't know the details of SureStream, send down all the encoded data for a SureStream clip
`BTN 0007403
`
`servicereal .com/hel p/I i brary/bl uepri nts/85codecs/htrnfi | es/producer2.htm|
`
`1
`
`1/3
`NEULION 1004
`
`BTN0007403
`
`1
`
`NEULION 1004
`
`

`

`9/27/13
`
`servi cereal .com/hel p/l i brary/bl uepri nts/85codecs/htmfi |es/producer2.html
`
`rather than just one stream
`
`Duress Streams
`
`Although you can encode a clip for just one connection speed with SureStream, you should never do this when
`
`delivering a clip with a Web server. Even when encoded for just one speed, a SureStream clip contains "duress"
`
`streams that let it downshifi during network turbulence. For example, a SureStream music clip encoded only for
`
`28.8 Kbps has duress streams at 16 and 11 Kbps. A Web server downloads all these streams, wasting
`bandwidth.
`
`Multiple Bandwidth Choices Through SMIL
`
`When using a Web server, you can provide different bandwidth choices by encoding your source file several
`
`times for diiferent connection speeds. You then provide multiple links on your Web page (one for each clip), or
`
`use SMIL's <switch> tag so each RealPlayer chooses the right clip automatically. SMIL isn't as flex1ble as
`
`SureStream, and you won't get downshifiing, but using SMIL makes it easier for your viewers to get the best clip
`for them
`
`See the SMIL chapter inRealSystem Production Guide for instructions on using a < swi t ch> tag.
`
`SureStream File Size
`
`Because each SureStream stream increases the clip's file size, an encoded clip may be larger than its source file,
`
`even though the clip is compressed. Ifthe clip's file size is an issue, limit the SureStream streams to just the
`
`essential speeds. Table 1 gives ballpark figures for file space required for each minute of a RealAudio or
`RealVideo stream
`
`Table 1:Approximate Size for RealAudio and RealVideo Clips
`
`Target Audience
`
`28.8 Kbps modem
`
`56 Kbps modem
`
`64 Kbps single ISDN
`
`112 Kbps dual ISDN
`
`Corporate LAN
`
`256 Kbps DSL/cable modem
`
`384 Kbps DSL/cable modem
`
`512 Kbps DSL/cable modem
`
`
`
`
`
`RealVideo
`
`0.15 Megabytes/minute
`
`0.25 Megabytes/minute
`
`0.33 Megabytes/minute
`
`0.59 Megabytes/minute
`
`1.1 Megabytes/minute
`
`1.65 Megabytes/minute
`
`2.56 Megabytes/minute
`
`3.30 Megabytes/minute
`
`
`
`When using SureStream to encode RealAudio or RealVideo, add the figures from Table 1 for each connection
`
`speed you encode, then multiply by the length in minutes the source file plays. Table 1 shows that ifyou encode a
`
`RealAudio clip for 28.8 Kbps and 56 Kbps modems, for example, the clip takes about 0.39 Megabytes of disk
`
`space per minute (0.15 + 0.24). Ifthe audio is five minutes long, the clip willbe about 1.95 Megabytes in size
`
`(0.39 x 5).
`
`servicereal .com/hel p/I i brary/bl uepri nts/85codecs/htmfi | es/producer2.htm|
`
`2
`
`BTN 0007404
`
`23
`
`BTN0007404
`
`2
`
`

`

`9/27/13
`
`servi cereal .com/hel p/l i brary/bl uepri nts/85codecs/htmfi |es/producer2.html
`
`The figure you get is an approxirmtion based on using the RealSystem Producer default settings. The actual file
`
`size varies depending on the combination of streams you've chosen, the type of audio, and Whether you‘ve
`
`changed the defaults. Ifyou encode for just one connection speed, the file will likely be larger than you calculated
`
`because ofthe duress streams. When you encode ReaIVideo for multiple connections, the file size may be lower
`
`than you calculated because different RealVideo streams may use the same RealAudio stream for a soundtrack.
`
`Copyright © 2001 RealNetworks
`For information on RealNetworks' technical support, click here.
`Comments on this document? Click here.
`This file last updated on 04/10/01 at 16:17:57.
`
`4-»
`
`servicereal .com/hel p/I i brary/bl uepri nts/85codecs/htrnfi | es/producer2.html
`
`3
`
`BTN 0007405
`
`3/3
`
`BTN0007405
`
`3
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket