Script Commands Cannot Be Added When You Use a High Bit Rate Source (270873)
The information in this article applies to:
- Microsoft Windows Media Encoder 7
- Microsoft Windows Media Encoder 7.1
This article was previously published under Q270873 SYMPTOMS
When you convert a high bit-rate file, if the output file uses script commands, the Encoder may become unresponsive. The Encoder initially starts off at a high CPU, and after time, it drops down to about five percent CPU utilization. The encoding process never seems to end, and the Encoder does not display any error messages.
CAUSE
When a high bit-rate source is selected (such as an Uncompressed AVI), scripts are added in real time. The Encoder treats this as a live encode. In some instances, there is so much data going through the Encoder that it cannot keep up with the encoding process. The resulting output is lower than expected quality. This is partially due to system resources, as well as the bitrate, frame rate, and screen size of the source.
WORKAROUND
If script commands are not needed immediately during the encode, convert the file into a WMV or WMA, and then use a tool such as the ASF Indexer or Advanced Script Indexer to add the script commands after the encoding session.
STATUSMicrosoft has confirmed that this is a problem in Microsoft Windows Media Encoder version 7.0.
| Modification Type: | Major | Last Reviewed: | 9/30/2003 |
|---|
| Keywords: | kbbug kbpending KB270873 |
|---|
|