New "Custom Value Conflict" warnings with 0.8.3

[Andre Gosselin]

(19-12-2014 22:48)simoncn Wrote:  

(16-12-2014 00:01)Andre Gosselin Wrote:  Simon,
Following upgrade to 0.8.3, I get "Custom Value Conflict" warnings which never showed up before. Here are some examples:

[code]Warning: custom value conflict for RECENT tag '2014-11' in file Achten, Nicolas/Purcell- How Pleasant 'tis to Love!/01 Purcell- Sound the Trumpet.flac

Apologies for the delay in responding.

When you assign a custom sort value (as you are doing for RECENT and DateAdded), you need to always use the same DateAdded value for the same RECENT value. This means the following would cause a custom value conflict warning:

Some file:
RECENT=2014-11
DATEADDED=2014-11-01

Some other file:
RECENT=2014-11
DATEADDED=2014-11-02

The following would be OK:

Some file:
RECENT=2014-11
DATEADDED=2014-11-01

Some other file:
RECENT=2014-11
DATEADDED=2014-11-01

This behaviour has not changed in 0.8.3.

To fix this problem, you should remove the Recent.Value.sort={DateAdded} setting. To view the album list for the RECENT index tag sorted by the value of the DateAdded tag, you can set Album.sortTags to "DateAdded".

Simon,
Your diagnosis is 100% correct. I was'nt aware of this requirement when assigning a sort value (I should probably have looked more carefully at the manual ...).
Thanks again for this great software.

I wish you a merry Christmas!