Would like to be able to tag and organize artists

[Heathen Hammer]

If it is possible, I'd like to be able to organize artists in much the same ways as I do songs and albums. I'd like to be able to assign tags, groups, etc. to them.

I would also appreciate Finnish language support as well.

[jonap]

+1

[phred]

I would also appreciate Finnish language support as well.

Language support is provided by fellow users. Perhaps you can create the language file and make it available for your fellow Fins. I suggest you take a look at the forum section found under MusicBee & Add-Ons > Customizations > Localization

[Mayibongwe]

If it is possible, I'd like to be able to organize artists in much the same ways as I do songs and albums. I'd like to be able to assign tags, groups, etc. to them.

Might be just me, but I don't get what you mean there. Mind elaborating?

[Heathen Hammer]

I'd like to be able to treat an artist similarly to the way we can treat individual tracks and albums. I want to be able to organize them with tags and groups. Already we can edit artist bios (by editing the DAT files); I want to go a step further.

I don't know if this is possible, but let's see.

[Mayibongwe]

I'm still not able to really picture the use-cases here.
Do you mind providing specific examples? Suppose you had artist_1 and artist_2:
In what context or scenario would you be "organizing them with tags and groups"?

[Fox63]

If it is possible, I'd like to be able to organize artists in much the same ways as I do songs and albums. I'd like to be able to assign tags, groups, etc. to them.

I would also appreciate Finnish language support as well.

+1
I have made many requests in this sense but apparently it is not clear.
Manage artists as you manage songs with separate tags, not a simple and unique biography.
For example:
Artist Name, Alias, Date of birth, date of death, age (which the program could easily calculate), nationality, a link to the site, if it is a group, a single singer and finally a field to insert the complete biography . Possibly a simple table to insert the discography.
In this way the artists could be grouped by nationality or age or something else.

[frankz]

You understand that we can group and categorize songs because each song is an individual file that can be tagged, right?

So what mechanism do you propose we use to group and categorize artists?

The way to do this is to put a custom tag or customs tags for each thing you want to track about an artist in each song file by that artist.  But this is not workable because each song could have multiple artists appearing on it from different countries with different attributes.

There is no file structure for individual artists like there is for individual songs, so this would require a separate database or something which would explode exponentially considering each song can have multiple artists attached to it.

I do not see how this is workable.  Please explain how you think it would work and how it could be accomplished.

[Fox63]

You understand that we can group and categorize songs because each song is an individual file that can be tagged, right?

So what mechanism do you propose we use to group and categorize artists?

The way to do this is to put a custom tag or customs tags for each thing you want to track about an artist in each song file by that artist.  But this is not workable because each song could have multiple artists appearing on it from different countries with different attributes.

There is no file structure for individual artists like there is for individual songs, so this would require a separate database or something which would explode exponentially considering each song can have multiple artists attached to it.

I do not see how this is workable.  Please explain how you think it would work and how it could be accomplished.

I hope I'm clear I'm using google translate.
There is a system. In theory but I also think in practice it can be done with a relational database. When you start a song, which is stored in the library (a database after all), the software takes charge of the selected artist and searches for it in the artist database and once found it will display it in the appropriate form (panel).
Now you no longer need each mp3 file to have an internal biography.
I believe MB currently does the same thing. In fact, when you choose a song, the text that was stored appears in the "artist biography" panel, so that text is already saved in a database.
But everything happens with just one field.
This would involve adding a certain number of fields (Tags) referring to the artist.
A database is just a text file with search references and therefore would not even take up too much disk space.
Imagine an artist panel with an image of the artist at the top right and to the side and below all the data including the discography in which the owned discs are highlighted and can be recalled with a click.I have the impression that few people use the artist's biography precisely because it has no appeal, as it is currently developed.
Briefly: if a tag database was created for mp3s, I don't see why a similar database couldn't be created for artists.

[hiccup]

Imagine an artist panel with an image of the artist at the top right and to the side and below all the data including the discography in which the owned discs are highlighted and can be recalled with a click.

There are already several ways to select an artist and then see what albums and tracks of him you have in your library.
Including having their pictures displayed.

But more importantly, here is a practical question:
How would you populate all the tags that you are suggesting that are important to link to an artist?
Manually? How many artists exist in your library?
And how many tags would you setup for artists?
Would you really be entering all of them for all your artists?

[frankz]

I believe MB currently does the same thing. In fact, when you choose a song, the text that was stored appears in the "artist biography" panel, so that text is already saved in a database.

No, those are individual files that are created from information downloaded from the internet.  You can see them in \%APPDATA%\Internal Cache\ArtistData

