WMWalkthrough.doc.doc.doc.doc.doc
Upcoming SlideShare
Loading in...5
×
 

WMWalkthrough.doc.doc.doc.doc.doc

on

  • 748 views

 

Statistics

Views

Total Views
748
Views on SlideShare
748
Embed Views
0

Actions

Likes
0
Downloads
3
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft Word

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

WMWalkthrough.doc.doc.doc.doc.doc WMWalkthrough.doc.doc.doc.doc.doc Document Transcript

  • Windows Media 7.1 Walkthrough Abstract With Microsoft Windows Media Technologies you can create, deliver, and play streaming media files for applications ranging from news and entertainment to e-commerce to corporate communications and training. Windows Media Technologies components include the Windows Media Tools, Windows Media Services streaming server, and Windows Media Player. These components provide an end-to-end solution for streaming multimedia, from content authoring to delivery to playback. This document will guide you through setting up and using Windows Media Technologies. It is intended for both technical and non-technical persons who wish to evaluate Windows Media Technologies as an easy-to-use, feature rich, and powerful streaming media platform.
  • © 2001 Microsoft Corporation. All rights reserved. The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This White Paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT. Microsoft, the BackOffice logo, NetShow, Windows, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Other product or company names mentioned herein may be the trademarks of their respective owners. Microsoft Corporation • One Microsoft Way • Redmond, WA 98052-6399 • USA 0498
  • Contents About This Guide About This Guide.......................................................................1 About Windows Media Technologies........................................2 Key Attributes 2 Getting Started..........................................................................3 Resource Planning 3 Installing Windows Media Components....................................6 Setup Windows Media Encoder 7 Setup the Web Server 7 Setup Windows Media Server 8 Setup Windows Media Player 8 Configuring Windows Media Components.................................9 Encoding 9 Serving 11 Using Windows Media.............................................................17 Understanding WMA and WMV Files 17 Embedding the Windows Media Player in a Web Page 17 Microsoft PowerPoint Integration...........................................18 PowerPoint XP2000 Presentation Broadcasting 19 Windows Media Publish to ASF 19 Windows Media Presenter 20 Monitoring Performance..........................................................20 Logging....................................................................................20 Enabling Unicast Logging 21 Enabling Multicast Logging 21 3rd Party Reporting Tools 22 Getting Help............................................................................22 Welcome to the Windows Media Technologies 7.1 Walkthrough. This document will guide you through setting up and using Windows Media Technologies. It is intended for both technical and non-technical persons who wish to evaluate Windows Media Technologies as an easy-to-use, feature rich, and powerful streaming media platform. This guide will: • Assist you in building a Windows Media test lab. • Show you how to encode live and stored digital content. Getting Started with Windows Media 1
  • About Windows Media Technologies • Explain how to conduct a live, scheduled, or on-demand broadcast on the Internet or intranet. • Show examples of embedding Windows Media Player in your Web pages. • Help you conduct a streaming Windows Media presentation using Microsoft PowerPoint. This guide assumes you have a working knowledge of simple TCP/IP networking and the Microsoft Windows operating system. With Microsoft Windows Media Technologies you can create, deliver, and play streaming media files for applications ranging from news and entertainment to e-commerce to corporate communications and training. Windows Media Technologies components include the Windows Media Tools, Windows Media Services streaming server, and Windows Media Player. These components provide an end-to-end solution for streaming multimedia, from content authoring to delivery to playback. Windows Media Tools The content creation components of Windows Media Technologies include tools for authoring both live and on-demand content, and for converting other file formats such as WAV, AVI, MPEG1 and MP3 to Windows Media format. Windows Media Encoder creates live content for broadcast over the Internet or intranets. It can also encode stored content for on-demand playback. The Windows Media Author and Advanced Script Indexer tools allow authors to create illustrated presentations by embedding graphics, markers, script commands, and indexes in a Windows Media file. There are several different tool kits available on the Windows Media web site (http://www.microsoft.com/windows/windowsmedia) in the Resource Kit area. The tools available are: Windows Media Encoder 7.1 Tools, Windows Media Format 7 Tools, Windows Media Services Tools and Windows Media Tools 4.1. Windows Media Services The Windows Media Services is a streaming media server. It is comprised of a set of four services running on Windows 2000 Server or Windows NT Server that can distribute audio, video, and other media to client computers via unicast or multicast delivery. To deliver live, real-time content, Windows Media Services works in conjunction with Windows Media Encoder, which compresses the audio and video feed in real time and passes it to the Windows Media server for delivery to the network. Windows Media Player Users play Windows Media content with Windows Media Player. Intranet and Internet surfers can use the Player to play audio, full-motion video files, and illustrated audio (synchronized sound and still images), as well as to offer playback of many other multimedia data types such as MP3 files and MPEG movies. Key Attributes  Highest Quality Audio and Video Triple the music with audio quality that is comparable to MP3 but at nearly one-third the size, broadcast near-DVD quality video at bit rates ranging from 500 Kbps to several megabits per second (Mbps), or deliver true-to-the-source screen capture to achieve the most compelling experience for broadband digital media content. Getting Started with Windows Media 2
  • Getting Started  Easiest to Use and Extend The all-in-one, customizable Player and enhanced encoder user interface facilitate a more productive and enjoyable user experience of broadband content creation and playback. In addition, the Windows Media software development kits (SDK) for Windows Media Player and Windows Media Encoder allow developers to easily integrate Windows Media support into their media tools and players.  Industrial-Strength Security The enhanced digital rights management (DRM) system is more secure and flexible, enabling innovative new business models for broadband content distribution.  Highest Scalability and Reliability Windows Media Services on Windows 2000-based servers will provide up to 9,000 concurrent narrowband streams (22 Kilobits per second) of video from a single server, and up to 2,400 broadband (100 Kilobits per second) Internet streams. In order to support the demonstrations described in this document, it is suggested that you build a lab with three test computers; one will be used as the media encoder, another as a media server and Web server, and a third computer for playback. It is recommended that this test lab be physically separated from your production network. The following diagram shows how all of the components work together. VCR, DVD, Live Video etc. MEDIACLIENT01 Windows Media Player/web browser Cable TV/Radio ENCODER01 MEDIASRV01 Windows Media Windows Media Encoder Server/web server Additional Clients (optional) Digital Content Windows Media (AVI, WAV, MPEG, etc.) Player/web browser Creation Distribution Playback Windows Media Components Resource Planning Getting Started with Windows Media 3
  • The following tables outline the minimum and recommended configurations for each Windows Media component. Windows Media Encoder Minimum Encoding task Recommended configuration configuration 200 megahertz (MHz) processor, such as an Convert existing Intel Pentium, with .wav, .avi, .mpg, and 500 MHz processor or higher, such MMX; .mp3 files to as a Pentium III;·Windows Microsoft Windows® Microsoft Windows 2000,·128 MB of RAM or more 98 Second Edition; Media™ Format 32 megabytes (MB) of RAM 200 MHz processor, 300 MHz processor or higher, such such as a Pentium as a Pentium II or Advanced Micro Real-time capture with MMX; Windows Devices (AMD) and broadcast of 98 Second Edition;·32 processor;·Windows 2000;·128 MB audio files MB of RAM· of RAM or more· Supported audio Supported audio capture device capture device Real-time capture Single stream and multiple-bit- and broadcast of Single stream and rate content for 100 Kbps through audio and video files multiple-bit-rate 500 Kbps:; 450 MHz processor or for dial-up modem content for 28.8 Kbps higher, such as a Pentium III· and mid-bandwidth and 56 Kbps modems: Windows 2000,·256 MB of RAM· audiences using the (Use recommended Supported audio and video Windows Media 7 configuration) capture devices codec Single stream content Single stream and multiple-bit- Real-time capture for 28.8 kilobits rate content for 100 Kbps through and broadcast of (Kbps) and 56 Kbps 500 Kbps;·700 MHz dual processor audio and video files modems· or higher, such as a Pentium III, for dial-up modem 700 MHz processor, or 1.5 gigahertz (GHz) processor and mid-bandwidth such as a Pentium III· or higher, such as a Pentium IV· audiences using Windows 98 Second Windows 2000,·256 MB of RAM· Windows Media 8 Edition,·32 MB of RAM· Supported audio and video codec Supported audio and capture devices video capture devices Single stream and multiple-bit- rate content for 500 Kbps through 2 megabits (Mbps) or more· Real-time capture 700 MHz dual processor and broadcast of (Use recommended or higher, such as a Pentium III· audio and video for configuration) Windows 2000,·256 MB of RAM or high bandwidth more· Supported audio and video capture devices Note For the latest information about system requirements, see the Windows Media Getting Started with Windows Media 4
  • Encoder 7.1 System Requirements page at the Microsoft web site (http://www.microsoft.com/windows/windowsmedia). Windows Media Services Minimum Recommended Component Optimal Configuration Configuration Dual Intel Pentium Eight Intel Pentium IV Intel Pentium 90 Processor II 400 MHz or processors (the fastest MHz better available) Memory 64 MB 256 MB or more 512 MB Network 10 Mb TCP/IP 10/100 Mb TCP/IP 100 Mb TCP/IP Interface Card Ethernet card Ethernet card Ethernet 21 MB for Windows 21 MB for Windows Media Services; Available hard Media Services; 4 GB or more SCSI 500 MB or more disk space enough disk space Raid 0 disk space for for content storage content storage Microsoft Internet Explorer 4.01 or Microsoft Internet later; Microsoft Explorer 4.01 or Microsoft Internet Windows 95 with later; Microsoft Explorer 4.01; DCOM95 or Software Windows NT Microsoft Windows NT Microsoft Windows Server version 4.0 Server version 4.0 NT Server or with Service Pack with Service Pack 5 Microsoft Windows 4 or later NT Workstation 4.0 with SP4 Getting Started with Windows Media 5
  • Installing Windows Media Components Windows Media Player Minimum Component Recommended Configuration Configuration Pentium 120 Processor Pentium or AMD Athlon 266 MHz or faster MHz Memory 64 MB or more 32 MB Network Interface 10 Mb TCP/IP 100 Mb TCP/IP Ethernet card Card Ethernet card 16-bit sound Audio Sound Blaster compatible 16-bit sound card card Video 16-color display True color 24-bit color display Supported Windows® 98, Windows 98 Second Edition, Windows 2000, or Operating Systems Windows Millennium Edition OS for portable WindowsCE 2.11 devices Software for ActiveSync® 3.0 portable devices Additional Hardware • Dedicated 10 or 100 MB hub. 100 MB hub suggested. • VCR with audio and video content or video camera for demonstrating real-time encoding. This section describes how to set up a demonstration lab for evaluating Windows Media Technologies. For the purposes of this walkthrough, the configuration below assumes that your Web server and streaming server will reside on the same computer. In a production environment however, it is recommended that the Web server and Windows Media server reside on two separate dedicated computers. For more information about planning a production streaming environment, download the Microsoft Windows Media Services Deployment Guide. There are four installation steps: • Set up Windows Media Encoder • Set up the Web server • Set up Windows Media Services • Setup Windows Media Player Prior to these steps, each computer should have its appropriate operating system installed and configured with proper Service Packs as necessary. Each computer should be a standalone server or workstation in a single workgroup. For example, name the workgroup MEDIALAB. Using User Manager on each computer, create a user ID and password that are the same on all of the computers in the MEDIALAB workgroup. Log in to the computers using the same user ID and password. Getting Started with Windows Media 6
  • Setup Windows Media Encoder 1. On the encoder computer, install and configure appropriate audio and video capture devices. For help with configuring each device, contact the device’s vendor. 2. To get built-in support for Intel’s Pentium III Streaming SIMD Extensions, run Windows Media Encoder on Windows 2000. If you are using Windows NT4 Service Pack 4: • Download and install the Intel Streaming SIMD Extensions Driver from the Intel Web site. or • Install Windows NT Service Pack 5, which includes the SIMD Extensions Driver. For information on the Intel Pentium III SIMD Streaming Extensions see the Intel Corporation Web site. For more information on Windows Media codecs, see the Microsoft Windows Media Technologies Web site. 3. Name the computer ENCODER01 and configure it to join the MEDIALAB workgroup. 4. Install Microsoft Windows Media Tools. Windows Media Tools can be downloaded from the Microsoft Windows Media Technologies Web site. Setup the Web Server 1. Name the computer designated as the Windows Media server MEDIASRV01 and join the MEDIALAB workgroup. 2. Install Microsoft Internet Explorer 4.01 Service Pack 1 or greater. 3. If you are running Microsoft Windows NT4 Server, install Microsoft Internet Information Server (IIS) using “typical” setup. Microsoft IIS is part of the Windows NT Server 4.0 Option Pack and can be downloaded from the Microsoft Web site. (Users of Microsoft Windows 2000 need only to install IIS through the Components Wizard, or at installation of the operating system.) 4. Create a directory on the Web server to store Windows Media station configuration files (stations files will be explained later in this document). This directory should be a subdirectory of a Web publishing point and its files should be visible to users from a Web browser. For example, if your default Web publishing point is C:Inetpubwwwroot, create a directory C:Inetpubwwwrootstations. 5. Create a Windows 2000/NT network share for the newly created directory called stations: a. From Windows Explorer, right click on C:Inetpubwwwrootstations and select Properties. b. Click on the Sharing tab and select Share As. c. For the share name type “stations” and click OK. 6. Make sure that the correct MIME type is set for Windows Media files. For Microsoft IIS 5.0: Getting Started with Windows Media 7
  • a. Open the Microsoft Management Console (Start, Programs, Administrative Tools, Internet Service Manager). (For IIS 4.0, click (Start, Programs, Microsoft Internet Information Server, Internet Service Manager). b. Right click on the default Web site and click Properties. c. Select HTTP Headers. d. Click the File Types button. e. Add the file extensions and associated MIME types listed in the Windows Media Format SDK. f. Click Apply, and the Web site will be updated. Note that any Web server software may be used in place of Microsoft IIS. Support for installing and configuring other Web servers and MIME types must be supplied by the software vendor. For help with setting Windows Media Services MIME types for other common Web servers, see MIME Type Settings for Windows Media Services on the Microsoft Windows NT Server Streaming Media Services Web site. Setup Windows Media Server Install Microsoft Windows Media Services on the Web server, MEDIASRV01. 1. Install Windows Media Services via the Windows Components Wizard (Click Add/Remove Programs, then click Add/Remove Windows Components and then scroll to the bottom of the list and select Windows Media Services) if you are running Windows 2000 Server or Advanced Server. It can be downloaded from the Microsoft Windows Media Technologies Web site if you’re running Windows NT Server 4.0. During setup: a. Choose Do not enable HTTP streaming b. Choose Create Windows Media Services Account c. Accept the default publishing point C:asfroot. 2. Create a Windows 2000/NT network share for the C:asfroot directory called asfroot: a. From Windows Explorer, right click on C:asfroot and select Properties. b. Click on the Sharing tab and select Share As. c. For the share name type “asfroot” and click Ok. Setup Windows Media Player 1. Name the computer designated as the Windows Media client MEDIACLIENT01 and join the MEDIALAB workgroup. 2. Install a Web browser such as Microsoft Internet Explorer 4.01 Service Pack 1 or greater or Netscape Navigator 4.0 or greater. Getting Started with Windows Media 8
  • Configuring Windows Media Components 3. Download and install either the Microsoft Windows Media Player version 6.4 (recommended for corporate intranet use) or version version 7.1 (for internet content) from the Microsoft Windows Media Technologies Web site. Corporate network administrators can configure settings for this player by using the Enterpise Deployment Pack for Windows Media Player 7.1, which can be downloaded from the same location as the player. This section describes how to configure Windows Media components to create and distribute multimedia content. The section is broken into two categories: • Encoding. Describes the steps necessary to encode live or stored content for live or on-demand streaming. • Serving. Describes how to configure Windows Media Services for live or scheduled broadcasts and on-demand streaming. Encoding Before content is available to stream to users, it must be encoded, or converted to Windows Media format. Windows Media Encoder can encode both live content from analog devices, such as a VCR or video camera, digital devices via the Osprey 500 video capture card, and pre-recorded digital content in AVI, WAV, or MP3 format. This section describes how to encode both a live stream for real-time broadcast and stored content for on-demand streaming. Encoding a Live Stream In order to encode a live source in real time, a video capture card is required on the encoder computer. For a list of supported video capture cards, see the list of Windows Media Hardware Providers on the Windows Media Technologies Web site. Additionally, since the quality of a real-time encoded video stream depends greatly on the speed of the encoder’s processor, the faster your CPU the better audio and video quality you will achieve. Your camera’s Video Out and Audio Out should be plugged in to the encoder’s video capture card and audio input device, respectively. If a video camera is not available, you can use a VCR instead to simulate a live feed. Your video capture card should have come with software to test the video input. You may want to verify that the video and audio devices are working before proceeding. Consult the documentation that came with your hardware for details. To begin encoding a live stream: 1. On the encoder computer, ENCODER01, open Windows Media Encoder (Start, Programs, Windows Media, Windows Media Encoder). 2. The Welcome screen should appear with options for creating a new configuration. If it does not, click New or New Session Wizard from the Session menu on the main encoder window. Getting Started with Windows Media 9
  • Windows Media Encoder Welcome Screen 3. Select Broadcast, capture, or convert a file using the New Session Wizard, and then click Next. 4. Select Broadcast a live event from attached devices or computer screen, and then click Next. 5. Select the devices from which you’ll capture your audio and video, and then click Next. 6. Specify the port through which you will broadcast. Click Next. 7. Select a profile from the list. For example, if you will be encoding audio and video for viewing over a dial-up modem and a corporate LAN, choose Video for dial-up modems or LAN (28.8 to 100 Kbps). Click Next. 8. Specify whether you’d like to archive a copy of the broadcast. (When you clickthe archive check box, the encoder will prompt you for a path and file name.) Archiving the file makes it available later for on-demand streaming. 9. Choose whether to include welcome, intermission, or goodbye files to stream at the appropriate times during your broadcast. (If yes, the encoder will prompt you for the file names and offer defaults for each. Click Next. 10. Enter any metadata, such as title, author, copyright, rating, and description, that you want to make available to viewers of your content. Click Next. 11. Review your settings, and click Finish. The main encoder window will be displayed. 12. If you are streaming the content from a Windows Media server using multicast, then point to the Tools menu and click Generate Stream Format File. Enter a path and file name for the stream format file. Stream format files have an .asf file name extension. 13. Click Start to begin encoding. You can preview the input video, output, or both by clicking the desired option from the Display list.on View, Preview. Note that previewing the video can degrade performance during the encoding process. To minimize the effect on performance Getting Started with Windows Media 10
  • either deselect Video on the View menu or decrease the size of the preview window using the Zoom control. Once encoding begins, your live stream is available to a Windows Media server for broadcasting on the Internet or intranet. Your archived file will be ready when encoding is complete for on-demand streaming or scheduled live broadcast. To play the archived Windows Media file in Windows Media Player, double-click the file from Windows Explorer. Encoding Stored Content If the original content is already in digital form such as AVI, WAV, or MP3 format, you can encode the file to Windows Media format and make it available for on-demand streaming or scheduled broadcast. To encode stored content: 1. On the encoder computer, ENCODER01, open Windows Media Encoder (Start, Programs, Windows Media, Windows Media Encoder). 2. The Welcome screen should appear with options for creating a new configuration. If it does not, click New or New Session Wizard from the Session menu on the main encoder window. 3. Click Convert an audio or video file into a Windows Media file, and click Next. 4. Specify the file to be converted. Click Next. 5. Select File will stream from a Windows Media server, and then click Next. 6. Select a profile from the list. For example, if you will be encoding audio and video for viewing over a dial-up modem and a corporate LAN, choose Video for dial-up modems or LAN (28.8 to 100 Kbps). Click Next. 7. Enter any desired metadata. Click Next. 8. Review your settings, and then click Finish. The main encoder window will be displayed. 9. Click Start to begin encoding. You can preview the input video, output, or both by clicking the desired option from the Display list.on View, Preview. Note that previewing the video can degrade performance during the encoding process. To minimize the effect on performance either deselect Video on the View menu or decrease the size of the preview window using the Zoom control. Serving Windows Media Services is a set of services running on a Windows 2000 Server or Windows NT server that streams audio and video content via unicast and multicast to clients. The terms unicast and multicast describe how clients receive data packets from a Windows Media Services server. In a unicast, each client receives a distinct stream from the server that is delivered only when the user initiates a request for that stream. A multicast is a one-to-many connection in which multiple clients can receive the same stream from a server, but have no control over transmission of the stream. There are pros and cons for using both formats. An Getting Started with Windows Media 11
  • advantage of multicast streaming is that it saves network bandwidth, since many users can watch the same stream at the same time. You can try thinking of a multicast as a television broadcast, where a TV station broadcasts their signal via satellite and your television set receives the signal. To the TV station it doesn’t matter if one person or 100,000 people tune in, just one signal is distributed. In a multicast, much like watching TV, viewers cannot start, stop, rewind, fast-forward, or pause the stream and cannot decide when it begins or ends. However, not all businesses are equipped for multicasting. For more information on unicast versus multicast distribution, see the Multicast Streaming: An Introduction whitepaper on the Microsoft Streaming Media Services Web site. This section explains how to configure Windows Media Services to deliver streams to users. This can be done in many ways: • On-demand unicast delivery gives a user active control of a pre- recorded stream. The user can start, stop, rewind, fast-forward, or pause the stream. On-demand connections can quickly use up the bandwidth of a network because each client has its own connection to a server. For example, if 10 users are simultaneously watching a 100Kbps unicast stream, 1Mb (10 x 100Kbps) of bandwidth is being used on the network. • Live unicast broadcast delivery involves unicasting a live source such as a TV or radio station or a corporate address. In the live scenario, a user has passive control of the stream and cannot rewind, fast-forward or pause the stream. • Scheduled unicast broadcast delivery is the same as live unicast, except rather than streaming a live source, pre-recorded media in the form of a Windows Media file is played back from disk in real time. Live unicast and scheduled unicast delivery are most commonly used in environments that don’t support multicast, such as a non-multicast enabled LAN or on most of the Internet. • Live multicast broadcast is similar to live unicast streaming except that streams are delivered via multicast packets which saves network bandwidth. Like watching television, a user cannot control the stream. • Scheduled multicast broadcast is similar to scheduled unicast streaming except streams are delivered via multicast packets. On-demand Unicast To make stored content available on-demand to Windows Media clients, copy encoded Windows Media files to the media server’s home publishing point. During the Windows Media Services installation, you were prompted to specify a directory for the home publishing point that, by default, is created in c:asfroot. A publishing point on a Windows Media Services server can be compared to a publishing point on a Web server: All files in a Web server’s publishing point can be viewed from a Web browser by typing in the HTTP URL to file. For example with Microsoft IIS, the file in the default publishing point, C:Inetpubwwwrootpage1.htm on the computer MYWEBSERVER can be viewed from the Web URL http://mywebserver/page1.htm. Likewise, the file in the default publishing point, C:asfrootfile1.asf on the computer MEDIASRV01 can be viewed from the URL Getting Started with Windows Media 12
  • mms://mediasrv01/file1.asf. The MMS protocol is used to access streams on a Microsoft Windows Media Services server much like the HTTP protocol is used to access Web pages on a Web server1. To make a stream available for on-demand streaming, copy the encoded file C:tempclock.asf from the encoder to the home publishing point, C:asfroot, on the Media Server. To playback the file: 1. Open the Windows Media Player on MEDIACLIENT01 (for Windows Media Player 7.1, click Start, Programs, Windows Media Player. For earlier versions of Windows Media Player, click Start, Programs, Accessories, Entertainment, Windows Media Player). 2. Click File, Open and type mms://mediasrv01/clock.asf. Live or Scheduled Unicast Broadcast To configure a live or scheduled unicast broadcast: 1. Start the Windows Media Administrator on MEDIASRV01 (From Windows 2000, click Start, Programs, Administrative Tools, Windows Media. On Windows NT4, click Start, Programs, Windows Media, Windows Media Administrator). Windows Media Administrator was installed with Windows Media Services. 2. You should see MEDIASRV01 as the selected server in the server drop down box. Under Configure Server click Unicast Publishing Points. 3. In the bottom window titled Broadcast Unicast Publishing Points, make sure the Use wizard to create new broadcast publishing point check box is selected and select Broadcast, New. 4. The Configure and Publish Unicast Broadcast Streams QuickStart wizard appears. Click Next. 5. On the Select publishing point screen, select Create a broadcast publishing point. Click Next. 6. In the Specify source window, select the source for the broadcast: • To broadcast a live stream from an encoder choose Windows Media Encoder as your source. • To broadcast a pre-existing Windows Media file, choose Remote publishing point as your source. 7. Click Next. 1 If HTTP streaming is enabled on a Microsoft Windows Media Server, streams can be accessed via the http protocol as well. For more information about enabling HTTP streaming, see the Microsoft Windows Media Services Help documentation. Getting Started with Windows Media 13
  • Unicast Broadcast QuickStart Wizard 8. In the New broadcast publishing point window (see Unicast Broadcast Wizard figure above), type a name for the publishing point in the Alias box. For example, “LiveStream1”. 9. In the Path box, type the protocol and path to the stream you are broadcasting • If you are broadcasting live from the encoder, type “HTTP://encoder01” and use the default port number of 7007 you chose in the section above, Encoding a Live Stream. • If you are broadcasting stored content, type the URL path to the file you created. For example, “mms://mediasrv01/clock.asf”. 10. Click Next. 11. At Select publishing method, choose Create an .asx file that points at the ASF stream and click Next. 12. Click Finish and save the ASX file in a directory on a Web server that clients can access . For example, MEDIASRV01stationsLiveStream1.asx. Once created, the broadcast can be accessed via a Web browser by typing in the URL to the ASX file on the Web server: http://mediasrv01/stations/LiveStream1.asx. For more information on ASX’s refer to the Using Windows Media section below. Live or Scheduled Multicast Broadcast This section describes the steps necessary to broadcast a live or scheduled multicast stream on an internal network such as an intranet. Multicast broadcasts are not suitable for Internet streaming since most of the Internet is not multicast enabled. For Internet broadcasts, use unicast streaming. Multicast streaming introduces the concept of station configuration files (.nsc files). NSC files contain settings such as the bit rate, video size, codec used, IP address and port of the multicast stream. In an on-demand scenario, this information is read from the Windows Media file’s header. In a multicast however, since a user is connecting to a multicast IP address and not a static file, there must be an external file to configure the player. In a multicast, an ASX file points to an NSC file which sits on a Web server or Windows 2000/NT share that configures the Windows Media Player to load the multicast stream. The following diagram describes the role of an NSC file and the Web server during a multicast broadcast. Getting Started with Windows Media 14
  • 1 2 3 4 Windows Media Client Web Server 5 Your LAN 1. User requests ASX file from web server Windows 2. Web server returns URL to NSC File Media Server 3. Media Player requests NSC from web server 4. Web server returns NSC file with IP address of multicast 5. Media Player connects to multicast IP and plays stream To configure a live or scheduled multicast broadcast: 1. Start the Windows Media Administrator on MEDIASRV01 (for Windows 2000 click Start, Programs, Administrative Tools, Windows Media. For Windows NT4 click Start, Programs, Windows Media, Windows Media Administrator). Windows Media Administrator was installed with Windows Media Services. 2. You should see MEDIASRV01 as the selected server in the server drop down box. Under Configure Server click Multicast Stations. 3. The Multicast Stations page appears. Make sure the Use wizard to create new station check box is selected and select Stations, New. 4. The Configure and Publish Multicast Broadcast Streams QuickStart wizard appears. Click Next. 5. On the Select a station screen, select Create a new station. Click Next. 6. On the Create a new station screen, type a name for the station. For example: “Station1”. For Distribution Mode select Multicast and distribution. Click Next. 7. On the Specify a program and stream name screen, type a name for the program in the Program Name box. For example: “Program1.” 8. In the Stream Name box on the same screen, type a name for the stream. For example, “Stream1”. 9. Check Start Program Once Wizard is finished to make the program immediately available for viewing after the station is created. 10. To play the program repeatedly after it is started, check Replay stream objects once finished (loop). Click Next. 11. Under Specify a Source for the Stream Object box: Getting Started with Windows Media 15
  • • If you are multicasting live from a real-time encoder, choose Windows Media Encoder as your source and click Next. • If you are multicasting a pre-existing ASF file, choose Advanced Streaming Format (.asf) File and click Next. 12. In the Specify Source URL for the stream object window, type the path to the source file or remote encoder you setup in the above section Encoding a Live Stream: • If you are multicasting from a remote encoder: a. Type the protocol, computer name, and port number of the encoder computer in the Source URL box. For example, “http:// ENCODER01:7007”. Click Next. b. In the Specify Stream Format Information window, you will need to use a stream format file generated from the v7.1 encoder. To do this you must use the v7.1 encoder to generate a stream format file. In the v7 encoder, after you've created a session in the encoder, click Tools, Generate Stream Format File. This will create an ASF file. Enter the file here and then click Next. • If you are multicasting a Windows Media file: a. Type the protocol, server name and filename in the Source URL box. For example, “mms://mediasrv01/clock.asf”. Click Next. b. In the Specify Stream Format Information window, type the actual path to the Windows Media file (not the mms path). For example, MEDIASRV01asfrootclock.asf. 13. In the Export Path for the station information window type the path to the saved Windows Media Station Configuration file (.nsc file) in the Path text box. This file should be stored on a Web server (Internet or intranet) or network share (intranet). In this example, save the file on the Web server’s share, MEDIASRV01stationsstation1.nsc. 14. Click Next to bring up the Station Information File URL screen. Since the NSC file was published to a Web server, select Use an HTTP path to the station information file and type the URL to the file. For example, “http://MEDIASRV01/stations/station1.nsc”. Click Next. 15. On the Select publishing method screen, make sure that the create an ASX file that points at the ASF stream checkbox is selected. Click Next. 16. On the Ready to publish screen click Finish. Save the ASX file in a directory on a Web server that clients can access via HTTP. For example, MEDIASRV01stationsstation1.asx. 17. On the Publishing Complete screen, click Test .asx to ensure that the stream is functioning properly. 18. Click Close to complete the creation of the station. To play back the multicast stream, on MEDIACLIENT01, open a Web browser and type in the URL to the ASX file you just created. For example, http://MEDIASRV01/stations/station1.asx. This URL can be Getting Started with Windows Media 16
  • Using Windows Media reference by a hyperlink on a Web page. For information about embedding the player in a Web page, see Embedding the Windows Media Player below. Understanding WMA and WMV Files The Windows Media format is a data format for streaming audio and video content, images, and script commands in packets over a network. Windows Media content can be a static file or a live stream generated by Windows Media Encoder. WMA files are compressed audio files that can be streamed over a network or downloaded from the Internet. WMV files are compressed video files that can be streamed over a network or downloaded from the Internet. The difference between WMA and WMV files are the codecs that are used to compress the audio and video. Both file types are considered to be Windows Media files. An ASX, or ASF Stream Redirector, is an XML text file that redirects the Windows Media Player to a Windows Media file on a Windows Media Services server. ASX files can include information such as the protocol required to view the stream; content metadata, including content author, description, title, and copyright; or custom playlist definitions. Other stream redirector files are WAX and WVX, which serve as redirector files for WMA and WMV files, respectively. Windows Media files are generally stored on a Windows Media server publishing point so that they can be streamed to user’s desktops. ASX, WAX and WVX files reside on a Web server and are used to launch the Windows Media Player and redirect it to the appropriate file or stream. Embedding the Windows Media Player in a Web Page The Microsoft Windows Media Player can be embedded into a Web page and customized via the API documented in the Windows Media Player Software Development Kit (SDK). The code sample below embeds the Windows Media Player as an ActiveX control in Microsoft Internet Explorer and as a plug-in for Netscape Navigator browsers. This code can be automatically generated by the Multicast Station wizard or the Broadcast Publishing Point wizard in Windows Media Services. See the Windows Media Services Help documentation or the Windows Media Player SDK for more information. The code for the Netscape Navigator plug-in is included between the <EMBED> tags. The code within the <OBJECT> tags is used to embed the Windows Media Player ActiveX control. Insert the following code between the <BODY> and </BODY> tags in your HTML document. Replace the three lines pointing to http://mediasrv01/stations/LiveStream1.asx with the URL to your published ASX file. The FileName field can also point directly to the Windows Media file, as in mms://mediasrv01/clock.asf. Getting Started with Windows Media 17
  • Microsoft PowerPoint Integration <OBJECT ID="MediaPlayer" WIDTH=320 HEIGHT=240 CLASSID="CLSID:22D6F312-B0F6-11D0-94AB-0080C74C7E95" CODEBASE="http://activex.microsoft.com/activex/controls/mplayer/en/ nsmp2inf.cab#Version=5,1,52,701" STANDBY="Loading Microsoft® Windows® Media Player components..." TYPE="application/x-oleobject"> <PARAM NAME="FileName" VALUE="http://mediasrv01/stations/LiveStream1.asx"> <EMBED TYPE="application/x-mplayer2" PLUGINSPAGE="http://www.microsoft.com/Windows/ Downloads/Contents/Products/MediaPlayer/" SRC="http://mediasrv01/stations/LiveStream1.asx" NAME="MediaPlayer" WIDTH=320 HEIGHT=240> </EMBED> </OBJECT> <BR><BR> <a HREF="http://mediasrv01/stations/LiveStream1.asx"> Start the streaming media presentation in the stand-alone player.</a> Adding Control Buttons You can also control an embedded Windows Media Player control using scripting languages such as JavaScript of VBScript. For example, you can add a play, pause, and stop button by using the following lines of code in your HTML: <input type="button" value="Play" name="Play" Onclick="MediaPlayer.Play()"> <input type="button" value="Pause" name="Pause" Onclick="MediaPlayer.Pause()"> <input type="button" value="Stop" name="Stop" Onclick= "MediaPlayer.Stop()"> For more information on embedding the Windows Media Player in Web pages and applications, download the Windows Media Player SDK from the Microsoft Windows Media Technologies Web site. One of the most compelling benefits of Microsoft Windows Media components is its tight integration with other Microsoft products such as Microsoft Office, Site Server, Internet Information Server, Internet Explorer, and others. This section includes three examples of how Windows Media components can be used together with Microsoft PowerPoint to deliver live or on-demand audio/ video with slides to users’ desktops. • PowerPoint XP2000 Presentation Broadcast allows users to broadcast streaming PowerPoint presentations in real time to network users. In addition to slides, presenters can broadcast video and audio simultaneously to deliver a live multimedia show online. • Windows Media Publish to ASF is a useful tool for converting PowerPoint presentations into on-demand ASF files. • Windows Media Presenter for Microsoft PowerPoint 97 is an add-in tool that helps you synchronize a PowerPoint presentation with an ASF stream. With the customizable sample Web pages, users can view the audio, video and slides from their Web browser. Getting Started with Windows Media 18
  • PowerPoint XP2000 Presentation Broadcasting With the Presentation Broadcasting feature of PowerPoint XP2000, presenters can broadcast synchronized streaming PowerPoint presentations – slides, video, and audio – in real time, and then store their presentations for on- demand playback. Presenters create their slides using the familiar PowerPoint program and then launch a wizard to schedule, publish, and deliver their presentation. During the presentation, all of the slide transitions and animations are synchronized with the actions of the presenter, allowing the audience to follow the presentation as if they were in the same room as the presenter. Audience members only need a Web browser and the Windows Media Player to view a presentation. For more information on configuring Microsoft PowerPoint 2000 for Presentation Broadcasting, see the article entitled Presentation Broadcasting in PowerPoint 2000 on the Microsoft Developer Network Web site. Windows Media Publish to ASF Using the Publish to ASF wizard, any user can convert their PowerPoint 97 or PowerPoint 2000 slides and narrations into an ASF file for streaming on the company Web site or intranet. To use the Publish to ASF tool: 1. Install the Windows Media Publish to ASF plug-in for Microsoft PowerPoint, which is part of the Microsoft Windows Media Tools 4.1 installation. 2. Open a saved presentation in PowerPoint. 3. If you have not done so already, record slide narrations for your presentation by clicking on Tools, Record Narration. 4. When recording is done, save the presentation and click Tools, Publish to ASF to begin the Publish to ASF wizard. 5. Click OK to export the slides to JPEG images. 6. Select a target bandwidth. For example, intranet (100 Kbps). 7. Select a location to save the ASF file. For example, C:TempPresentation1.asf. 8. Click Finish to end the publishing wizard. Getting Started with Windows Media 19
  • Logging Monitoring Performance To stream the presentation, copy the Windows Media file to a Windows Media publishing point on the Windows Media server. The file can also be played back locally in Windows Media Player by double clicking it in Windows Explorer. Windows Media Presenter Microsoft PowerPoint XP’s2000’s Presentation Broadcasting feature has replaced Windows Media Presenter as the easy-to-use and integrated solution to stream a presentation. However, in environments where PowerPoint XP2000 cannot be used, Windows Media Presenter for PowerPoint 97 is an effective substitute. Windows Media Presenter is installed by default with Windows Media Tools 4.1 which is part of the Windows Media 7 Resource Kit. Instructions for setting up and configuring Presenter is included with the Windows Media Tools documentation (Start, Programs, Windows Media, Windows Media Tools Documentation). See the section titled Windows Media Presenter. Windows Media Services ships with a set of Windows 2000/NT Performance Monitor counters for monitoring streaming server performance. Examples of items that can be monitored include active TCP/UDP/HTTP streams, number of connected users, total send rate as well as late reads and CPU usage. By monitoring certain counters, you can monitor your server’s health and have it alert you when performance degrades. Performance Monitor is also a useful tool in determining your media server requirements for a production streaming environment. Consult the Windows Media Services help documentation for a complete list of available performance counters. To start Windows Media Performance Monitor, on MEDIASRV01, click on Start, Programs, Windows Media, Windows Media Performance Counters. This loads the performance monitor template Nsperf.pmc which includes counters for the Windows Media Unicast service and Windows Media Station service. Windows Media Services provides extensive logging features that enable administrators to view virtually every aspect of a user’s streaming activities on their site. Once the information is logged, usage reports can be generated to Getting Started with Windows Media 20
  • determine aspects like the number of users that played a stream and when and how long they played it. All stream requests from the media server are written to a W3C standard plain- text log file that can be examined or imported into statistical analysis packages for reporting. Examples of fields that are recorded in a unicast log file include the client’s IP address, name of stream played, average bandwidth received, quality received, start time and duration. By default, Windows Media log files are saved in %systemroot%system32 logfiles and have the format NetShow.yymmddiii.log for unicast logs and NetShow.yymmddiiii.log for multicast logs, where yy is the year, mm is the month, and dd is the day. The iii extension specifies the version of the file if more than one file is generated in a calendar day. This section describes how to configure Windows Media services for unicast and multicast logging. Enabling Unicast Logging 1. Open the Windows Media Administrator (Start, Programs, Windows Media, Windows Media Administrator) and click on Server Properties in the left pane. 2. On the Configure Server - Server Properties page, click on Publishing Point Logging and click Enable Logging. 3. Under Period select an interval (Daily, Weekly, or Monthly) or a maximum size for the log file to reach before it is written. For example, select Daily. 4. Accept the default log file directory and click the Apply button. Enabling Multicast Logging Multicast logging for Windows Media Services is handled by an ISAPI extension that runs on a Microsoft Internet Information Server (IIS). This is because during a multicast, a user does not connect directly to the media server. Recall that in order to connect to a multicast, the Windows Media Player loads an NSC file which configures the player to connect to a multicast IP address. Therefore, multicast logging must be recorded at the point when the user requests an NSC from the Web server. 1. If not already installed during Windows Media Services setup, install the Windows Media logging ISAPI application by copying the file nsiislog.dll from C:Program FilesWindows Media ComponentsServer to the scripts directory in your default installation path for IIS, usually C:InetpubScripts. 2. Create a new multicast station using the QuickStart Wizard. 3. When the wizard is complete, if the station is playing, highlight the station and click on the Stop Program. 4. Right click on the new station and click Properties. 5. In the Logging URL text box, type the HTTP URL to the nsiislog.dll. For example, “http://MEDIASRV01/Scripts/nsiislog.dll”. 6. Click OK to save the changes to the station. Getting Started with Windows Media 21
  • Getting Help If you choose not to use the Windows Media ISAPI dll for multicast logging you may build your own customized extension and enter its path in the Logging URL box when configuring the multicast properties in Windows Media Administrator. 3rd Party Reporting Tools Since Windows Media log files are generated in standard W3C format, Microsoft Site Server Express Usage Analysis can be used to generate preliminary reports from Windows Media log files. These reports are useful in determining viewer trends, such as most commonly watched streams, top viewers by domain or total hits by IP address/hostname. Site Server Express is part of the Microsoft Windows NT Server 4.0 Option Pack. For more advanced customizable reports, statistical analysis packages by other third-party software vendors are available, which allow you to report on streaming activity at your site. For a complete list of reporting tool vendors check the Windows Media Software Providers page on the Microsoft Windows Media Technologies Web site. There are a number of ways to get help with Windows Media Technologies: • The Microsoft Windows Media Technologies Web site contains numerous troubleshooting guides and Frequently Asked Questions as well as downloads, product documentation, and latest product news. • Windows Media Technologies Newsgroups on msnews.microsoft.com: o microsoft.public.windowsmedia.technologies o microsoft.public.multimedia.windows.mediaplayer • The MSDN Online Windows Media Technologies Workshop contains guides to help beginning and semi-experienced streaming media content authors and Web developers move into the fast lane. The site includes content creation overviews, step-by-step tutorials, code samples and tools information. • Windows Media Technologies Online Seminars are do-it-yourself online streaming seminars covering a range of hosting and delivery issues. • The Windows Media Technologies Discussion Group is an e-mail discussion group focused on developing for Windows Media Technologies. o To subscribe, send an e-mail message to: WMTALK@discuss.microsoft.com Leave subject blank Message text: subscribe Windows Media your name o To unsubscribe, send an e-mail message to: WMTALK@discuss.microsoft.com Leave subject blank Message text: signoff Windows Media Getting Started with Windows Media 22