COMAND File Order Algorithm?
If I select an album via "ALBUM" or "ARTIST" that has more than 9 tracks the order selected is track 01, 10, 11, 12, 13, 2, 3, 4, 5, 6, 7, 8, 9. I can see it is using the alphanumeric tracks as the 'decider' for track order.
If I select an album that has less than 10 tracks the order is correct, which is consistent with the twisted logic above.
Here is where things get nuts. I created three files of the same music. One album only had the first nine tracks. The next album had the tracks renumbered (using an ID3 tag editing program) starting with track 01 being track 10, and going up to track 23. I did this so there would be no alphanumerical priority of the 13 track versus the third track. I also made a file with the file names re-written the same way, but didn't change the track number (so the file name for track 3 would be "13-Giorgio". When I put this new SD card in the car it didn't seem to recognize any of these changes and still played the songs in the same screwed up order.
If I select an album via "FOLDERS" it recognizes the correct track order. So at least here, it respects how the musician and producer intended the music to be presented rather than how some German software engineer thinks it should be done.
I'm wondering if it is using the files to figure out the order through Gracenotes, then using that metadata in a demented way to reorder the tracks.
Anybody know what's going on behind the curtain, and better, any way to get around it?
I'll also look to see if there is a DB written on my SD card. I may have to do something to that. Don't know what, but let's see what's there first.







