Problème avec M6 replay

Bonjour,

je rencontre un problème avec M6 replay. en effet, j'ai le son mais aucune image.
ca me met le message suivant : "version série 9 optimisée. cliquez ici pour plus d'informations".
et quand je clique sur cliquez ici pour plus d'informations, le problème est que tous est écrit en anglais :
Fast Streaming

Related Links
• Downloads
• Experience It

Windows Media Player is Better Together With Windows Media Services
When Windows Media Player connects to Windows Media Services, broadband users experience the instant-on, always-on playback of Fast Streaming.

When you see Optimized streaming experience in the Windows Media Player status bar, you know you are getting the ultimate streaming experience!
To get Fast Streaming, you need:
Windows Media Player. You must be running Windows Media Player 9 Series or later to experience Fast Streaming.
Unused bandwidth. Your connection speed must be higher than the data rate of the content you are playing back to experience Fast Streaming. The faster your connection, the better your experience will be.
Windows Media Services. The media you are connecting to must be hosted on a server running Windows Media Services 9 Series or later. If you don't get a Fast Streaming experience, contact the site's webmaster and suggest that they upgrade their server.

To experience Fast Streaming for yourself, see Windows Media Audio and Video Demos.

Back to Top

What is Fast Streaming?
Fast Streaming refers to the following group of features included in Windows Media Services to improve the quality of streaming media content for the user:
Fast Cache
Fast Start
Fast Recovery
Fast Reconnect
Advanced Fast Start

Fast Cache
When used with Windows Media Player 9 Series or later, Fast Cache provides a way to stream content to clients faster than the data rate specified by the stream format. For example, using Fast Cache, the server can transmit a 128-kilobits-per-second (Kbps) stream at 700 Kbps. The stream is still rendered in Windows Media Player at the specified data rate, but the client is able to buffer a much larger portion of the content before rendering it. This allows the client to handle variable network conditions without a perceptible impact on the playback quality of either on-demand or broadcast content.

This ability is useful in the following situations:
When the available network bandwidth of the client exceeds the required bandwidth of the content; for example, clients that use a cable modem, DSL connection, or corporate intranets.
When the network connectivity is intermittent or has high latency; for example, wireless networks.
When the quality of the content received is of paramount importance; for example, businesses that provide pay-per-view movies.

Notes
When Fast Cache is enabled, Windows Media Services cannot use intelligent streaming.
You can control the behavior of individual streams by adding Fast Streaming URL modifiers to the URL that a client uses to connect to the stream. For example, you can use the WMCache URL modifier to enable a client to use Fast Cache. You can also control the maximum bandwidth available for streaming a file or a live stream by using the WMBitrate and WMContentBitrate URL modifiers. For more information, see Controlling Fast Streaming behavior with URL modifiers.
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 later, 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 re-buffering. A Player that connects through broadband networks starts 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.

Notes
The Fast Start feature is only used by clients that connect to a unicast stream.
Fast Start requires that Windows Media Services continuously maintain a buffer of content to be streamed to new clients. When the Start publishing point when first client connects property is enabled in a live broadcast publishing point, Fast Start can cause an additional rendering delay of 8 to 10 seconds for the first client that connects to the stream because Windows Media Services must first collect a content buffer. Clients connecting to a broadcast stream that is in progress will not experience any additional delays due to Fast Start buffering.
Fast Recovery
Fast Recovery is accomplished by enabling forward error correction (FEC) on a publishing point in Windows Media Services. With the help of FEC, Windows Media Player can usually recover lost or damaged data packets without having to request that the data be resent by the Windows Media server. In environments that are subject to latency problems, such as satellite networks and other wireless networks, this process of receiving data is much more efficient.

Fast Reconnect
Windows Media Services includes Fast Reconnect, which minimizes the impact to each client during a temporary network outage by enabling the client to reconnect to the server automatically and restart streaming. If the client was connected to an on-demand publishing point, the client restarts playback at the point at which the connection was lost by synchronizing itself with the content timeline. If the content includes video, the client estimates the approximate video frame at which the connection was lost. If the content is indexed, this estimate is more accurate. If the client is connected to a broadcast publishing point, the client reconnects to the broadcast in progress. Depending on the content, the user may experience a gap in the broadcast.

