MinimServer Conflicting Values in Filter Warning

[qblack]

(03-09-2017 20:52)simoncn Wrote:  The short answer is that you need to change EncodingTime.yearMonth.index to EncodingTime.yearMonth.index.sort. To understand why, read on....

Suppose your library contains albums tagged with a mixture of the following:

COMPOSER=Johann Sebastian Bach
COMPOSER=Bach, J.S

You decide that you want to see all these in your composer index as J.S. Bach, so you configure MinimServer to set all the index values to J.S. Bach. Because this doesn't change the sort values, you would get index entries for J.S. Bach in both the B and J sections of the Composer index. The J.S. Bach entry in the B section would contain everything tagged COMPOSER=Bach, J.S and the J.S. Bach entry in the J section would contain contain everything tagged COMPOSER=Johann Sebastian Bach.

This doesn't seem like a good idea, so MinimServer doesn't allow multiple tag values with the same index value and different sort values.

In your case, the sort values are so close together ('2009-09-16 10:36:30' and '2009-09-16 10:34:16') that this problem is unlikely to arise. However, the sort values are different, so MinimServer produces a warning to tell you about it.

Simon,

Wonderful! Detailed response in what seemed like minutes... on a Sunday! I've been using MinimServer for some years but only now do I feel I understand the difference between .sort and .index (in other applications I tend to think of indexing as sorting, I guess). So this has been invaluable, such a basic concept to finally grasp…

The reason I sought help on the warnings above was due to weird behaviour I was getting at my control point after creating some Groups in various albums and changing some Minimserver properties at the same time. I thought the warnings may have been another symptom of the one problem. Getting to these newly-created Groups by first selecting Month Added (ENCODINGTIME alias) at the first screen, then Composer, etc. brought up a Group I couldn't "get into.", though tapping it said "3 tracks added" (Naim app). Nothing actually happened. Getting to this Group via another route (say Composer first), worked as expected. Anyway, I suspect now that this was a caching problem and it was solved by a restart. Which brings me to the next point: how does Rescan in MinimWatch actually work? I notice sometimes that a rescan is quick, as if incremental, when what is needed is a complete rescan of the whole library (to fix problems such as that above). Is Restart the action needed for the latter?

As always, many, many thanks for your wonderful product, support and engagement. Your product is the icing on the cake.