Mnyb;600507 Wrote:
>
> SBS seems to use it's own "internal meta data format" ? and the dB is
> in that format ok ?
>
Nothing wrong with improving the information during scanning but I
agree that it shouldn't improve it based on how you like to browse it.
As long as the improvement of the data is related to making it suitable
to store the flat tag data in a relational database it's fine.
Unless I'm missing something I think there are very few options that
actually requires a rescan and those that does require a rescan is
related to interpretation of the tags and not based on how you want to
browse.
I think the settings that requires a rescan is:
- "Separator for Multiple Items in Tags"
- "Group discs"
- "Treat TPE2 MP3 tag as "...
The "Group discs" option is possibly an option that should be handled
during browsing but the other two feels pretty ok to handle during
scanning to me.
There were some discussion about a two phase scanning when the "new
schema" was discussed 1-2 years ago, the idea was to store the raw tag
values in phase 1 and in phase 2 take the above options into account
and adjust the data appropriately. When an option is changed you would
only have to redo phase 2 which should be fairly quick as it doesn't
require reading the music files.
The main issue which no one has dared to touch yet is that it's not
possible to represent all complex variants in tags, if you want more
advanced data you really need to be able to manage the database and not
only support to import database contents from tags. Especially
situations with multiple artists and sort tags gets complex as you
don't have any easy way to specify which sort tag belongs to with
artist. Basically as soon as you start to handle cases where you have
multiple artists of the same role on a single track you start to get
problems. It works in some scenarios but not in others.
Mnyb;600507 Wrote:
>
> But it is not one format ? as for example "group compilations
> together"
> requries a new scan ? and rebuild of the dB ?
>
Doesn't it take effect immediately without rescanning ?
I don't think the database contents is different based on this option,
it just result in different filtering in the browse menus.
Mnyb;600507 Wrote:
>
> I want to single out this as it is often a part of bugs/request of a
> more radical nature that require the whole thing to be rewritten . And
> therefore newer fixed.
>
I think the database contents and scanning is fine, possibly with the
exception of handling of multiple ALBUMARTIST tags. This whole
discussion is about the browse menus, not about the scanning logic.
--
erland
Erland Isaksson ('My homepage' (http://erland.isaksson.info))
(Developer of 'many plugins/applets'
(http://wiki.slimdevices.com/index.php/User:Erland). If my answer
helped you and you like to encourage future presence on this forum
and/or third party plugin/applet development, 'donations are always
appreciated' (http://erland.isaksson.info/donate))
------------------------------------------------------------------------
erland's Profile: http://forums.slimdevices.com/member.php?userid=3124
View this thread: http://forums.slimdevices.com/showthread.php?t=84475
_______________________________________________
beta mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/beta
