Beets & Lidarr Tagging

If you have a Lidarr deployment, you may have set-up a level of data tagging, or you're running out-the-box defaults. If you need some guidance in setting it up, then I highly recommend Davo's Community Lidarr guide: https://wiki.servarr.com/lidarr/community-guide

In this guide, he recommends the following for the Lidarr 'Recommended Naming Scheme' (Located in 'Lidarr / Media Management / Track Naming')

Standard Track Format

{Album Title} {(Album Disambiguation)}/{Artist Name}{Album Title}{track:00}_{Track Title}

Multi Disc Track Format

{Album Title} {(Album Disambiguation)}/{Artist Name}_{Album Title}_{medium:00}-{track:00}_{Track Title}

Beets Config (Pathing)

Now that's good and all, but if you're like me, you may be running a beets deployment at some stage as part of your workflow to get that tagging just right 👌.

I've added / updated the following paths in my beets config.yaml file located in my beets config folder (/config/config.yaml)

paths:
    default: $albumartist/$album%if{$albumdisambig, ($albumdisambig)}/$artist_%title{$album}_%if{$track,$track,00}_$title
    singleton: Non-Album/$artist/$title
    comp: Compilations/$album%if{$albumdisambig, ($albumdisambig)}/$artist_%title{$album}_%if{$track,$track,00}_$title
    albumtype_soundtrack: Soundtracks/$albumartist/$album%if{$albumdisambig, ($albumdisambig)}/$artist_%title{$album}_%if{$track,$track,00}_$title

That way, when I run either Lidarr's or Beet's tagging and/or move/copy/rename, the naming convention and scheme is all the same.

I finish it off with a good ole beets import via beet -v import -c -q /music (this command imports my whole library, accepts edits quietly, does copies based on the folder schema and is verbose)