So you have beets up and running and you’ve started importing your music. There’s a lot more that beets can do now that it has cataloged your collection. Here’s a few features to get you started.
Most of these tips involve plugins and fiddling with beets’ configuration. So use your favorite text editor create a config file before you continue.
Beets can help you fill in more than just the basic taxonomy metadata that comes from MusicBrainz. Plugins can provide album art, lyrics, and genres from databases around the Web.
If you want beets to get any of this data automatically during the import process, just enable any of the three relevant plugins (see Using Plugins). For example, put this line in your config file to enable all three:
plugins: fetchart lyrics lastgenre
Each plugin also has a command you can run to fetch data manually. For example, if you want to get lyrics for all the Beatles tracks in your collection, just type beet lyrics beatles after enabling the plugin.
Read more about using each of these plugins:
Beets uses an extremely flexible template system to name the folders and files that organize your music in your filesystem. Take a look at Path Format Configuration for the basics: use fields like $year and $title to build up a naming scheme. But if you need more flexibility, there are two features you need to know about:
If you already have music in your library and want to update their names according to a new scheme, just run the move command to rename everything.
Sometimes it can be really convenient to store your music on one machine and play it on another. For example, I like to keep my music on a server at home but play it at work (without copying my whole library locally). The Web Plugin makes streaming your music easy—it’s sort of like having your own personal Spotify.
First, enable the web plugin (see Using Plugins). Run the server by typing beet web and head to http://localhost:8337 in a browser. You can browse your collection with queries and, if your browser supports it, play music using HTML5 audio.
But for a great listening experience, pair beets with the Tomahawk music player. Tomahawk lets you listen to music from many different sources, including a beets server. Just download Tomahawk and open its settings to connect it to beets. A post on the beets blog has a more detailed guide.
Do you ever find yourself transcoding high-quality rips to a lower-bitrate, lossy format for your phone or music player? Beets can help with that.
You’ll first need to install ffmpeg. Then, enable beets’ Convert Plugin. Set a destination directory in your config file like so:
convert:
dest: ~/converted_music
Then, use the command beet convert QUERY to transcode everything matching the query and drop the resulting files in that directory, named according to your path formats. For example, beet convert long winters will move over everything by the Long Winters for listening on the go.
The plugin has many more dials you can fiddle with to get your conversions how you like them. Check out its documentation.