banner art

Understanding Fast Start

Windows Media Player must buffer a certain amount of data before it can start rendering content. If your clients are using Windows Media Player for Windows XP or a later version of the Player you can use Fast Start to provide data directly to the buffer at speeds higher than the bit rate of the content requested. This enables users to start receiving content more quickly. After the initial buffer requirement is fulfilled, on-demand and broadcast content streams at the bit rate defined by the content stream.

Using Fast Start enables your users to have a better experience when playing back your content. Users can fast-forward and rewind content without additional delay and rebuffering. A Player that connects through broadband networks start playing the content more quickly, making the experience much more like viewing a television program or listening to a radio broadcast. Users will notice that server-side playlists streaming from your publishing point switch smoothly and seamlessly between content items. Additionally, the pre-buffering of data makes the Player resistant to playback errors due to lost packets or other network issues.

The increased bandwidth that the Fast Start feature initially uses to send data to the Player can overburden a network if many Players connect to the stream at the same time. To reduce the risk of network congestion caused by the Fast Start feature, you can limit the amount of bandwidth the Fast Start feature uses to stream to each Player. For more information about limiting Fast Start bandwidth, see Limit Fast Start bandwidth per player (Kbps).

Note Image Notes

Related topics


© 2005 Microsoft Corporation. All rights reserved.

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.