Audio player CPU (and, therefore, power) usage benchmark update!
Following is an update to my previous article on the CPU usage of the audio player applications. Please consult the old article on how the data should be interpreted.
I’ve thoroughly benchmarked the current (!!!) versions of the most important media players (including the just-released Pocket Tunes; Resco Audio Recorder 4.01, while it’s not the best for playback, has also been included because of the low MP3 playback CPU usage). All the tests have been made on the HP iPAQ 210 (always) clocked at 624 MHz. n/a stands for not supported. I haven’t tested some (not that important) cases requiring a plug-in.
(HTML original HERE)
Compared to WMP:
* if you only play MP3’s, you’ll want to take a look at Resco, CorePlayer, TCPMP, GSPlayer, Pocket Tunes and MortPlayer in this order, should you want something better than the built-in WMP
* if you play back WMA’s, it’s only CorePlayer that is better than WMP
* if you play back standard (non-HE-AACv2) AAC, on PPC PE devices (that is, Pocket PC phones), you’ll want to go with WMP. On non-phone models, CorePlayer and TCPMP (in this order) are the best; the other (standard) AAC-capable players (Pocket Tunes etc.) aren't that good.
If you want to play back HE-AACv2, the just-released Pocket Tunes 4.1 is your best choice. If you don’t need goodies like libraries, tag reading or AVRCP and can put up with the slightly higher CPU usage, you can get on with TCPMP too. Forget the buggy GSPlayer altogether for HE-AACv2 playback because of the sound quality.
For OGG playback, TCPMP is the best choice. However, its OGG decoder is stated to be a bit inferior in quality; therefore, you might also want to take a look at CorePlayer or GSPlayer. The other OGG-capable players incur a slightly bigger CPU usage.
For FLAC, of the two compatible players, CorePlayer is a bit more battery-friendly. TCPMP isn’t much worse, though.