Overview
What Mixar's library holds, how folders and collections relate, and where the data lives.
The library is Mixar’s catalog of your music. It does not move or copy your files. It records where they are, what they are, and what Mixar has worked out about them (tempo, key, beat grid, waveform).
Collections and sources
A collection is a named list in the library, and it comes in two kinds:
| Kind | What it is |
|---|---|
| Folder | A real directory on disk. Mixar scans it (optionally including subfolders) and lists every supported audio file it finds. |
| Playlist | A list you build yourself: ordered, or a set with no meaningful order. |
A folder collection is a pointer to a directory, not a copy, so your files stay where you keep them. A track can sit in several playlists at once. Collections covers creating one and what its menu does.
Settings → Integrations reads a library from another DJ app and copies its structure into yours. Import from Mixxx brings tracks, playlists, and crates. Import from Rekordbox brings tracks, playlists, hot cues, and loops from a Rekordbox 6/7 install. Both copy lists and track references, not audio files. See Importing music.
What analysis adds
Analyzing a track works offline and fills in:
- BPM and key: used by the library table and the deck’s key display.
- Beat grid: what sync and beat-jump line up to. You can replace it with your own BPM and first beat.
- Waveform: the scrolling display on the deck.
- Loudness: used when volume normalization is on.
Settings → Library → Analysis quality decides how much of each track is examined: Fast, Precise, or Complete. You can analyze a whole collection from the collection’s three-dot menu, or one track from the track list. Analysis covers both routes and what each level decodes.
Hot cues, saved loops, and beat grids live in Mixar’s own database next to the library, not in your audio files. Tag write-back covers the one exception, and what Mixar does and does not write back to a file.
Where the data lives
| Data | Location |
|---|---|
| Tracks, collections, playlists, cues, loops, grids, waveforms | Mixar’s library.db under your app data folder |
| Generated stems and separation models | Mixar’s app data folder: see Stems |
| Your audio files | Wherever you keep them: untouched unless you turn on tag write-back |
Settings → Storage shows how much space the caches use and lets you clear them. Clearing caches never touches your audio files.
Settings that shape the library
| Setting | Effect |
|---|---|
| Analysis quality | How thoroughly each track is analyzed |
| Musical key → display mode / color mode | Whether keys read as Am or 8A, and whether the table color-codes them |
| File tags | Mirror Mixar’s BPM and key into your files: see Tag write-back |
| Stems format | Codec used for generated stem caches: see Stems storage |
| Track row layout | One dense line per track, or two lines with more detail |
| Visible fields | Which metadata chips each comfortable row shows (album, genre, year, track/disc number, comment, ISRC, length) plus the trailing BPM/key/rating/colour, in the order you pick. A chip that cannot fit is left out; the comment is cut to a snippet with an ellipsis. |
In this section
| Topic | Page |
|---|---|
| Find tracks: filter, sort, row actions, dragging to a deck | Browsing |
| Folder collections, playlists, and the collection menu | Collections |
| Queue BPM, key, beat grid, waveform, and loudness analysis | Analysis |
| Bring a Mixxx or Rekordbox library across | Importing music |
| Fix metadata, refresh from file | Editing tracks |
| Write a collection to a USB drive for CDJs | Export to a CDJ USB drive |
| Mirror BPM and key into your audio files | Tag write-back |