# \[X\] Mapping failure on ALBUMARTIST
**URL:** https://community.mp3tag.de/t/x-mapping-failure-on-albumartist/10022
**Category:** No Bugs
**Created:** [March 3, 2010, 2:15pm UTC](https://community.mp3tag.de/t/x-mapping-failure-on-albumartist/10022 "2010-03-03T14:15:15Z")
**Posts on this page:** 12
**Page:** 1
### Author:  [@chrisjj](https://community.mp3tag.de/u/chrisjj)
#### Post date: [March 3, 2010, 2:15pm UTC](https://community.mp3tag.de/t/x-mapping-failure-on-albumartist/10022/1 "2010-03-03T14:15:15Z")
To solve the long-standing issue of the existing UI property BAND not showing FLAC ALBUMARTIST. [http://img46.imageshack.us/img46/7374/picf.png](http://img46.imageshack.us/img46/7374/picf.png) ...
... I added a mapping rule "VorbisComment ALBUMARTIST BAND"), and it works as far as BAND display is concerned, but silently breaks the display of %albumartist%, causing it to falsely show null. [http://img9.imageshack.us/img9/1950/picvh.png](http://img9.imageshack.us/img9/1950/picvh.png)
This seems like a bug.
Attempting to workaround this by adding a mapping "VorbisComment ALBUMARTIST ALBUMARTIST" fails - regardless of the order of the two mapping rules. [http://img641.imageshack.us/img641/5581/picj.png](http://img641.imageshack.us/img641/5581/picj.png)
In fact even having the workaround rule without the problem rule (BAND) blanks the display of %albumartist%. [http://img246.imageshack.us/img246/5721/piciq.png](http://img246.imageshack.us/img246/5721/piciq.png). This too seems like a bug.
---
### Author:  [@dano](https://community.mp3tag.de/u/dano)
#### Post date: [March 3, 2010, 2:37pm UTC](https://community.mp3tag.de/t/x-mapping-failure-on-albumartist/10022/2 "2010-03-03T14:37:42Z")
The content of albumartist is now grabbed by BAND so no display in albumartist. Otherwise you'd think you had two tag fields.
---
### Author:  [@chrisjj](https://community.mp3tag.de/u/chrisjj)
#### Post date: [March 3, 2010, 2:53pm UTC](https://community.mp3tag.de/t/x-mapping-failure-on-albumartist/10022/3 "2010-03-03T14:53:58Z")
> [@dano](#):
>
> Otherwise you'd think you had two tag fields.
If I would think that, I'd still think that currently - just one shows blank.
But two columns does not mean two tag fields. I already have multiple columns for a single tag field e.g. Album and EAN (taken by regexp from album).
And actually in this case I do have two tag fields - BAND (TPE2) and ALBUMARTIST - and the current mapping behaviour prevents me from showing which is active.
---
### Author:  [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [March 3, 2010, 6:47pm UTC](https://community.mp3tag.de/t/x-mapping-failure-on-albumartist/10022/4 "2010-03-03T18:47:56Z")
dano is right, marked as "No Bug"
---
### Author:  [@chrisjj](https://community.mp3tag.de/u/chrisjj)
#### Post date: [March 3, 2010, 6:56pm UTC](https://community.mp3tag.de/t/x-mapping-failure-on-albumartist/10022/5 "2010-03-03T18:56:35Z")
> [@Florian](#):
>
> marked as "No Bug"
Even the failure of "VorbisComment ALBUMARTIST ALBUMARTIST" ??
---
### Author:  [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [March 3, 2010, 7:01pm UTC](https://community.mp3tag.de/t/x-mapping-failure-on-albumartist/10022/6 "2010-03-03T19:01:50Z")
Yes, adding multiple mappings for one field simply makes no sense.
---
### Author:  [@chrisjj](https://community.mp3tag.de/u/chrisjj)
#### Post date: [March 3, 2010, 8:32pm UTC](https://community.mp3tag.de/t/x-mapping-failure-on-albumartist/10022/7 "2010-03-03T20:32:44Z")
It makes sense to me because it is the only way for me to see which file field a UI field value came from.
Not even Advanced Tags shows the file field.
Unless you know another way?
---
### Author:  [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [March 3, 2010, 8:36pm UTC](https://community.mp3tag.de/t/x-mapping-failure-on-albumartist/10022/8 "2010-03-03T20:36:31Z")
Yes, the format-specific field name is then not visible anymore (which is by intention, since you want to have one field name for a specific field regardless of the format-specific field names).
---
### Author:  [@chrisjj](https://community.mp3tag.de/u/chrisjj)
#### Post date: [March 3, 2010, 8:48pm UTC](https://community.mp3tag.de/t/x-mapping-failure-on-albumartist/10022/9 "2010-03-03T20:48:05Z")
Actually I don't. I want to have one field name for all formats where required and still have format-specific names where required.
Florian, I have to ay I think this mapping implementation is misconceived. It would be better to map in the reverse direction - EDIT: each UI field name from a single file field name (for each format). Just like the current column label maps onto a single editable UI field. This would allow what is currently needlessly disallowed, and correctly disallow what is currently accepted but non-operative - multiple file field names (for the same format) onto the same UI field name. And thereby not break existing functionailty of the previous version. I hope you'll consider this change.
---
### Author:  [@DetlevD](https://community.mp3tag.de/u/DetlevD)
#### Post date: [March 4, 2010, 4:29am UTC](https://community.mp3tag.de/t/x-mapping-failure-on-albumartist/10022/10 "2010-03-04T04:29:12Z")
> [@chrisjj](#):
>
> ... multiple format fields onto the same UI fields. ...
Yes, on this way I understand intelligent functional field mapping.
One UI field for all different tag formats, simple 1:n mapping.
All power emanates from the user, not from the tag format. 😉
DD.20100304.0629.CET
---
### Author:  [@chrisjj](https://community.mp3tag.de/u/chrisjj)
#### Post date: [March 4, 2010, 9:11am UTC](https://community.mp3tag.de/t/x-mapping-failure-on-albumartist/10022/11 "2010-03-04T09:11:58Z")
> Yes, on this way I understand intelligent functional field mapping.
> One UI field for all different tag formats, simple 1:n mapping.
Sorry Detlev, I was unclear. I have edited my post to clarify.
---
### Author:  [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [December 28, 2018, 2:28pm UTC](https://community.mp3tag.de/t/x-mapping-failure-on-albumartist/10022/12 "2018-12-28T14:28:33Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.