Albums with multiple album artists are not shown when browsing e.g. by album artists

[bbrip]

(09-03-2013 14:23)simoncn Wrote:  In the next release of MinimServer, there will be a new "tag alias" facility that would enable you to define (for example) MAINARTIST as the alias for ALBUMARTIST. This would disable MinimServer's special handling of 1) 2) and 3) above. You could use the existing tag index display renaming facility to display the index choice for MAINARTIST as the name AlbumArtist if you prefer to see this when browsing. This might be the combination you are looking for.

Hi Simon,

thats great to read as the handling of AlbumArtist is one of the very few quibbles I have with MinimServer

thanks again
bbrip

[simoncn]

(09-03-2013 15:18)bbrip Wrote:  Hi Simon,

thats great to read as the handling of AlbumArtist is one of the very few quibbles I have with MinimServer

thanks again
bbrip

I'll be interested in your feedback on this when the next release is available. The "tag alias" facility is being added to solve a different problem, but it has the additional benefit of helping with this situation as well.

[Oliviander]

(09-03-2013 14:23)simoncn Wrote:  In the next release of MinimServer, there will be a new "tag alias" facility that would enable you to define (for example) MAINARTIST as the alias for ALBUMARTIST. This would disable MinimServer's special handling of 1) 2) and 3) above. You could use the existing tag index display renaming facility to display the index choice for MAINARTIST as the name AlbumArtist if you prefer to see this when browsing. This might be the combination you are looking for.

Do I understand this correctly: if I would set MAINARTIST as an alias
for ALBUMARTIST minimserver would use MAINARTIST for 1) 2) and 3)
instead of ALBUMARTIST..
If so this would be great news, as I have already tagged
my collection with a (non multiple) ALBUM_MAIN_SUBJECT tag.
This tag has always only a single entry as it represents the
subdirectory where the file is stored.
(either the first ALBUMARTIST or the COMPOSER)

I did this because I couldn't bring myself to write the Composer in the ALBUMARTIST tag as often suggested for classical collections.

THX for the answer and hopefully for a soon release of the next version

[simoncn]

(10-03-2013 00:42)Oliviander Wrote:  Do I understand this correctly: if I would set MAINARTIST as an alias
for ALBUMARTIST minimserver would use MAINARTIST for 1) 2) and 3)
instead of ALBUMARTIST..

The tag alias facility will allow you to define one or more tags that are treated as aliases for a given tag. For example, the alias definition:

A: B, C

would translate all occurrences of B and C into A (internally within MinimServer) before MinimServer does any other tag processing. Any occurrences of A would be left unchanged.

So, if you define:

MAINARTIST: ALBUMARTIST

this means MinimServer's tag processing wouldn't see any ALBUMARTIST tags but would see MAINARTIST tags instead, and MinimServer would do nothing for 1) 2) and 3).

Quote:If so this would be great news, as I have already tagged
my collection with a (non multiple) ALBUM_MAIN_SUBJECT tag.
This tag has always only a single entry as it represents the
subdirectory where the file is stored.
(either the first ALBUMARTIST or the COMPOSER)

I did this because I couldn't bring myself to write the Composer in the ALBUMARTIST tag as often suggested for classical collections.

THX for the answer and hopefully for a soon release of the next version

You could get what you want (I think) by defining two aliases:

MAINARTIST: ALBUMARTIST
ALBUMARTIST: ALBUM_MAIN_SUBJECT

If you do this, MinimServer would use your ALBUM_MAIN_SUBJECT tags for 1) 2) and 3).

[Oliviander]

(10-03-2013 07:50)simoncn Wrote:  For example, the alias definition:

A: B, C

would translate all occurrences of B and C into A (internally within MinimServer) before MinimServer does any other tag processing. Any occurrences of A would be left unchanged.

This feature sounds really GREAT
The way you describe it, it should be especially useful when you
make it possible to use individual aliases for each contentDirectory
Doing this, you could easily align different collections that are tagged in
complete different ways without having to do any tagging at all !

[simoncn]

