• Using Playlists. Provides information about writing playlists for the Macintosh platform.
• Logging. Describes how Windows Media Player for Mac handles logging requests.
• Embedding the Player in a Web Page. Details the issues involved with embedding the Player in a Web page, including detecting whether the Player has been installed on the client computer.
• Script Commands. Describes the supported script commands in Windows Media files.
• Closed Captions. Describes issues with displaying closed captions in an embedded Windows Media Player.
• Windows Media Rights Manager. Provides information about configuring servers to support digital rights management on Macintosh clients.
• Windows Media Download Support. Describes how Windows Media Player for Mac supports download packages.
• Authentication Issues. Describes how to work with user authentication.
• For More Information.

Back to the top

• Extensions. Windows Media files with .asx extensions that have had their file name extensions changed to .asf will not play on the Macintosh. Be sure to label your files appropriately.
• Protocols. Instead of linking directly to a digital media server by using the Microsoft Media Server (MMS) protocol from a Web page, you should create an .asx file that redirects traffic to the server, and link to the .asx file. Windows Media Player for Mac does not provide protocol handlers.

• Large dynamic playlists. Client-side playlists that contain an unusually large number of entries may perform poorly on the Macintosh.
• Cookies. You cannot use Microsoft Internet Explorer cookies for query data when generating a playlist.
• Numbers in the URL. Be careful how you use numbers in your URL paths. If you include a URL that contains floating-point values, and you also fail to provide a file name extension and a question mark query separator, the Player will treat the URL as an IP address.
• Redirection. If you use HTTP 301 (Moved Permanently) or HTTP 302 (Moved Temporarily) redirection, be sure your content type remains consistent. For example, if you use HTTP 302 redirection from a link to a file with an .asx file name extension, be sure to respond with the URL of an .asx playlist. Failure to maintain consistent content types may yield unexpected results.

Note: Proxy redirection is not supported (HTTP 305).

• LOGO
• PARAM
• SKIPIFREF

Back to the top

{3300AD50-2C39-46c0-AE0A-xxxxxxxxxxxx}

Back to the top

• Plug-in TYPE. Pay close attention to the value of the TYPE attribute in the <EMBED> tag when embedding the Player. This value must read:

  "application/x-mplayer2"

  Use this value exactly as it appears.
  
  

• BaseURL. When you specify a base URL, avoid using a relative URL to access a parent directory. Instead, specify the BaseURL value to be the URL of the highest-level directory. Each relative URL can then be specified by its relationship to the parent directory.
• MIME type. Be sure to configure your server to provide the correct MIME type for your content.
• Full-screen mode. Users cannot switch to a full-screen display from an embedded Player on a Macintosh computer. If you want users to be able to view your content in full-screen mode, provide a link from your Web page directly to an .asx file. This will cause the stand-alone Player to launch and start the playlist.
• Netscape 6. The Netscape 6 browser is not supported.
• Internet Explorer 4.5 for Mac. Specifying a value for the SRC attribute within an <EMBED> tag that refers to a URL using the MMS protocol will result in an error. Instead, point to an .asx file, and encourage users to upgrade their browser software to Internet Explorer 5 for Mac. Alternatively, use the FileName attribute. Using the SRC attribute to open digital media files using the MMS protocol might yield unexpected results.

• AutoStart
• BaseURL
• CurrentMarker
• CurrentPosition
• DefaultFrame
• FileName
• InvokeURLs
• Mute
• PlayCount
• PreviewMode
• SAMIFileName
• SAMILang
• SAMIStyle
• SelectionEnd
• SelectionStart
• ShowAudioControls
• ShowCaptioning
• ShowControls
• ShowDisplay
• ShowGotoBar
• ShowPositionControls
• ShowStatusBar
• ShowTracker
• Volume

Note: You must specify a value for the FileName attribute before specifying values for any other attributes.

For details about the behavior of the attributes in the preceding list, refer to the "Version 6.4 Object Model Reference" section of the Windows Media Player 6.4 SDK.

Detecting the Player
You can write script for the Macintosh to verify that Windows Media Player is installed on the client computer. You can also check if the Player is installed on clients using Netscape Communicator 4.5 or later and Internet Explorer for Mac version 5 or later.

To check for the installation of Windows Media Player for Mac, use the following JavaScript code to check for the plug-in.

var fHasWMP = navigator.mimeTypes 
              && navigator.mimeTypes["application/x-mplayer2"]
              && navigator.mimeTypes["application/x-mplayer2"].enabledPlugin;
if( fHasWMP ) {
    document.write("Windows Media Player is installed.");
}

Back to the top

Back to the top

http://server/filename.asf?sami=http://server/samifile.smi

<!-- Unsupported! -->
;MULTI
mms://servername//filename.asf
http://servername/filename.smi

Back to the top

• Server support. When using Windows Media Rights Manager, servers must be configured specifically to support Macintosh clients. The process involves updating the appropriate Microsoft SQL Server™ database to contain the proper key value in the drm_constants table of the music database.

  You can use the following SQL query to add the key to your database:
  
  

  insert into drm_constants (attribute, type, value2)
  VALUES ('client_verification_public_key_0.1.0.2', 2,
  'FiLzeUi!jkNCFzhKaQQh5v0J1jAyq5mDc6F9P2JUFALIasYmYQ!5aA==')
  

  For step-by-step instructions about updating your SQL Server database to support Windows Media Rights Manager on the Macintosh, see the "Macintosh Client Support for the Windows Media License Service" article on the MSDN Web site.
  
  

• Windows Media Rights Manager and the embedded Player. If a license for the requested file already exists on the client computer, the file will play in the embedded Windows Media Player. However, if the license needs to be downloaded, the browser will retrieve the license and then launch the stand-alone version of the Player to play the encrypted content.

Back to the top

Back to the top

Back to the top

Back to the top

Back to the top