In this thread I'll try to describe some of the bugs in "Look for new and changed" files - I think this is more useful than creating many single bugs - for I think, there is ONE BIG bug ;-) And to say it clearly - it is NOT limited to the known "Cover art bugs".
I've made the experience that it ONLY works good for NEW files - it doesn't recognize CHANGED files (properly) and it doesn't always delete DELETED tags. Three examples: a) I've had some miss-spellings in my library like "Maroon5" and "Maroon 5" or "Amy Macdonald" and "Amy MacDonald" both of them shown as 2 separate artists (or at least 4 ;-)) So - I corrected and harmonised spelling - did a "new and changed" scan ... But nothing has changed! There are still TWO different artists for each name - and if I click the "miss-spelled" one (that actually isn't in my database anymore) it lists ALL the albums he WAS on BEFORE the rescan. If I click the single albums, - some are shown as "empty" - some show the files with the "new" (correct) spelling If I now click the files and get BACK to the album - the album NOW is empty... This leads me to the conclusion, that "new and changed" hasn't read the tags from this files at all. BUT: By changing the artists name, it got a new timestamp - and it has been listed in the "new music" section. So it leads me to another conclusion: - The "new and changed scan" sees the file - it recognizes the file as "changed" - in SOME cases it reads the new tags and deletes the old - in SOME cases it doesn't read the new tags - in EVERY case it doesn't remove the "old spelling" from database b) I bought a single from itunes - later on itunes informed me, the whole album is available and I downloaded the "missing" tracks only. I put them in a new folder - but forgot to change the "ALBUM" tag. So it's been like Track 01 .... album tag = ALBUM Track 02 .... album tag = ALBUM Track 03 .... album tag = ALBUM ... Track 11 .... album tag = SINGLE After I saw this, I corrected "track 11" so it was Track 11 .... album tag = ALBUM ... and did the rescan ... The result has been, there were still ALBUM and SINGLE in my database - BOTH listed under "new music" but with the "old" album tag. So it leads me to once again conclusion: - The "new and changed scan" sees the file - it recognizes the file as "changed" - it DIDN'T read the changed tags and didn't do any changes to my database... and once again: By "clicking" the file, it reads the new tags and shows it. BIG conclusion: "new and changed" doesn't do what it should do - it doesn't read changed files and changes the database. The only way to really change files in the database is to add EVERY file manually (by "folder browsing") and/or clicking EVERY new/changed file. This isn't usuable at all - I think - it's not usuable for "the freaks" for they have to many new files and changes and it's not usuable for the "everyday" user who expects some comfort... I think the usual user will have his library, scan it once - add some new albums, do a rescan and expects "everything to be fine". There of course is c) The third thing, I described before, that if you add new tracks to an existing album, they are shown as SEPERATE album with the same name ... http://forums.slimdevices.com/showthread.php?95104-Any-work-on-LMS-7-8-anymore&p=704334&viewfull=1#post704334 I think, "new and changed" needs a big re-work... :-(( ------------------------------------------------------------------------ frank1969's Profile: http://forums.slimdevices.com/member.php?userid=31156 View this thread: http://forums.slimdevices.com/showthread.php?t=95222 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
