A minor formatting problem

[Pastim]

(22-10-2014 13:11)simoncn Wrote:  

(19-10-2014 11:33)Pastim Wrote:  I recently decided to include the disc and track number in track titles. My tagFormat is therefore like:

Code:

Title.displayFormat={$discnumber$tracknumber^^ - ^:$title^$date^ (^)$rating^ [^]$#AudioData^ [^]}

On multi-disc sets the nth track on the nth disc, instead of displaying, n:n shows just n. so in the example attached, 03:3 shows as just 03 (when there are more than 9 discs or tracks I tend to include a leading 0 for the benefit of systems that don't sort numbers correctly).

The first track on a single disc set is fine, as is the 2nd track on a 2 disc set.

I have tested this with two different control points (upplay and foobar2000).

Edit - As I sat down to listen to a single disc album I noticed track 1 had the same problem as the multi-disc sets (showing 1 instead of 1:1), but other albums don't have the problem I haven't tested much more (too busy listening) but it may be a more general, albeit trivial, issue.

Strange.

Some of this is the result of MinimServer automatically removing duplicate identical values (e.g., 3:3 or 03:03). If the values aren't identical (e.g, 03:3 or 3:03), this shouldn't happen. For some reason, duplicate removal is happening for 03:3 but not for 3:03. I''ll investigate further and post an update.

Why would minimserver detect 'duplicate' data when it is only numerically the same but different in meaning (eg one is disc and one is track, separated by a non-numeric separator)? I assume this detection was introduced for some other reason. It seems a little strange. I spent many hours trying to find out what was wrong with my disc and track numbers before posting here (I tend to assume it's my fault....).

Where else might minimserver do something like this?