I've experimented with renaming files using the split5 format and can tidy up the titlestrips somewhat, by sorting by album I can get the 2 sides of a single in the same titlestrip but not listed correctly, if the program had a second sorting parameter it may then work (Album, Track No.) Ideally the titlestrips would be generated and then randomised as done in DWJukebox.
Hi Vampire, and thank you for your feedback!

Firstly, my apologies for not responding more quickly; it's been quite hectic here recently.
The primary reason the ini option is called 'SongSort', is to preserve a level of backwards file structure compatibility with DWJukebox, but the underlying logic is:
1. If the database is empty or invalid (or the 'UpdateIndex' option is set to true), we read in all the available metadata for each track, and build the database. If ID3 metadata is not sufficient to uniquely identify the track (or is disabled), we apply the selected 'FilenameCrop' option (ie, Split5/Smart, etc.).
2. Apply the selected sorting algorithm, based on each individual track's metadata.
3. Display the title strips.
If I'm visualising this correctly, your file system structure is:
ArtistName
└- Album1
└- Track 'A' Title
└- Album2
└- Track 'B' Title
And your skin.ini file specifies 'SongsPerStrip=Double'.
To 'tie' two tracks together, the album title is used (currently), which (in the example above) would be two similar (but not identical) albums, resulting in a loss of fidelity (assuming we were to rely on the folder name to contain the album name, which we don't do at this point).
If (on the other hand) your track filenames contain ALL the relevant data in Split5 format (ie, album name - disk number - track number - artist - track title; eg: "Singles-01-01-John Denver-Take Me Home, Country Roads.mp3" for the 'A' side, and "Singles-01-02-John Denver-Thank God I'm a Country Boy.mp3" for the 'B' side), regardless of where they're stored in the filesystem, the correct relationship should be in no doubt.
Obviously, my assumption is that, for a single, track number 1 will be the 'A' side, and track number 2 the 'B' side.
So, if (for whatever reason) the track numbers aren't accurately read in during metadata parsing, this relationship will not be stored correctly, and the sorting step will yield inconsistent results, causing the title strips to appear jumbled.
Your suggestion is completely valid, and I'll be reviewing the code for filename-only based metadata creation and sorting methods.
To date, this hasn't been much of a personal priority, as I spent considerable time a few years back running my collection through MusicBrainz Picard to update the ID3 info on every track, and have been focused on ensuring ID3 info works reliably.
I agree completely that it's VITAL to be able to display singles as singles (with A/B side preservation), so I could easily add a 'FileFolder' option to the sorting methods (or maybe just enhance the 'Smart' FilenameCrop method?), to ensure singles are treated as a discreet unit (even when randomly sorted) - the caveat being that the file system would be required to match a highly structured layout and naming convention, which may be fragile and difficult to detect/maintain/enforce.
Also, you're quite right to point out the inaccuracy in the ini documentation regarding Album sorting - that's a holdover from a previous strategy. We always allow Album sorting now, precisely so that singles are grouped together whenever 'SongsPerStrip=Double' is set.

From the latest ini file:
; If SongSort is set to:
; Album: title strips will be sorted by the album name.
; Artist: title strips will be sorted by the artist name.
; Popularity: sort by playcount, in descending order.
; Random: title strips will be randomized.
; Title: sort by song title.
; Type: sort Video tracks from Audio-only tracks (Video first).
; Unsorted: Tracks will appear in the order they're stored in the database.
; Note that Album sort no longer only applies to CD-based skins.
; The default is Artist.
SongSort = Artist
Hope this helps.
