XXHighEnd

Ultimate Audio Playback => Download Area and Release Notes => Topic started by: PeterSt on October 26, 2007, 12:54:20 am



Title: XXHighEnd Model 0.9p (Implements MP3 support)
Post by: PeterSt on October 26, 2007, 12:54:20 am
For those who have MP3's around and want to play them via XXHighEnd, here it is ...
(.MP3 extension only)

More importantly however, chances are high that you find MP3 playback via XXHighEnd to have a better SQ than you are used to. Anyway, it should from theory. By far ...
For those who play MP3's ... please let know your opninion.

As with FLAC, currently MP3 files can not be searched for in the Library Area, nor can they be used in the Galeries.

VBR (Variable BitRate) files were *not* tested. If they don't work as they should, you will notice this by a wrong indication of the duration, which goes along with a too early stop of playing the file when the duration is indicated too short, or currently unknown anomalies when it is indicated too long.

Gapless was tested and found ok, but do note that this greatly depends on the source material, and last parts of a track are very often cut (at encoding to MP3).

Obviously it is handy to show the running bitrate (at judging quality), but currently it's not there. :sorry:

It can be so that Cue encapsulated MP3 albums (etc.) just work (thus, a Cue File with MP3 in there), but it was not tested.

In future, improvement on SQ especially for MP3 (and other lossy formats) are to be expected.


This has been the last upgrade on, say, more major new functionalities, and now first the running bugs are going to be solved in order to get a final 1.00 version.
No bugs were solved in this 0.9p version.


Edit :

Because of the duration calculation (and the means this currently is done), MP3 tracks do not load as fast into the Playlist Area as WAV/FLAC. For one album this takes 4-5 seconds in a well performing system, but with a less performing system (mainly in the disk I/O area) it may take 20 seconds or even more.
It can be expected that in a future version this will be solved (with low priority).