pyrekordbox Documentation

Pyrekordbox is a Python package designed to interact with the library and export data from Pioneer Rekordbox DJ Software. It allows developers to programmatically access and manipulate various Rekordbox data formats.

Supported Data Formats:

• Rekordbox master.db database
• Rekordbox XML database
• Analysis files (ANLZ)
• My-Setting files
• Device library plus

Tested Rekordbox Versions:

• 5.8.6
• 6.7.7
• 7.0.9

WARNING

This project is not affiliated with Pioneer Corp. or its related companies. Use at your own risk; maintainers are not liable for damages to your Rekordbox library.

Rekordbox analysis files use the .DAT, .EXT, and .2EX extensions. The format is structured as a file header followed by a series of tagged sections. Each section is identified by a unique four-character code, followed by its own header and content.

File Header Structure

• Format Identifier: The file begins with the four-character code PMAI.
• len_header (Bytes 04-07): A four-byte value specifying the length of the file header in bytes (typically 1c bytes).
• len_file (Bytes 08-0b): A four-byte value specifying the total length of the entire file in bytes.

Rekordbox My-Setting files (DEVSETTING.DAT, DJMMYSETTING.DAT, MYSETTING.DAT, MYSETTING2.DAT) use little-endian data types and consist of a header, a data body, and a footer.

Header Structure (104 bytes total)

• len_strings (1 byte): Combined size of string fields (typically 96).
• Padding (3 bytes): Always zero.
• brand (32 bytes): ASCII string identifying the brand.
• software (32 bytes): ASCII string (always "rekordbox").
• version (32 bytes): ASCII string describing the version.
• len_data (4 bytes): Size of the data field in bytes.

Footer Structure (4 bytes)

• Checksum (2 bytes): Calculated over the data field. Note: For DJMMYSETTING.DAT, the checksum is calculated over all preceding bytes (including length fields) using the CRC16 XMODEM algorithm.
• Unknown (2 bytes): Always 0x00.

Rekordbox 6 transitioned from a DeviceSQL database (.edb) to an SQLite3 database. This database is encrypted using SQLCipher4.

Because the database is encrypted, it cannot be accessed or parsed without the encryption key. The key is believed to be universal across all databases and is not dependent on specific licenses or machines.

Rekordbox stores track analysis information in specific files (e.g., ANLZ0000) with extensions like .DAT, .EXT, or .2EX. These files contain critical DJ metadata, including:

• Waveforms
• Beat grids (precise beat timing)
• Time indices (for efficient seeking in variable bit-rate streams)
• Memory cues and loop points

Rekordbox analysis files (.DAT, .EXT, .2EX) are composed of multiple tagged sections. Each section follows a consistent "envelope" structure that allows for easy navigation through the file even if the internal content of a specific tag is unknown.

Every section begins with:

1. fourcc: A four-character code identifying the specific structure and content.
2. len_header: A four-byte value specifying the size of the section header.
3. len_tag: A four-byte value specifying the total length of the entire tagged section (including the header).

To find the start of the next tag, add len_tag to the current tag's starting address.

In the Rekordbox 6 database, playlist-like objects (such as Playlists and Histories) follow a dual-table pattern:

1. Metadata Table (djmd<NAME>): Contains information about the playlist or playlist folder itself (e.g., djmdPlaylist). Each entry has a unique ID.
2. Membership Table (djmdSong<NAME>): Contains the actual tracks within those playlists (e.g., djmdSongPlaylist).

To reconstruct a playlist, you must link the membership table to the metadata table using the <NAME>ID column, and then link the track to the main collection using the ContentID column which points to the djmdContent table.

Many tables in the Rekordbox database are linked via foreign keys. The ORM provides relationship attributes to access these linked objects directly. For example, a DjmdContent instance has an Artist attribute that links to the corresponding DjmdArtist entry.

content = db.get_content(ID=0)
artist = content.Artist

The Device Library Plus is a library format exported to USB storage or SD cards for newer generation Pioneer DJ devices. As of 2025, this format is supported by the following devices:

• OPUS-QUAD
• OMNIS-DUO
• XDJ-AZ

Technically, the format is a SQLite database encrypted using the SQLCipher library. The encryption key is not license or machine dependent; all Device Libraries use the same key. The database schema is a subset of the main Rekordbox database (master.db), containing similar tables, columns, and data types.

Rekordbox separates the definition of a playlist/folder from the actual tracks contained within it.

• djmdPlaylist: Stores the metadata for playlists, folders, and smart playlists.
  • Attribute 0: playlist, 1: folder, 4: smart playlist.
• djmdSongPlaylist: A junction table that links tracks (ContentID) to playlists (PlaylistID).
• djmdHistory: Stores history playlist metadata (folders or playlists).
• djmdSongHistory: Links tracks (ContentID) to history entries (HistoryID).
• djmdRelatedTracks: Stores related track lists. Uses djmdSongRelatedTracks to link tracks.
• djmdSampler: Stores sampler lists. Uses djmdSongSampler to link samples.

You can install the pyrekordbox package using pip.

$ pip install pyrekordbox