Hello
Does anybody know how to add the Sort Artist colum to the files list view?
I know I can custmize the file list view
Already read the documentation Customization of Tag Panel and File List & Format Strings and Available Placeholders but I can’t understant what to write here:
Name: should be Sort Artist
Field: I have no idea what to write down.
Value: I have no idea what to write down.
When a song has sort album field data extended tags is showed as ARTISTSORT.
Thank you in advanced!
The correct tag field name in this case would be ARTISTSORT. In fact the field mapping table shows there are five different sort fields currently built-in and mapped for most file types.
ALBUMSORT
ALBUMARTISTSORT
ARTISTSORT
COMPOSERSORT
TITLESORT
Others can be created as a custom tag but it is unlikely most other programs will readily be able to use them. They could be helpful within mp3tag though. Maybe also Foobar or MusicBee. Examples might include something like CONDUCTORSORT, ORIGARTISTSORT, ORIGALBUMSORT, MOVEMENTNAMESORT, or WORKSORT just to name a few potential candidates.
You could have a look at the other column definitions ...
Field: to which field the displayed information should be written
Value: get the set data and display it. If there is no data (as none has been set so far, the column stays empty.)
If you get data from read-only fields, then leave Field empty.
So “ARTISTSORT” is the value? (is what I have to write down in the Value field?). I do not think so, artist value is a weird code “$metasep(artist,\)” not “ARTIST”.
& what about the field? Artist field is “%artist%” so probably Artist Sort field is “%artistsort%”?
BTW I don’t know how to get to the table you shared Motley Tag Field Mappings Table – Mp3tag Documentation
When I read the Customization of Tag Panel and File List & Format Strings and Available Placeholders the link you shared was not mentioned.
Furthermore, do not understand for what is this mapping table useful, it does not seem it says which data write down in the Value & Field field.
I just say this to let you know that for somebbody who is beginning is hard to uderstand & follow you.
I do not understand your message ohrenkino.
If I look to artist columm I see
Name: Artist
Value: $metasep(artist,\)
Field: %artist%
So?
Everything is fine, I would say.
You define a field to which a value should be written. To get an existing value, you set a format string where to find it. In your case with ARTIST it gets the contents from all possibly existing fields of the type ARTIST and displays them separated by \\. This string then gets written back to the target field, in this case %ARTIST%.
For the sorted artist it would be
Value: $meta_sep(artistsort,\\)
Field: %artistsort%
Ok, Thank you, I understood both of you.
What I don’t get is:
$meta_sep(***,\\) where *** is the name of the field? How Is supposed I should know/learn this code? (this code is not listed here Format Strings and Available Placeholders )so %***% is a placeholder & $meta_sep() & \\ are script functions.
Just curious, do you know this code before starting using MP3tag?
It is based in a common computing code/language or users must learn when starting to use the software?
Ok I have tested this configuration:
This was my first idea of what I should write down in the fields, in english adjectives usually goes before the name, so it is Sort Artist & not Artist Sort, but surprisingly you suggested me the opposite & it worked!
Just wondering how artistsort works but sortartist no.
I assume this means in the file there’s no field called sortartist but artistsort but what I do not understand is how you know it: how you discover that the correct field name is artistsort. Is there a list of the names?
I have used many programming languages in the past. The basic functions are the same within mp3tag. But like all apps there is a learning curve. I have been using mp3tag for a very long time and there are still features I learn about all the time. The best way to learn is to try it. Keep a backup or two just in case for recovery.
This was already shared. The list of fields are the common ones mp3tag is already configured to provide. You will find Artistsort along with many others fields in this list.
The difference is: ARTISTSORT maps to a standard field in the corresponding tag format while SORTARTIST is a user-defined field which is supported by only very few players.
User-defined fields are also valid fields but it is hard for an application to guess what could be meant by the name as this probably depends a lot on the individual preferences and languages.
I think this is the crucial part of the conversation that wasn't highlighted enough.
When you inspect a file via Extended Tags, you'll see all the fields with their FIELDNAME as Mp3tag recognises them. You can reference these fields using placeholders like %FIELDNAME% in various Mp3tag functions.
In your example, you can see ARTISTSORT in Extended Tags, so you can use %ARTISTSORT%, e.g., when adding a new column to the file list.
Thanks for the advice because with a very important library of 32k files I don’t want to take risks.
Yeah true.
Yess, so this list Tag Field Mappings Table – Mp3tag Documentation points to the let’s say universal or common fields that you should use if you want to use software created by others (not by you). Also, even the field exist that does not necessary mean the software use that field, you must cheeck which fields are using each software of your enviroment to have control on where to write data. I guess you do that by writting data on a test file on each field on each software & cheecking the Extended Tags (that shows you all the fields that have data).
All correct here, thank you Florian!