Notes
Fast Reconnect can be used by clients that connect through any of the default connection protocols (MMS, HTTP, and RTSP) to a unicast stream. A successful reconnection is reflected in the log file with a status code of 210.
You can control the behavior of individual streams by adding Fast Streaming URL modifiers to the URL that a client uses to connect to the stream. For example, you can use the WMReconnect URL modifier to specify the number of times a client can try to reconnect to a stream if a connection is lost. For more information, see Controlling Fast Streaming behavior with URL modifiers.
Advanced Fast Start
Advanced Fast Start is designed to minimize startup latency in Windows Media Player 10 or later. Startup latency is the period of time starting when a viewer requests a stream by using the Player, and ending when the content begins playing. A number of factors can introduce latency, such as the speed of the client computer, the state of the network, the available bandwidth, and the Windows Media server configuration. However, the primary reason for startup latency is the delay caused by buffering on the client.

An adequate buffer size is essential for providing a good user experience. The client buffer stores streaming media data in memory so that the Player can maintain smooth playback of a stream. With inadequate buffer size, presentation playback can be uneven. The buffer is also used by codecs that decode a stream. When more buffer memory is available to codecs, the audio and video quality is improved.

The buffer size affects the amount of startup latency because a client cannot begin playing a stream until the buffer is full. The Fast Start feature in Windows Media Services reduces latency significantly by streaming the data at an accelerated rate until the buffer is full. However, the stream still cannot be played until that point.

Advanced Fast Start enables the Player to begin playing a stream before its buffer is full. When the Player receives a minimum amount of data, it can begin playing a stream while its buffer continues to fill at an accelerated rate—a rate that is faster than the encoded bit rate of the content. When the buffer is full, acceleration stops and the Player begins receiving data at the encoded bit rate.

For Advanced Fast Start to work effectively, adequate bandwidth must be available above the encoded bit rate of a stream. For example, if 1,200 kilobits per second (Kbps) of bandwidth is available for an 800 Kbps stream, the Player can use an acceleration rate of 1.5 times the encoded bit rate. On the other hand, if no additional bandwidth is available, the Player must fill its buffer before it begins playing a stream and no benefit can be gained from either Advanced Fast Start or Fast Start.

Note
To use Advanced Fast Start, it must be enabled on both the Player and Windows Media Services because it depends on communication between the two components when the Player initially requests a stream. On the client side, Advanced Fast Start is supported by Windows Media Player 10 or later or by Windows CE 5.0 or later (using the HTTP protocol). On the server side, Advanced Fast Start is not available if Windows Media Services is running Windows Server 2003, Standard Edition.

How Advanced Fast Start works
For Advanced Fast Start to work effectively, adequate bandwidth must be available above the encoded bit rate of a stream. For example, if 1,200 kilobits per second (Kbps) of bandwidth is available for an 800 Kbps stream, Windows Media Player can use an acceleration rate of 1.5 times the encoded bit rate. On the other hand, if no additional bandwidth is available, the Player must fill its buffer before it begins playing a stream and no benefit can be gained from either Advanced Fast Start or Fast Start.

To use Advanced Fast Start, it must be enabled on both Windows Media Player 10 and Windows Media Services because it depends on communication between the two components when the Player initially requests a stream.

Advanced Fast Start requires that the Windows Media server send an accelerated bit rate stream. Therefore, this feature is only available for unicast streaming.

