FIX: No sound is produced when you try to play some MP3 files in Windows Media Player on a Windows CE 5.0-based device (908955)



The information in this article applies to:

  • Microsoft Windows CE 5.0

SYMPTOMS

Consider the following scenario. You have MP3 files that play correctly in Microsoft Windows Media Player on a Microsoft Windows XP-based computer. You try to play the same MP3 files in Windows Media Player on a Microsoft Windows CE 5.0-based device. In this scenario, the Windows Media Player application will behave as if it is actually playing the MP3 files. The time increases, and the progress bar moves steadily from left to right. However, no sound is produced.

CAUSE

This problem occurs because a problem existed in the reference code for the original release version of the MP3 encoder/decoder logic. This problem caused the CRC calculation to be incorrect. Therefore, many early MP3 decoders and players that were based on this reference code also experience this problem. Some MP3 files that still exist today include this incorrect CRC value embedded in the MP3 file. Currently, most new MP3 players ignore the CRC check because files and network streams usually have their own error correction and detection schemes.

When Windows CE 5.0 computes the CRC, Windows Media Player produces no sound to "correct" this error, if the error exists.

This software update updates Windows CE 5.0 so that Windows CE 5.0 ignores the CRC check on MP3 files. Therefore, MP3 files that contain a bad CRC value can play on Windows CE 5.0-based devices.

RESOLUTION

Software update information

A supported software update is now available from Microsoft as Windows CE 5.0 Core OS QFE 908955. To resolve this problem immediately, click the following article number for information about obtaining Windows CE Platform Builder and core operating system software updates:

837392 How to locate core operating system fixes for Microsoft Windows CE Platform Builder products

Prerequisites

This software update is supported only if all previously issued software updates for this product have also been applied.

Restart requirement

After you apply this software update, you must perform a clean build of the whole platform. To clean the platform, click Clean on the Build menu. To build the platform, click Build Platform on the Build menu. You do not have to restart the computer after you apply this software update.

Software update replacement information

This software update does not replace any other software updates.

File information

The English version of this software update package has the file attributes or the later file attributes that are listed in the following table.
File nameFile sizeDateTime
Wincepb50-051020-kb908955-armv4i.msi628,22420-Oct-200522:00
Wincepb50-051020-kb908955-mipsii.msi630,78420-Oct-200522:00
Wincepb50-051020-kb908955-mipsii_fp.msi632,83220-Oct-200522:00
Wincepb50-051020-kb908955-mipsiv.msi635,39220-Oct-200522:00
Wincepb50-051020-kb908955-mipsiv_fp.msi636,41620-Oct-200522:00
Wincepb50-051020-kb908955-sh4.msi608,25620-Oct-200522:00
Wincepb50-051020-kb908955-x86.msi610,81620-Oct-200522:00
The English version of this software update has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
File nameFile sizeDateTimePath
L3aud32s.lib419,84204-Oct-200518:54Public\Directx\Oak\Lib\Armv4i\Debug
L3aud32s.lib344,80004-Oct-200518:53Public\Directx\Oak\Lib\Armv4i\Retail
L3aud32s.lib415,07404-Oct-200518:54Public\Directx\Oak\Lib\Mipsii\Debug
L3aud32s.lib360,77204-Oct-200518:54Public\Directx\Oak\Lib\Mipsii\Retail
L3aud32s.lib413,30604-Oct-200518:55Public\Directx\Oak\Lib\Mipsii_fp\Debug
L3aud32s.lib346,18404-Oct-200518:55Public\Directx\Oak\Lib\Mipsii_fp\Retail
L3aud32s.lib414,53404-Oct-200518:55Public\Directx\Oak\Lib\Mipsiv\Debug
L3aud32s.lib346,76604-Oct-200518:55Public\Directx\Oak\Lib\Mipsiv\Retail
L3aud32s.lib415,96604-Oct-200518:56Public\Directx\Oak\Lib\Mipsiv_fp\Debug
L3aud32s.lib344,85804-Oct-200518:56Public\Directx\Oak\Lib\Mipsiv_fp\Retail
L3aud32s.lib356,93204-Oct-200518:53Public\Directx\Oak\Lib\Sh4\Debug
L3aud32s.lib317,34804-Oct-200518:53Public\Directx\Oak\Lib\Sh4\Retail
L3aud32s.lib389,32604-Oct-200518:53Public\Directx\Oak\Lib\X86\Debug
L3aud32s.lib338,73204-Oct-200518:52Public\Directx\Oak\Lib\X86\Retail

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Modification Type:MinorLast Reviewed:7/26/2006
Keywords:kbBug kbfix kbQFE kbpubtypekc KB908955 kbAudOEM