Welcome to beets! This guide will help you begin using it to make your music collection better.
You will need Python. Beets works on Python 2.7 and Python 3.4 or later.
macOS v10.7 (Lion) and later include Python 2.7 out of the box. You can opt for Python 3 by installing it via Homebrew:
brew install python3
On Debian or Ubuntu, depending on the version, beets is available as an official package (Debian details, Ubuntu details), so try typing:
apt-get install beets. But the version in the repositories might lag behind, so make sure you read the right version of these docs. If you want the latest version, you can get everything you need to install with pip as described below by running:
apt-get install python-dev python-pip
For Gentoo Linux, beets is in Portage as
media-sound/beets. Just run
emerge beetsto install. There are several USE flags available for optional plugin dependencies.
On FreeBSD, there’s a beets port at
On OpenBSD, beets can be installed with
For Slackware, there’s a SlackBuild available.
On Fedora 22 or later, there is a DNF package (or three):
$ sudo dnf install beets beets-plugins beets-doc
On NixOS, run
nix-env -i beets.
If you have pip, just say
pip install beets (you might need
front of that).
To install without pip, download beets from its PyPI page and run
setup.py install in the directory therein.
The best way to upgrade beets to a new version is by running
pip install -U
beets. You may want to follow @b33ts on Twitter to hear about progress on
Installing on macOS 10.11 and Higher¶
Starting with version 10.11 (El Capitan), macOS has a new security feature
called System Integrity Protection (SIP) that prevents you from modifying
some parts of the system. This means that some
pip commands may fail with
a permissions error, even when you use
sudo. (You probably won’t run
into this if you’ve installed Python yourself with Homebrew or otherwise.)
If this happens, you can install beets for the current user only (sans
sudo) by typing
pip install --user beets. If you do that, you might want
~/Library/Python/2.7/bin to your
Installing on Windows¶
Installing beets on Windows can be tricky. Following these steps might help you get it right:
- If you don’t have it, install Python (you want Python 2.7).
- If you haven’t done so already, set your
PATHenvironment variable to include Python and its scripts. To do so, you have to get the “Properties” window for “My Computer”, then choose the “Advanced” tab, then hit the “Environment Variables” button, and then look for the
PATHvariable in the table. Add the following to the end of the variable’s value:
- Next, install pip (if you don’t have it already) by downloading and running the get-pip.py script.
- Now install beets by running:
pip install beets
- You’re all set! Type
beetat the command prompt to make sure everything’s in order.
Windows users may also want to install a context menu item for importing files into beets. Just download and open beets.reg to add the necessary keys to the registry. You can then right-click a directory and choose “Import with beets”. If Python is in a nonstandard location on your system, you may have to edit the command path manually.
Because I don’t use Windows myself, I may have missed something. If you have trouble or you have more detail to contribute here, please direct it to the mailing list.
You’ll want to set a few basic options before you start using beets. The
configuration is stored in a text file. You
can show its location by running
beet config -p, though it may not
exist yet. Run
beet config -e to edit the configuration in your
favorite text editor. The file will start out empty, but here’s good
place to start:
directory: ~/music library: ~/data/musiclibrary.db
Change that first path to a directory where you’d like to keep your music. Then,
library, choose a good place to keep a database file that keeps an index
of your music. (The config’s format is YAML. You’ll want to configure your
text editor to use spaces, not real tabs, for indentation.)
The default configuration assumes you want to start a new organized music folder
directory above) and that you’ll copy cleaned-up music into that
empty folder using beets’
import command (see below). But you can configure
beets to behave many other ways:
Start with a new empty directory, but move new music in instead of copying it (saving disk space). Put this in your config file:
import: move: yes
Keep your current directory structure; importing should never move or copy files but instead just correct the tags on music. Put the line
copy: nounder the
import:heading in your config file to disable any copying or renaming. Make sure to point
directoryat the place where your music is currently stored.
Keep your current directory structure and do not correct files’ tags: leave files completely unmodified on your disk. (Corrected tags will still be stored in beets’ database, and you can use them to do renaming or tag changes later.) Put this in your config file:
import: copy: no write: no
to disable renaming and tag-writing.
There are approximately six million other configuration options you can set here, including the directory and file naming scheme. See Configuration for a full reference.
Importing Your Library¶
There are two good ways to bring your existing library into beets. You can either: (a) quickly bring all your files with all their current metadata into beets’ database, or (b) use beets’ highly-refined autotagger to find canonical metadata for every album you import. Option (a) is really fast, but option (b) makes sure all your songs’ tags are exactly right from the get-go. The point about speed bears repeating: using the autotagger on a large library can take a very long time, and it’s an interactive process. So set aside a good chunk of time if you’re going to go that route. For more on the interactive tagging process, see Using the Auto-Tagger.
If you’ve got time and want to tag all your music right once and for all, do this:
$ beet import /path/to/my/music
(Note that by default, this command will copy music into the directory you
specified above. If you want to use your current directory structure, set the
import.copy config option.) To take the fast,
un-autotagged path, just say:
$ beet import -A /my/huge/mp3/library
Note that you just need to add
-A for “don’t autotag”.
Adding More Music¶
If you’ve ripped or... otherwise obtained some new music, you can add it with
beet import command, the same way you imported your library. Like so:
$ beet import ~/some_great_album
This will attempt to autotag the new album (interactively) and add it to your
library. There are, of course, more options for this command—just type
help import to see what’s available.
Seeing Your Music¶
If you want to query your music library, the
beet list (shortened to
ls) command is for you. You give it a query string,
which is formatted something like a Google search, and it gives you a list of
$ beet ls the magnetic fields The Magnetic Fields - Distortion - Three-Way The Magnetic Fields - Distortion - California Girls The Magnetic Fields - Distortion - Old Fools $ beet ls hissing gronlandic of Montreal - Hissing Fauna, Are You the Destroyer? - Gronlandic Edit $ beet ls bird The Knife - The Knife - Bird The Mae Shi - Terrorbird - Revelation Six $ beet ls album:bird The Mae Shi - Terrorbird - Revelation Six
As you can see, search terms by default search all attributes of songs. (They’re
also implicitly joined by ANDs: a track must match all criteria in order to
match the query.) To narrow a search term to a particular metadata field, just
put the field before the term, separated by a : character. So
only looks for
bird in the “album” field of your songs. (Need to know more?
Queries will answer all your questions.)
beet list command has another useful option worth mentioning,
which searches for albums instead of songs:
$ beet ls -a forever Bon Iver - For Emma, Forever Ago Freezepop - Freezepop Forever
Beets also has a
stats command, just in case you want to see how much music
$ beet stats Tracks: 13019 Total time: 4.9 weeks Total size: 71.1 GB Artists: 548 Albums: 1094
This is only the beginning of your long and prosperous journey with beets. To keep learning, take a look at Advanced Awesomeness for a sampling of what else is possible. You’ll also want to glance over the Command-Line Interface page for a more detailed description of all of beets’ functionality. (Like deleting music! That’s important.)
Also, check out beets’ plugins. The real power of beets is in its extensibility—with plugins, beets can do almost anything for your music collection.
You can always get help using the
beet help command. The plain
command lists all the available commands; then, for example,
import gives more specific help about the