Language tag - Title language or Lyrical language?

beetz · August 15, 2019, 2:21am

MusicBrainz makes a distinction between a release’s

title language, and its
lyrical language

See: https://musicbrainz.org/doc/Release

This is probably because they can differ, and I recently found out that it happens more often than I thought.

I believe beets currently fetches the release’s title language as opposed to the work’s lyrical language, although the latter would be more useful – I like to classify my music by lyrical language first, then by genre; the title language almost never matters.

In other words, I would like to avoid having beet move non-English songs in the English directory based on their English title, and have it refer to the work’s lyrical language instead.

Is this tag already implemented in beets? If not, where can I implement it myself?

adrian · August 15, 2019, 3:29pm

Not currently implemented, no. I’m glad you’re interested in trying to add it! The place where we pull stuff out of the MB web service is in mb.py:

github.com

beetbox/beets/blob/master/beets/autotag/mb.py

# -*- coding: utf-8 -*-
# This file is part of beets.
# Copyright 2016, Adrian Sampson.
#
# Permission is hereby granted, free of charge, to any person obtaining
# a copy of this software and associated documentation files (the
# "Software"), to deal in the Software without restriction, including
# without limitation the rights to use, copy, modify, merge, publish,
# distribute, sublicense, and/or sell copies of the Software, and to
# permit persons to whom the Software is furnished to do so, subject to
# the following conditions:
#
# The above copyright notice and this permission notice shall be
# included in all copies or substantial portions of the Software.

"""Searches for albums in the MusicBrainz database.
"""
from __future__ import division, absolute_import, print_function

import musicbrainzngs

This file has been truncated. show original

For example, here’s where we get the current language field:

github.com

beetbox/beets/blob/27e0e7600d05fd7d2e36124b803120ea5cb9e3d4/beets/autotag/mb.py#L403


    if label_info.get('label'):
        label = label_info['label']['name']
        if label != '[no label]':
            info.label = label
    info.catalognum = label_info.get('catalog-number')


# Text representation data.
if release.get('text-representation'):
    rep = release['text-representation']
    info.script = rep.get('script')
    info.language = rep.get('language')


# Media (format).
if release['medium-list']:
    first_medium = release['medium-list'][0]
    info.media = first_medium.get('format')


info.decode()
return info

Moonbase59 · September 23, 2019, 11:56am

This is actually an ever-going question on MusicBrainz. I’m also an editor there and mainly use Picard for tagging.

There is the release’s (album’s) language and script, which denotes the language and script the titles are written in on the cover/booklet.

Then there is the language field per track that denotes the language sung in the song (i.e., lyrics), an ISO-639-3 terminological 3-letter code (i.e., “deu” for German). These codes have been extended by the four special codes [mis], [mul], [und], [zxx] to be used for uncoded language, multiple languages, undetermined and instrumental.

The latter are usually coded in the work, and (sadly) often not available in MusicBrainz. These would go into the “item” (i.e., track) in beets and could be multivalue fields (i.e. separate tags multiple times in Ogg Vorbis comments and ID3v2.4, or separated by the selected separation character(s) in ID3v2.3 (i.e. “deu; eng”, “deu/eng”, “deu,eng”, “deu(NUL)eng”, etc. for a song that contains both German and English lyrics—using “mul” is sometimes not wanted).

If they aren’t available (yet) in MusicBrainz, I usually tag these manually when tagging a new album, because I sometimes need search functionality like “1990s songs sung in Swedish from a female-fronted Swedish hard rock group”.

So yes, it’d be great if beets would support the (lyrics) language(s) per track!

I advise not to blindly overwrite existing language tags from the MusicBrainz data—this could easily destroy collections like mine (almost 150,000 tracks, about 80-85% language-tagged, where MusicBrainz would only deliver about 10-15% of the language tags).

Moonbase59 · September 30, 2019, 8:35pm

@adrian: Should this be in MediaFile? I could probably come up with a PR adding the track (=lyrics) language tags.

EDIT: Oops, already in there, it seems.