(11-03-2013 00:41)Oliviander Wrote:  This feature sounds really GREAT
The way you describe it, it should be especially useful when you
make it possible to use individual aliases for each contentDirectory
Doing this, you could easily align different collections that are tagged in
complete different ways without having to do any tagging at all !

This is an interesting idea, but I'm not convinced that the benefits are worth the extra complexity.

The first step is to support global aliasing and see how people get on with that and what they use it for. After that, we can continue this discussion.

[Oliviander]

(11-03-2013 04:00)simoncn Wrote:  This is an interesting idea, but I'm not convinced that the benefits are worth the extra complexity.
The first step is to support global aliasing and see how people get on with that and what they use it for. After that, we can continue this discussion.

Here I am totally with you, as I would always align my tags
the hard way. (And it is not that hard, if you know ho to use MP3tag)
Or as an alternative, start another Instance of minimserver and
leave the collections as they are. But for that feature proposal
I will start another GENERAL thread soon

[Oliviander]

(09-03-2013 14:23)simoncn Wrote:  The tags that MinimServer reads even if they don't appear in indexTags are ARTIST, ALBUMARTIST, ALBUM ARTIST, TITLE, ALBUM, GROUP, TRACKNUMBER, DISCNUMBER and DISCSUBTITLE.

In the next release of MinimServer, there will be a new "tag alias" facility that would enable you to define (for example) MAINARTIST as the alias for ALBUMARTIST.

Hi Simon,
yesterday I did a little thinking on how to go on with my tagging.
I did some checking how different control points show informations.

And I came to the conclusion, that it would be logical if minimserver,
would also read the composer tag without appearing in the index tags.

Reason:
I like to have the Information displayed in the Controlpoint
with the prename first.

So I use ARTIST ALBUMARTIST and COMPOSER
like: "Eric Clapton" or "Ludwig van Beethoven"

I don't want to have these Entries indexed because in
the search tree I would use

ARTISTSORT, ALBUMARTISTSORT and COMPOSERSORT

Displaying as "Clapton, Eric" or "Beethoven, Ludwig van"

But when I want to see the Composer in the Playing now section
i have to tag it and therefore will have an entry in the search
path which i don't want to have (not elegant! )

An alternative would obviously be to allow an entry
Composer:, with an empty display name resulting in not
showing the indexed tag as an selectable entry.
(which results in an error and in not starting the server by now)

Or did I miss an option ??

[simoncn]

(14-03-2013 08:10)Oliviander Wrote:  But when I want to see the Composer in the Playing now section
i have to tag it and therefore will have an entry in the search
path which i don't want to have (not elegant! )

An alternative would obviously be to allow an entry
Composer:, with an empty display name resulting in not
showing the indexed tag as an selectable entry.
(which results in an error and in not starting the server by now)

Or did I miss an option ??

The next release will provide the ability to specify tags for MinimServer to read without creating index entries for them. As well as the scenario you described, this allows tags to be used for sorting purposes without appearing in the index.

This will probably be supported by adding a new property named fileTags.

In a future release, there will be a "lastNameFirst" setting, which should provide an even better solution to your composer naming requirement.

[Oliviander]

(14-03-2013 08:57)simoncn Wrote:  The next release will provide the ability to specify tags for MinimServer to read without creating index entries for them. As well as the scenario you described, this allows tags to be used for sorting purposes without appearing in the index.

This will probably be supported by adding a new property named fileTags.

In a future release, there will be a "lastNameFirst" setting, which should provide an even better solution to your composer naming requirement.

file tags : Very Good

lastNameFirst : I would rather see a lastNameLast function
as I have completely tagged my collection
the other way round (and prefer it that way)
But actually I think I won't use it, because I do not like things
beeing displayed in another way as they truly are.
I rather use different tags for the following reason:

Here i could cite your entry of minimserver properties :

"Take control of your tagging"
MinimServer doesn't attempt to fix tagging inconsistencies itself. For example, if you've got some tracks tagged with the artist ABBA and others tagged with the artist Abba, MinimServer will show these as separate artists instead of trying to guess which of them is correct. By doing this, MinimServer puts you in control to get your tagging the way you want it, rather than applying its own rules which might not do what you want.

But as long as it is purely optional - no problem with that

THX for the great work