Readme for Windows Media Encoder 9 Series
January 2003
This documentation provides late-breaking or other information that supplements the documentation for Microsoft® Windows Media® Encoder 9 Series.
Minimum system requirements
Known issues
Legal notice
For information on required and recommended configurations, please read System Requirements.
Unicode folders
It is not possible to install the encoder in a folder that has a Unicode string (for example, C:\???üisgIIli??öÄüߧ) in the folder name.
Video-only sources
If you switch sources from an audio/video source to a video-only source, you will lose 1 to 2 seconds of audio before the switch.
Pausing encoding
When you pause and then resume encoding, audio and video may lose synchronization during playback for a few seconds.
RGB8 pixel format
Using the RGB8 pixel format may result in suboptimal quality in the encoded content.
Digital video devices
It may not be possible to source from legacy digital video (DV) devices when the encoder is installed on a computer running Windows 2000.
Device detection
If you have installed the encoder on a computer running Windows 2000, turning a device on and off will not be detected automatically by the encoder. Instead, you must quit and restart the encoder for your change to be detected.
No statistics
If the first source in a multisource session has a blank stream (audio, video, or scripts), statistics for that stream type will not be displayed in the Monitor panel or in the Encoding Results dialog box. For example, if the first source has a blank video stream, then the Monitor panel and Encoding Results dialog box will not display any video statistics for the entire session, even if subsequent sources have video streams.
Stream format file
If your session uses the Windows Media Audio 9 Voice codec and you generate a stream format file for the session, you may get an error when you specify the stream format file on the server running Windows Media Services. To prevent the error, in the encoder, click Apply in the Session Properties panel before you generate the stream format file. Or, start encoding and then have the server initiate the connection with the encoder (using the format http://encoder:port to obtain the stream format information).
Windows Media Video 9 codec format change
The format of content encoded with the Windows Media Video 9 codec has changed since the release of the Windows Media 9 Series beta. This change will cause some content to be unreadable by some players. The effects of this change are:
- Content created with the beta version of the Windows Media Video 9 codec will decode properly using Windows Media Player or applications built with the Windows Media Format SDK.
- Content created with any version of the Windows Media Video 9 codec will decode properly using the latest Windows Media Player or applications built with the latest Windows Media Format SDK. This content can also be decoded by older applications if they download the Windows Media Video 9 decoder after October 31, 2002.
- To decode content created with the latest version of the Windows Media Video 9 codec, users of Windows Media Player 7.0, 7.1, or Windows Media Player for Windows XP should take the following steps to force the player to download the latest decoder:
- Start Microsoft Internet Explorer.
- On the Tools menu, click Internet Options.
- On the General tab, click Settings, and then click View Objects.
- Delete the object named {33564D57-9980-0010-8000-00AA00389B71}.
- On the Start menu, click Run.
- Type the following command:
rundll32 advpack.dll,LaunchINFSection c:\windows\inf\wmv9dmo.inf,Uninstall
The next time a file containing Windows Media Video 9 content is loaded into Windows Media Player (or a player that implements codec downloading), the latest version of the decoder will be installed. Users of the beta version of Windows Media Player 9 Series must upgrade to a later release to play content encoded with the new Windows Media Video 9 codec.
Key IDs with DRM profiles
The Help incorrectly states that key IDs cannot be edited. If you do edit a key ID, however, keep in mind that the key ID cannot exceed 31 characters, including spaces.
Script commands, time codes, and storing content temporarily
If you enable the following combination of features in a session, the output file will not contain video: script commands as a source, generating or preserving a time code, and temporary storage of content.
Windows Media Encoding Script
Two command line options, -maxpacket and -minpacket, have been added to Windows Media Encoding Script. The options enable you to specify the maximum and minimum size, in bytes, of Advanced Systems Format (ASF) packets that stream across the network. The options apply to single bit rate content that is streamed from a Windows Media server. Acceptable values are either 0 or a number between 100 and 65535. If you specify a value of 0 for -maxpacket, the encoding process automatically generates packets that are no larger than 16,000 bytes. The actual packet size is calculated during encoding. If you are finding that packets are getting lost or fragmented during the broadcast, you can use -maxpacket to reduce the maximum size of the packets. Note that if you are encoding audio content at very high bit rates, you may exceed the maximum packet size. The maximum packet size does not include the networking packet header or the Windows Media packet header.
Windows Media Profile Editor
Windows Media Profile Editor does not include a feature that automatically checks for compatibility with Windows Media Player 7.1. For information about creating content that is targeted for playback in Windows Media Player 7.1, see the topic "Feature Requirements" in Windows Media Encoder Help.
 Back to the top
Information in this document, including URL and other Internet Web site references, is subject to change without notice and is provided for informational purposes only. The entire risk of the use or results of the use of this document remains with the user, and Microsoft Corporation makes no warranties, either express or implied. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, places or events is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
Copyright © 2002-2003 Microsoft Corporation. All rights reserved.
Microsoft, MS-DOS, Windows, Windows Media, Windows NT, ActiveSync, ActiveX, Direct3D, DirectDraw, DirectInput, DirectMusic, DirectPlay, DirectShow, DirectSound, DirectX, FrontPage, JScript, Microsoft Press, MSN, NetShow, Outlook, PowerPoint, Visual Basic, Visual C++, Visual InterDev, Visual J++, Visual Studio, WebTV, Win32, and Win32s are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A. and/or other countries.
The names of actual companies and products mentioned herein may be the trademarks of their respective owners.
Back to the top
|
