Be that as it may. Is the Language tag incapable of reading / parsing custom or unorthodox information like many of the other tag fields?
Unfortunately I have a nasty habbit of abusing tags to get heaps of custom information through that would otherwise be non accessible in my media player.
Logs uploaded with Description:
Language Parsing by MISTA_J_
FLAC
Test went swimmingly
M4A (MP4)
The exact opposite missing almost everything tagged
OPUS, MP3 & WAV
Did well but still missed one which was intriguing as I expected opus to act similary to FLAC
Side note (slightly unrelated) I noticed the Languages view in the app is on an album vs per track basis. Just wondered if that was a decision made or is that just the “default” . I have a number of albums where one song features an artist who speaks Spanish for example but the rest of the album was all in english. So then that album is now appearing under Spanish albums although there is only one track in the album that actually features any Spanish.
Is this something i can shoot over to feature requests or a mute point?
When tagging these files in mp3tag they are multi value. Meaning the tag “Language” has multiple entries rather than being one field with delimiters. None of those entries should have multiple lines or even extra whitespace as they have been trimmed.
Each of those files was tagged with the exact same language tags. The results of which were inconsistent across the different file types.
I’m also noticing that the FLAC file shows all the Languages I tagged but when I visit the language view of Symfonium Jamaican Patois for example is empty.
Symfonium recognizes that for this library Jamaican Patois is a language but it doesnt show me any albums…“Nothing To Display”
I had assumed this was because of the “Invalid” Languages but for some reason the “ Black Female” Langauage tag works as per usual.
& regarding album level & track level language tags I guess I’m wondering if there is a way I can view all the songs of a particular language using the language view rather than just seeing the albums. More often than not I find myself searching for a specific track rather than an album.
This is interesting. On my end the files were tagged in batch. At the same time in the same manner & checking the tags in my application I can see no carriage return. Ill have to do some digging to figure out why mp3tag is handling the files differently or perhaps a tweak will be required in my scripting.
& the Smart Filters are a very nice feature my only gripe is I have to manually create one for every Language. I think the Smart Filters are better suited for a bit more niche searches in my opinion.
I was able to find the cause of the empty space (extra lines) & remove them, but it appears mp4 (m4a) files only show the first value in Language tags. Is this a drawback for the mp4 container or is there another explanation?
Even in your screenshot of the m4a file there is only 1 listed language even though all the files sent have the same 9 languages tagged.
Ive attempted using a single Language field delimited with “,” & “;” unfortunately the field is read as one long value & not multiple values.
My FLAC MP3 WAV & OPUS Files have 0 issues when tagging the Language field as a multivalue field.
The MP4 container already gives me some slight headaches when tagging so I will be Happily erradicating m4a files from my library.
Unfortunately this means ill now be carrying the originals (archives) & FLAC files that are just bloated m4a but I will happily do so if it means I can more easily tag my library & take advantage of the benefits of vorbis comments
Black Female” Langauage tag works as per usual.
