Running into frustration: Title.displayFormat

[simoncn]

For MP3, 3/16 is the correct (standard) way to tag tracknumber/totaltracks. VirtualDJ should be able to handle this correctly and its failure to do this is a bug in VirtualDJ.

When MinimServer reads this information from an MP3 file, it reads the value before the / as TRACKNUMBER and the value after the / (if present) as TOTALTRACKS. This is simple and ensures that what is tagged in the files matches what MinimServer displays.

There are some issues with MinimServer trying to compute TOTALTRACKS if not present. Some examples:

1) The "total tracks" value might be tagged for some tracks of an album but not others. In such a case, should MinimServer use this tagged value for the tracks that don't have it or should it use the actual total number of tracks in the album (if this is different)?

2) Related to 1), if the actual total number isn't the same as the tagged total value, should MinimServer use the actual total number or the tagged total value?

3) The actual total number can't be known until the complete album has been read. This is too late to add new tags to the files because tag processing happens when each file is read. Also, MinimServer can merge albums across folders, which makes this even more difficult.

4) It is an important design principle of MinimServer that it presents exactly the tags that are in the library and doesn't try to "improve" them.

For these reasons, I would be very reluctant to make MinimServer attempt to compute the TOTALTRACKS value if it is not present in the file.

There is a possible workaround. You could define a custom tag named TOTALTRACKS in Mp3tag and set this in each file to the total number of tracks. The track field in Mp3tag would be set to the track number only (as you currently have it). MinimServer would map this number to TRACKNUMBER and would use the custom TOTALTRACKS tagged value for TOTALTRACKS. This should work without any problems in Mp3tag, MinimServer and VirtualDJ.