|
Yes, you both are right - with these measurements, I've forgotten to set the CPU speed to fixed (all my past measurements used fixed CPU speeds); this is why I haven't noticed the player indeed runs, in general, the CPU at, in general, two steps higher speed setting (for example, 416 MHz as opposed to 208 MHz) than WMP / Conduits Pocket Player and three times higher CPU speed than iPlay.
The fixed results are as follows:
On the A12 x51v,
at a fixed 208 MHz, CPU usage (at this low speed, the CPU usage difference becomes highly visible):
WMP 10: 24%
WinVibe: 28%
iPlay 4.x: 11%
Pocket Player 3.01: 27%
at auto speed, the player runs the CPU at the following speed (in MHz):
WMP 10: 208
WinVibe: 416
iPlay 4.x (without using the built-in CPU applet to set the CPU speed): 104
Pocket Player 3.01: 208
(The CPU usage introduced by actively monitoring the CPU speed / loads (through Services.exe) is 1.5 (1.8 with enabling the load monitoring) at 208 MHz and is, therefore, negligible, as far as the test results are concerned. That is, it's highly unlikely the additional, at 312 MHz, ~1.3% CPU usage caused by monitoring is causing the CPU to switch to 416 MHz from 312.)
Thanks for pointing out the mistake!
__________________
MS MVP- Mobile Devices.
|