The following process describes how Advanced Fast Start works after the Player sends a request and the server has successfully located the requested content and authorized the Player to receive it:
The server analyzes the content, and calculates the following data for a number of acceleration rates:
Largest underflow amount. Underflow occurs when the Player renders the data faster than it is being received. When underflow occurs, the Player must stop and buffer more data. Therefore, underflow must be avoided to maintain a quality user experience. The largest underflow amount is the largest amount of extra data that the client will require during a given acceleration period to avoid underflow. The higher the acceleration rate and longer the acceleration period, the less likely it is that underflow will occur. The server initially determines a fixed acceleration period.
Time of underflow. The time that the largest underflow amount occurs.
The server typically sends the client data at the following acceleration rates: 1.0, 1.2, 1.5, 2.0, and 3.0. For example, the data might show that with an acceleration rate of 1.2, the client will need 150 KB of additional data in its buffer after five seconds to avoid underflow.
The Player calculates the current bandwidth between the client and server, and then requests the most appropriate acceleration rate from the server.
The server streams the content at the requested acceleration rate.
The Player buffers the minimum amount of data, checks to make sure that adequate data has been received, and then begins playing the content. Meanwhile, its buffer continues to fill at the requested acceleration rate.
When its buffer is full, the Player sends a message to the server to end acceleration, and begins streaming at the encoded bit rate.
Encoding content for Advanced Fast Start
Windows Media Encoder organizes audio and video data into data packets that can be easily and efficiently transported over a network. When the packets arrive at the client, Windows Media Player 10 re-assembles the data in the correct order and plays the audio and video with the correct synchronization. Because the video buffer is typically larger than the audio buffer, it is common for the encoder to place the audio data in a packet that arrives after the corresponding video. When this occurs, the Player must wait for the audio to arrive before it begins rendering a stream because video cannot play without the accompanying audio stream.

Audio that arrives late is typically not a problem if startup latency is not an issue in the streaming scenario. However, when Advanced Fast Start is used to minimize latency, it is important that the audio arrive slightly before the video so the content can begin playing when possible. To make sure the audio arrives before the video, you can create an encoder system profile in which the audio and video buffers are the same size. The fixed audio buffer size is 1450 milliseconds (ms). Therefore, if the profile sets audio and video buffers to 3000 ms, the audio buffer is 3000 ms plus the fixed buffer size, or 4450 ms, which effectively places the audio data before the video data.

To create a profile that includes an audio buffer setting, first create a custom profile by using the Windows Media Profile Editor utility in Windows Media Encoder, and then add the setting by opening and editing the custom profile file with a text editor, such as Notepad.

To add an audio buffer setting to an encoding profile
On the Start menu, point to All Programs, point to Windows Media, point to Utilities, and then click Windows Media Profile Editor.
On the General tab, enter the following information:
Name and Description. Enter text to identify your custom profile.
Mode and Codec. In Media Types, select the Audio and Video check boxes. Make sure CBR (constant bit rate) is selected for audio and video, and Windows Media Audio 9 and Windows Media Video 9 codecs are selected.
Select the Allow interlaced processing and Allow non-square pixel output check boxes (This is not required for Advanced Fast Start, but is recommended).
Target bit rates. Click Add, and type any number over 15K. You will adjust the final bit rate on the Bit Rate tab.
On the Bit Rate tab, enter the following information:
Audio format. Select a compression setting and format. For example, for high-quality audio, select 64 Kbps, 48 kHz, stereo CBR.
Video size. Select the Same as video input check box.
Frame rate. Enter an appropriate frame rate. For highest quality, the frame rate should be the same as the source, for example 29.97 for NTSC video.
Key frame interval. Enter the minimum key-frame interval value of 1.
Video bit rate. Enter an appropriate high-bandwidth video bit rate, for example 1200 Kbps or 1.2 Mbps.
Buffer size. For unicast delivery with Advanced Fast Start, enter 3. For multicast, enter the minimum buffer size of 1.
Video smoothness. Enter a value of 83.
Click Save and Close.
In the Save Profile As dialog box, locate the Profiles folder (by default, %systemdrive%\Program Files\Windows Media components\Encoder\Profiles), and enter a file name for the profile.
Close Windows Media Profile Editor, open a text editor such as Notepad, and then open the custom profile file.
In the profile text, specify the bufferwindow value as 4450:
bufferwindow="4450"
Save the file.

Note
The audio buffer setting described in this section is a guideline that works well for many, but not all, streaming scenarios. For more information, see Delivering IPTV with the Windows Media Platform.

merci de m'aider