Post Reply 
Some "custom value conflict" errors during rescan
17-06-2014, 08:48
Post: #1
Some "custom value conflict" errors during rescan
Simon,

first of all I have to congratulate you for this great server program. Before I used it I had been a longtime user of Twonky but having experienced the added values of Minimserver I immediately changed.

Starting with Minimserver I realized that I had to do a lot of work regarding the metadata of my music files; I usually do it with MP3tag.
My last metadata work was to fill all the "Sort"-fields (AlbumartistSort, ArtistSort, ComposerSort, ConductorSort) with "lastname, firstname" while the corresponding fields are filled with "firstname lastname". I use the tagValue property to sort by the corresponding "Sort-field" (e.g. Artist.value.sort={ArtistSort}) which normally works perfectly as expected. I find e.g. the AlbumArtist "Miles Davis" under "D" (having activated alphaGroup property) and it is dispayed as "Miles Davis".

Rescanning my 1.800 albums and 30.000 items I get 10 "custom value conflict" errors regarding Artist, AlbumArtist, or Composer field. In these cases the "field - fieldSort" logic does not work. I checked the metadata of these albums with MP3tag but found no unnormalties so I suspect that it is not a problem of incorrect metadata.

Any idea?

Thanks in advance for our support
Rainer
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
Some "custom value conflict" errors during rescan - bruemmer - 17-06-2014 08:48

Forum Jump:


User(s) browsing this thread: 1 Guest(s)