Author Topic: Bug with "Infer and Update Tags From Filename"  (Read 659 times)

Kareem

  • Newbie
  • *
  • Posts: 3
I'm trying to tag files with the "Infer and Update Tags From Filename" feature

this is the template I'm using  <Album Artist>\<Album> to populate the album artist and album tag fields

Expected behavior:
Musicbee should populate these fields using the folder hierarchy

The behavior I get:
MusicBee populates the artist field instead of the album artist field.
it only populates the album artist if the artist field is already populated, if not then i get this weird behavior


Another weird thing I noticed:
If for example I go along with this weird behavior, "Apply Changes" and let it populate the artist field instead of the album artist one, I expect it now to populate the album artist field the next time I apply the template since the artist field is now populated, but instead it tells me "No changes".
If i manually change the artist field again then it goes back to populating the album artist field when I apply the template again


Is this behavior due to a bug? am I missing something? I'm not sure
Sorry if this is a dumb question, I tried to explain the issue the best I can. thank you in advance for any help


I'm using the latest version of MusicBee 3.6.9202 P

Screenshots:
https://postimg.cc/QBVh3N3F

tjinc

  • Sr. Member
  • ****
  • Posts: 824
Certainly not a dumb question here - I concur that I see the same behaviour.

I would guess that this is tied up with MusicBee's behaviour regards Artist and Album Artist - i.e. if empty, <Album Artist> is assumed to be the same as <Artist>.

So in this situation you are telling MusicBee to set <Album Artist> to "Marley":
 • If <Artist> is empty  - "Marley" is written to <Artist> and <Album Artist> is then assumed to be "Marley".
 • If <Artist>="Marley" - No action taken as <Album Artist> already assumed to be "Marley".
 • If <Artist>="Bob Marley - "Marley" is written to <Album Artist> as it differs from <Artist> value.

I agree that this behaviour is odd but obviously it is up to Steven if he wants to tackle this.

Edit:
Having thought about this a little more, I am not so sure that this behaviour is as odd as it at first appears:
 • It would be strange to have the <Album Artist> field populated and leave the <Artist> field empty.
 • It seems unnecessary to populate <Album Artist> and <Artist> with the same values (although I do have a lot of tracks tagged like this).
Last Edit: June 08, 2025, 10:11:40 PM by tjinc

Steven

  • Administrator
  • Hero Member
  • *****
  • Posts: 34974
The implementation is intentional but i think i am ok with changing it so Album Artist is always populated and also Artist with the same value if its blank

tjinc

  • Sr. Member
  • ****
  • Posts: 824
That sounds like a sensible way to go - and less confusing on first sight.
Hopefully the OP will agree.

Kareem

  • Newbie
  • *
  • Posts: 3
Sorry for the late response guys
Thank you tjinc, your comment explains a lot. I always found it a bit odd how MusicBee does that since Artist and Album artist are not always the same,

"Album artist" is the "main artist" or the artist who the album belongs to, "Artist" on the other hand could be any artist or artists who contributed to a track or multiple tracks within a given album alongside the "Album Artist" or the main artist. at least this is the way I always understood it. when browsing the music files using the regular windows file explorer you'd actually find that "Artist" metadata field is called "Contributing Artists"

that's why there's confusion sometimes when using MusicBee. one example is when using the "Tracks" view where it shows the details of every track in columns, the "Album Artist" column would show the same value as the "Artist" column giving the impression that this value is populated in that track while in reality it is not and just mirrored from the "Artist" value

Other prominent example is when you're choosing between "Artist" and "Album Artist" for the Thumbnail browser:
If you choose "Artist" it lists every single artist that exists in the "Artist" field of all the tracks in your library, but for the tracks that don't have "Artist" populated, these are all grouped together under [Unknown] even if these tracks have "Album Artist" populated, that behavior makes some sense on first sight (since "Artist" is not populated for these tracks) while in reality it should utilize the "Album Artist" field and list the artists there as well,
If you choose "Album Artist" for the Thumbnail browser on the other hand it lists all the artists that exist in both "Album Artist" and "Artist" Fields, which doesn't make sense if you follow the same logic. tracks that only have "Artist" populated and no "Album Artist" should be grouped under [Unknown] as well, artists listed in that view are not always the album artist

I understand now that this behavior is due to MusicBee treating "Artist" as an "Album Artist" which doesn't make a lot of sense and causes confusion,
I think MusicBee should treat the "album artist" as an "artist" and not the other way around because "artist" is not always the "album artist" but the opposite is true


I realize that this is a small detail, but in my opinion it's quite important. in my use case for example, I set the Thumbnail browser to show "Album Artist" for easier browsing, it narrows things down a lot better than just "Artist", that way it's only showing my "main artists" or the artists I have albums for in my library (somewhat like browsing folders), a very clean look.
choosing "Artist" for the Thumbnail browser populates the panel with way more artists than I need or care to look at and it makes the whole thing very cluttered and not very pretty to look at (I'm sure that this view has it's use cases though). but in my case I'm just interested in listing the artists that I have albums for, that's why I'm suing the "Album Artist" view, but then whenever I add new tracks to my library that don't have "Album Artist" I have to manually deal with the stray "Artists" that pop up in there and clutter my view. as a workaround I create a custom "Album Artist" to group these tracks into

Ideally, I think MusicBee should treat "Artist" and "Album Artist" separately or just treat "Album Artist" as "Artist". I think this would eliminate all confusion and make the terms make more sense inside the app

That way the "Artist" view would list all the artists from all the metadata fields it could find artists in, and [Unknown] there would only have the tracks that don't have any artists in all the metadata fields,
and the "Album Artist" view would just list the album artists as the name suggests and [Unknown] there would only have the tracks that don't have an "Album Artist"


Sorry for the wall of text, but that's my two cents on the matter. I hope sharing my perspective would be useful in any way and help users eliminate any possible confusion when using the app.
Lastly I wanna say that MusicBee is a phenomenal app as it is, but it's just my perfectionist side getting the best of me and want to see a great app be even better.

TL;DR
That said, returning to the issue of templates, I personally think <Album Artist>\ should just populate Album Artist and <Artist>\ should just populate Artist,
but making <Album Artist>\ populate both like Steven suggested would also be fine and would make sense, since the "Album Artist" is also an "Artist"