This page describes the internal API of beets’ core. It’s a work in progress—since beets is an application first and a library second, its API has been mainly undocumented until recently. Please file bugs if you run across incomplete or incorrect docs here.
The Library Class¶
Library(path, directory[, path_formats[, replacements]])¶
A database of music containing songs and albums.
Given an album ID or an item associated with an album, return an
Albumobject for the album. If no such album exists, returns None.
Create a new album consisting of a list of items.
The items are added to the database if they don’t yet have an ID. Return a new
Albumobject. The list items must not be empty.
Transactionobject for interacting directly with the underlying SQLite database.
Library class provides the basic methods necessary to access and
manipulate its contents. To perform more complicated operations atomically, or
to interact directly with the underlying SQLite database, you must use a
transaction. For example:
lib = Library() with lib.transaction() as tx: items = lib.items(query) lib.add_album(list(items))
A context manager for safe, concurrent access to the database. All SQL commands should be executed through a transaction.
Execute an SQL statement with substitution values and return the row ID of the last affected row.
Execute an SQL statement with substitution values and return a list of rows from the database.
Execute a string containing multiple SQL statements.
The two model entities in beets libraries,
share a base class,
Model, that provides common functionality and
The fields model classes can be accessed using attributes (dots, as in
item.artist) or items (brackets, as in
Model base class provides some methods that resemble dict
An abstract object representing an object in the database. Model objects act like dictionaries (i.e., the allow subscript access like
obj['field']). The same field set is available via attribute access as a shortcut (i.e.,
obj.field). Three kinds of attributes are available:
- Fixed attributes come from a predetermined list of field names. These fields correspond to SQLite table columns and are thus fast to read, write, and query.
- Flexible attributes are free-form and do not need to be listed ahead of time.
- Computed attributes are read-only fields computed by a getter function provided by a plugin.
Access to all three field types is uniform:
obj.fieldworks the same regardless of whether
fieldis fixed, flexible, or computed.
Model objects can optionally be associated with a Library object, in which case they can be loaded and stored from the database. Dirty flags are used to track which fields need to be stored.
Add the object to the library database. This object must be associated with a database; you can provide one via the db parameter or use the currently associated database.
The object’s id and added fields are set along with any current field values.
Mark all fields as clean (i.e., not needing to be stored to the database).
Evaluate a template (a string or a Template object) using the object’s fields. If for_path is true, then no new path separators will be added to the template.
A dict-like view containing formatted values.
Get the value for a given key or default if it does not exist.
Iterate over (key, value) pairs that this object contains. Computed fields are not included.
Get a list of available field names for this object. The computed parameter controls whether computed (plugin-provided) fields are included in the key list.
Refresh the object’s metadata from the library database.
Remove the object’s associated rows from the database.
Save the object’s metadata into the library database.
Assign all values in the given dict.
Returns the current mtime of the file, rounded to the nearest integer.
destination(fragment=False, basedir=None, platform=None, path_formats=None)¶
Returns the path in the library directory designated for the item (i.e., where the file ought to be). fragment makes this method return just the path fragment underneath the root library directory; the path is also returned as Unicode instead of encoded as a bytestring. basedir can override the library’s base directory for the destination.
Creates a new item from the media file at the specified path.
Get the Album object that this item belongs to, if any, or None if the item is a singleton or is not associated with a library.
move(copy=False, basedir=None, with_album=True)¶
Move the item to its designated location within the library directory (provided by destination()). Subdirectories are created as needed. If the operation succeeds, the item’s path field is updated to reflect the new location.
If copy is True, moving the file is copied rather than moved.
basedir overrides the library base directory for the destination.
If the item is in an album, the album is given an opportunity to move its art. (This can be disabled by passing with_album=False.)
The item is stored to the database if it is in the database, so any dirty fields prior to the move() call will be written as a side effect. You probably want to call save() to commit the DB transaction.
Moves or copies the item’s file, updating the path value if the move succeeds. If a file exists at
dest, then it is slightly modified to be unique.
Read the metadata from the associated file.
read_pathis specified, read metadata from that file instead. Updates all the properties in _media_fields from the media file.
Raises a ReadError if the file could not be read.
Removes the item. If delete, then the associated file is removed from disk. If with_album, then the item’s album (if any) is removed if it the item was the last in the album.
Calls write() but catches and logs FileOperationError exceptions.
Returns False an exception was caught and True otherwise.
Set all key/value pairs in the mapping. If mtime is specified, it is not reset (as it might otherwise be).
Write the item’s metadata to a media file.
All fields in _media_fields are written to disk according to the values on this object.
Can raise either a ReadError or a WriteError.
Provides access to information about albums stored in a library. Reflects the library’s “albums” table, including album art.
Returns a path to the destination for the album art image for the album. image is the path of the image that will be moved there (used for its extension).
The path construction uses the existing path of the album’s items, so the album must contain at least one item or item_dir must be provided.
Returns the directory containing the album’s first item, provided that such an item exists.
item_keys= ['added', 'albumartist', 'albumartist_sort', 'albumartist_credit', 'album', 'genre', 'year', 'month', 'day', 'tracktotal', 'disctotal', 'comp', 'mb_albumid', 'mb_albumartistid', 'albumtype', 'label', 'mb_releasegroupid', 'asin', 'catalognum', 'script', 'language', 'country', 'albumstatus', 'media', 'albumdisambig', 'rg_album_gain', 'rg_album_peak', 'original_year', 'original_month', 'original_day']¶
List of keys that are set on an album’s items.
Returns an iterable over the items associated with this album.
Moves (or copies) all items to their destination. Any album art moves along with them. basedir overrides the library base directory for the destination. The album is stored to the database, persisting any modifications to its metadata.
Move or copy any existing album art so that it remains in the same directory as the items.
Removes this album and all its associated items from the library. If delete, then the items’ files are also deleted from disk, along with any album art. The directories containing the album are also removed (recursively) if empty. Set with_items to False to avoid removing the album’s items.
Sets the album’s cover art to the image at the given path. The image is copied (or moved) into place, replacing any existing art.
Update the database with the album information. The album’s tracks are also updated.