? | Without getting into a "you're comparing apples with oranges" kind of argument, I can't help but wonder why Media Center uses 10x the CPU that Winamp uses when playing an MP3 track with the window minimized. |
My system is far from being the latest-and-greatest, but is easily up to the job of MP3 playback.
I can't help but point the accusatory finger of blame at the skinned interface, as the CPU sits around 5% with the window maximised in a totally idle state. To be fair, I found the same problem with Winamp 5 and so have switched off all Winamp's new skinnable interface, effectively returning to the 2.x version.
Is there still some debug code in there? Or are there maybe a load of WM_PAINTs being thrown around unnecessarily? Or... something else entirely?
Don't get me wrong - I love MC (which is why I registered it after a week!), but am somewhat concerned the CPU problem may get worse as more and more features are added, without considering the processor-challenged such as myself.
--realShady
Media Center Registered 10.0.118 -- C:\Program Files\J River\Media Center\
Microsoft Windows XP 5.1 Service Pack 1 (Build 2600)
Intel Pentium III 800 MHz [reported by MC System Info as 118 MHz!!! ] MMX / Memory: Total - 392 MB, Free - 125 MB
Internet Explorer: 6.0.2800.1106 / ComCtl32.dll: 5.82 (xpsp1.020828-1920) / Shlwapi.dll: 6.00.2800.1400 / Shell32.dll: 6.00.2800.1233 (xpsp2.030604-1804) / wnaspi32.dll: N/A
Ripping / Drive D: Mode:Normal Type:Auto Speed:Max
Drive X: Mode:Normal Type:Auto Speed:Max
Digital playback: Yes / Use YADB: Yes / Get cover art: No / Calc replay gain: Yes / Copy volume: 32767
Eject after ripping: Yes / Play sound after ripping: No
Burning / Drive D: TOSHIBA DVD-ROM SD-R2002 Addr: 2:0:0 Speed:4 MaxSpeed:4 BurnProof:No
Test mode: No / Eject after writing: Yes / Direct decoding: No / Write CD-Text: Yes
Use playback settings: No / Normalization: None