>I think the settings that requires a rescan is: >- "Separator for Multiple Items in Tags" >- "Group discs" >- "Treat TPE2 MP3 tag as "...
Sounds about right - there aren't many things that cause a rescan. But I think you also missed "Articles To Ignore When Sorting". Also, they are generally things that a user may set only once (or until they get the library how they want it), and then very unlikely that they will change the settings. i.e. if a user has used the character | to separate artists, it is highly likely that they will set that once and never change. Similarly, some people will want to group disks as one album or be seen as several albums (or not be bothered because they don't use disc tags). Once decided, they are not likely to want to change. Also bear in mind that these options are not options that you would usually find in music library applications. They are a bonus that they are here at all. If there weren't options, they wouldn't cause a rescan ;-) Obviously the main reason for requiring a rescan is that the DB content is organised in a format that is more suitable for quickly reading data for display. It could be more generic thus not requiring any rescans, but then it would be a lot slower to browse music. eg. It ignores articles from name tags when scanning, so that it is only done once, not every time the user requests a list of artists or albums. It might be possible to simply recreate the namesort column(s) when the preference is changed, and not rescan everything, but some processing time is necessary, and I guess developers just took the easy option to rescan, rather than write specialised code for this case, as it probably isn't changed often. _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
