>i agree its real! of course your niche case is real, AND what that >means is... get ready for it... YOUR MUSIC FOR THAT NICHE CASE IS >HIDDEN RIGHT NOW! bug 9523 hides it just like anything else in >conflict. > Actually, the album isn't hidden right now for me, because it thinks it is a compilation, even though it's not currently being detected as a compilation. As I've been messing about with this album - changing tags, rescanning, etc, to test various situations. This is one of the reasons for the concerns - changing comp tags, album artists and rescanning for new/changed files isn't reliably picking up changes and applying them to existing albums. I'll have to do a full rescan to make it scan the album correctly.
>you seem to prefer that then erlands patch, which would reveal it. > Which would reveal it in the wrong place, and may have other side effects with how it can be browsed to/from other hyperlinks. I'm not really that bothered (1 out of many); as this is a tribute album that I have tagged with an ORIGINAL ARTIST tag, I would find these sorts of albums using Custom Scan to view cover songs. i.e. I wouldn't really browse to a normal "Various Artists" to find this album via artists list. I could find it by browsing albums, or searching. But actually, this sort of album I wouldn't go out of my way to find to play manually - it's the sort of thing that I wouldn't turn off it it came up during random play, which this day is my main way of listening to music. I probably have loads of other things that if I were to try to browse to them I might struggle to find. e.g. where artist sort is missing, so it's sorted under the wrong letter. I've never really been too concerned when I have so much music that I haven't heard. Conversely, I'm not too concerned that at the moment it is appearing within compilation albums when it is not a compilation album. It doesn't bother me much either way. >comp tags aren't valid at all imo, but they de facto exist, so i don't >see how comp=1 is valid while comp=0 isn't. in any case, SBS supports >them, so its moot anyway. (see Phil Leigh? i got your back! :) ) > Comp tags are valid - we're not just talking id3 tags. COMPILATION=0 is not supported by iTunes. in iTunes, an album is either tagged as a comp, or there is no comp tag. That's what it does - it's not possible to do something in the app such that it will store COMPILATION=0. If you do tag COMPILATION=0 in some other tag editor, and load it into iTunes and change something else, when saving tags back it drops the compilation tag. COMPILATION=0 for SBS will mean that songs by differing artists that share the same album name will be split into separate artists for each. i.e. it doesn't make one album not a compilation, it will make several albums. It probably doesn't matter much for albums that really aren't compilations that only have 1 artist on all songs, but it does mean that the album representation in the DB has track artists, rather than normal artists, and that affects browsing in other ways. >besides, it seems to me that RIGHT NOW without erlands patch, changing >that SBS VA naming option would require a full rescan. > No. You can change the name without needing to rescan. Changing the name will display the new name in the Browse Artists list, and change the name of the special contributor (a single artist name is changed to a new name). i.e. The setting currently only relates uni-directionally to decide how to display something. >i wanted an option to turn off mandatory VA auto detection, (bug 8324) >you said no. now you want this to be optional... > I think it's different. With VA auto detection, it can't really be optional, because it has to do something should there not be enough tags to decide what to do with the album. If the outcome is not the user wanted, then tags can be added to tell the scanner what the album should be. With this additional reverse-use of an album artist affecting compilation status, it is not possible to correct through changing tags. >i find it kinda irritating that you didn't respond to that point that >your niche case is just as affected by 9523 as a normal case is though. >is it b/c it then invalidates your niche case as being a valid argument >against erlands patch? > Not at all - it doesn't seem like the right fix to the underlying problem. I'll give you that though - as a patch it is another optional way to avoid the underlying problem. People can decide to apply the patch and run from source code. Or the user could add a COMPILATION=1 tag for albums that they really want to be marked as compilations, and be in full control of everything. Or the user could change the pref setting to something else, such that it doesn't interfere with Various Artists when users don't want to have compilation indicators at all. _______________________________________________ ripping mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/ripping
