I mainly talk about these:
TSOA - Album sort order
TSOP - Performer sort order
TSOT - Title sort order
These are used for sorting the album in e.g. lists.
The idea of these tags is to replace the artist with performer sort order, album with album sort order and title with title sort order when it comes to sorting.
This is powerful for artist which begin with an article, like The Who or Die Ärzte (Die is a German aticle) The performer sort order tags should look like "Who" and "Ärzte" respecively. In lists, The Who would show up under W, and Die Ärzte under A/Ä.
I know Media Monkey ignores "The" by default. But this is highly specific to the English language. With these 3 tags the user cannot only decide how to sort exactly, it's also possible to be multi-lingual.
I've tested it with "Die Toten Hosen", and they still show up under D. That's why I'm under the impression that these tags are unsupported.
I'm not entirely sure how MediaMonkey handles ID3v2.4 in general. It seems that it writes tags in v2.3, but can read v2.4 tags.
Please support these tags. They're very handy.
NOTE: There are similar tags for AAC and Vorbis as far as I know, which even support artist sort oder AND album artist sort oder (ID3v2.4 only has 1).
Some ID3v2.4 are unsupported/unused
Moderator: Gurus
Re: Some ID3v2.4 are unsupported/unused
Options -> Library -> Appearance -> Ignore prefixes.... Does this help? Me, having there "the,der,die,das,a,az" (no quotes, no spaces, only commas) works perfectkugel. wrote:This is powerful for artist which begin with an article, like The Who or Die Ärzte (Die is a German aticle) The performer sort order tags should look like "Who" and "Ärzte" respecively. In lists, The Who would show up under W, and Die Ärzte under A/Ä.
I know Media Monkey ignores "The" by default. But this is highly specific to the English language. With these 3 tags the user cannot only decide how to sort exactly, it's also possible to be multi-lingual.
-
- Posts: 16
- Joined: Tue Jul 11, 2006 1:15 am
Re: Some ID3v2.4 are unsupported/unused
I agree that MM ought to support these frames. I hate the hackish workarounds that you have to use to get correct sorting behavior...
Re: Some ID3v2.4 are unsupported/unused
Totally agreed on the sortname options. I do believe that something is planned for this in the future though couldn't pinpoint a precise comment.
MM Gold 3.0.3.1183 : Vista HP SP1 (x86) : Zen Stone (2GB)
Zekton: An original MM3 skin by Eyal.
Scripts in Use: Add/Remove PlayStat | Auto Album DJ | AutoRateAccurate | Backup
Case & Leading Zero Fixer | Classification & Genre Changer | Clean Scripts.ini | Clear
Field | Custom Report | Discogs Auto-Tag Web Search | Forget Crossfade | Invert
Selection/Select None | Last 100... | Lyricator | Lyrics to Instrumental | MonkeyRok
MusicBrainz Tagger | My Custom Nodes | Now Playing Art Node | Play History & Stats
Right Click for Reports | Right Click for Scripts | Right Click for Web | Stop After Current
WebNodes
Re: Some ID3v2.4 are unsupported/unused
FYI. The following tags have been wedged into the 'de facto' standard ID3v2.3, as well as the DOA ID3v2.4, thanks to Apple and iTunes:
Title Sort Order = TSOT
Artist Sort Order = TSOP
Album Sort Order = TSOA
Album Artist Sort Order = TSO2
Composer Sort Order= TSOC
Mp3tag was updated last year to support this 'popular' custom tag usage. Yes, for both ID3v2.3 & ID3v2.4. So, if wanted, MediaMonkey could implement usage of these tags for MP3/ID3 and not have to create incompatibility by forcing usage of the ID3v2.4.
Title Sort Order = TSOT
Artist Sort Order = TSOP
Album Sort Order = TSOA
Album Artist Sort Order = TSO2
Composer Sort Order= TSOC
Mp3tag was updated last year to support this 'popular' custom tag usage. Yes, for both ID3v2.3 & ID3v2.4. So, if wanted, MediaMonkey could implement usage of these tags for MP3/ID3 and not have to create incompatibility by forcing usage of the ID3v2.4.
Re: Some ID3v2.4 are unsupported/unused
Hi,
I can't see sorting being implemented in the short term as there would need to be significant changes required in the source code. As MM will only read/write a fixed set of tags you would need to write the strings into one (or more) of your Custom fields and remap these using an external tagger.
I haven't played with any kind of custom nodes, but would have thought that they could be a solution for presenting properly sorted lists.
Daz
I can't see sorting being implemented in the short term as there would need to be significant changes required in the source code. As MM will only read/write a fixed set of tags you would need to write the strings into one (or more) of your Custom fields and remap these using an external tagger.
I haven't played with any kind of custom nodes, but would have thought that they could be a solution for presenting properly sorted lists.
Daz
Re: Some ID3v2.4 are unsupported/unused
I personally think this is pretty low on the 'must have' scale. Anyway, this is likely a 'feature request' and not a bug report for MediaMonkey.