New "Custom Value Conflict" warnings with 0.8.3

[Andre Gosselin]

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
...
custom value conflict for RECENT tag '2014-05' in file Alessandrini, Rinaldo/Monteverdi- Ottavo Libro dei Madrigali Vol. 3/01 Monteverdi- Il Ballo delle Ninfe dell'Istro (Madrigals Book 8, canti guerrieri), SV 154 -1. Introduzione al Ballo (Volgendo il ciel per l'immortal sentiero).flac
...
Warning: custom value conflict for RECENT tag '2014-08' in file Bernardini, Alfredo/Telemann- Ouvertures à 8 for 3 oboes, bassoon, strings & cont/01 Telemann- Ouverture in D major for 3 oboes, bassoon, strings and b.c., TWV 55-D15 -1. Ouverture.flac

They all relate to the custom tag "RECENT" on the first track of albums. I use the RECENT tag as an index tag, used to hold the year-month of the date at which an album has been added to my library. I looked at the contents of the RECENT tag of the tracks involved in those warnings with Mp3Tag and Foobar, but could not see anything wrong in the values. I tried removing the RECENT tags, saving, and adding them back with MP3Tag, to no avail.

I have lots of albums with tracks tagged with RECENT=yyyy-mm values, but warnings appear only for a few of those, and only on track 01. Albums showing this warning are nevertheless correctly indexed when I browse the RECENT index.

Here are my Server settings.

Code:

indexTags AlbumArtist, All Artists, Composer, Conductor,Date, Genre,Recent,DateAdded,Label,Catno,Source, #AudioData:AudioData,#AudioQuality:AudioQuality
listVewAlbums 20
mergeFolderAlbums false
tagOptions Album.sortTags={Album, Artist}
Recent.Value.sort={DateAdded}

Recent.Value.sort is set this way because I sometimes reset tagOptions.Album.sorttags to "Recent", so as to view the album list for the RECENT index tag sorted by the value of the DateAdded tag (DateAdded is a custom tag holding the date the album was added to the library, in yyyy-mm-dd format). I checked the value of the DateAdded tags for the albums with warnings, but again could not see any errors in the values.

Could you provide any assistance ?

Thanks for your help.

[simoncn]

(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".

[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!