Briefly: if a tag database was created for mp3s, I don't see why a similar database couldn't be created for artists.

There is no tag database for mp3s (except in limited cases where you store custom tags to the library database instead of in the files).  There is a library database that contains information about the songs in your library, but not all of the tags associated with those songs. The tags generally exist in the files themselves.

IMO this is an unwieldy idea that will be useful to few.

[Fox63]

Imagine an artist panel with an image of the artist at the top right and to the side and below all the data including the discography in which the owned discs are highlighted and can be recalled with a click.

There are already several ways to select an artist and then see what albums and tracks of him you have in your library.
Including having their pictures displayed.

But more importantly, here is a practical question:
How would you populate all the tags that you are suggesting that are important to link to an artist?
Manually? How many artists exist in your library?
And how many tags would you setup for artists?
Would you really be entering all of them for all your artists?

Imagine an artist panel with an image of the artist at the top right and to the side and below all the data including the discography in which the owned discs are highlighted and can be recalled with a click.

There are already several ways to select an artist and then see what albums and tracks of him you have in your library.
Including having their pictures displayed.

But more importantly, here is a practical question:
How would you populate all the tags that you are suggesting that are important to link to an artist?
Manually? How many artists exist in your library?
And how many tags would you setup for artists?
Would you really be entering all of them for all your artists?

Of course I would use them.
Can the mixed system exist?
You could enter the data manually or with a button download the data from the network.
In any case, keep in mind that I am Italian and MB always finds biographies exclusively in English and therefore I find myself forced to find the biography in my language for each artist and paste it in the specific field.
Hard work but I'm doing it, calmly, but I'm doing it.
Among other things, MB often cannot find a biography for Italian singers due to spelling errors in the name. For example: Loredana Bertè (this is how it is written exactly) on iTunes it is written Loredanda Berte' and in the music explorer it does not exist under any circumstances, unless you write the name incorrectly.
It seems clear to me from the way biography is treated now that few people want to use it.
It would be enough for the programmer to add some fields related to the artist, not the music file.
Then the user could enter them in the info panel.
Of course it is a very long insertion job but it's easy to say that no one would do it and it doesn't mean that it has to be done in a short time. It's not like you're paid to do it. Collecting music is a hobby and the more data you can put in the more you increase the value for you who do it.
There are people who buy a smart TV but don't even have internet, indeed they believe that all the apps it contains are useless, precisely because they don't want to use them. Should we listen to these people?
Sorry but it's already difficult to express yourself through an AI translator, if someone then opposes an idea, it will never go forward.
I apologize for being long-winded

[hiccup]

You could enter the data manually or with a button download the data from the network.

What data exactly, and with what 'button'?

Same as you, I am only sharing my opinion.
I still don't see (m)any users putting in the effort to manually populate all sorts of artist related tags for the artists in their libraries.
And for that reason I don't think it is worth the time and effort of the developer to try and implement something like this.

Also I find the wish a bit vague and general.
Maybe if you would be able to propose something that is more clear and specific, and what would be easier to use I could change my mind.

[Fox63]

You could enter the data manually or with a button download the data from the network.

What data exactly, and with what 'button'?

I wonder if you're making fun of me.
I hope it's the translator's fault!!!!

What data? Tags?
Name of the artist, Alias, Date of birth, date of death, age (which the program could easily calculate), nationality, a link to the site, if it is a group, a single singer and finally a field to insert the complete biography. Possibly a simple table to insert the discography.
The button? Do you want me to write you the source in machine language?

Same as you, I am only sharing my opinion.
I still don't see (m)any users putting in the effort to manually populate all sorts of artist related tags for the artists in their libraries.
And for that reason I don't think it is worth the time and effort of the developer to try and implement something like this.

What tags are there in the program that refer to the artist?
There is currently only one container, not even a tag, that contains the entire text of the bio.
If they are present they will be hidden!!!!
It is clear that no one tries to populate tags that do not exist.

Also I find the wish a bit vague and general.
Maybe if you would be able to propose something that is more clear and specific, and what would be easier to use I could change my mind.

Do you want it to be precise?
Does this image taken from helium clarify your ideas?


This uses the manual system and the automatic system. See the download button?
If helium wasn't slow and complicated tag management it wouldn't be bad for the idea itself.

I can't be clearer than that. Unfortunately, by using a translator you cannot be sure that everything will be understood.

"Also I find the wish a bit vague and general"
For example, this sentence, translated, has no meaning for me.

[hiccup]

What data exactly, and with what 'button'?

The button? Do you want me to write you the source in machine language?

That may be a very good idea.
Perhaps you can create a plugin for this in machine language?