Install Mixar
Install and launch Mixar, get sound, and load a first track, plus source builds and where the app keeps your data.
Mixar is a desktop DJ app built on a Rust audio engine. It gives you two or four decks, a mixer, an offline-analyzed library, stems, and a performance pad grid. It runs on Linux, macOS, and Windows. Linux is the primary development platform.
The app is under active development and is not a stable product yet, so settings can change between versions.
This page takes you from nothing to a track playing on a deck. Each step ends with something you can see on screen, and where a step can fail, it names the fix.
Before you start
- A supported computer: Linux, macOS, or Windows.
- A working sound device: the mixer runs inside the audio engine, so a working output device is what makes sound. Without one the app still opens, but it stays silent.
- A build: a download from GitHub Releases. Downloading is the supported path for users.
1. Get a build
Prebuilt packages are attached to GitHub Releases:
| Platform | Asset |
|---|---|
| Linux | .AppImage, marked executable and run directly |
| macOS | .dmg |
| Windows | .exe setup |
The latest public build is a pre-release. Artefacts ship unsigned by default. On macOS you have to allow the app in System Settings after the first launch attempt, because notarization is not wired yet. On Windows you will see a SmartScreen warning. There is no auto-updater; getting a new version means downloading it again.
To build Mixar yourself, follow the Quick start in the repository README: github.com/geovannimp/mixar#quick-start. It lists the toolchain, the Linux headers, and the commands, and the first-launch checkpoint in step 2 applies unchanged to a source build.
2. Install and open it
- Linux: mark the
.AppImageexecutable and run it directly. - macOS: open the
.dmgand launch the app. Allow it in System Settings after the first launch attempt; notarization is not wired yet. - Windows: run the
.exesetup. The first run shows a SmartScreen warning.
Checkpoint: a fresh install opens setup instead of the mixer. Finishing or skipping it opens the mixer, with two empty decks and an empty library, and the engine already started on your system default output device.
First launch
Setup is six full-window steps, or seven when Mixar detects a supported, mapped controller. They point Mixar at your music and set the app up the way you like it. Each step is its own stage: headline on the left, the choice on the right, and a numbered track beside the headline showing where you are.
| Step | What it asks for |
|---|---|
| Welcome | Nothing: what the app is and what the steps cover |
| Language | The interface language, switched live as you pick |
| Appearance | Theme and accent color, previewed live as you pick |
| Controllers | Only shown when Mixar detects a supported, mapped MIDI controller: trust it to connect on its own |
| Library | A folder of tracks, plus an import row for any Mixxx or Rekordbox library found on this machine |
| Privacy | Whether Mixar may send anonymous usage data, off by default |
| Ready | Three tips, then into the mixer |
Start mixing saves the settings draft and opens the mixer. Skip setup marks the flow as done while keeping what is already saved. It discards draft edits such as language, theme, accent, controller trust, and privacy, but a folder you added or a library you imported in the Library step has already happened and stays. Nothing is destructive either way, because every option is in Settings afterwards.
Audio is not part of setup: the engine starts on your system default output when the mixer opens. Change the device in Audio settings.
The appearance step is a real preview: picking a theme, accent color, or language repaints the window immediately, so you see the app before finishing. Enter moves forward and ← steps back; the mouse is optional.
Setup reduces to a single column when the window is narrow, and the background animation stops if your system asks for reduced motion.
To see the steps again, use Settings → UI → First-run setup → Show setup again and Save.
The mixer itself opens on two empty decks and an empty library:
| Surface | What it says when empty |
|---|---|
| Deck track info | No track loaded / Drop a track or click the cover |
| Collections sidebar | No collections yet. Create a folder or playlist collection. |
| Track list, Drive tab | Select a drive or folder to browse audio files |
| Track list, folder open | No tracks |
Deck layout, jog behaviour, tempo range, and every other default are described in Settings. The two settings worth visiting before you play are Settings → Audio and Settings → Library → Analysis quality.
If the app shows an audio failure
With no usable device the engine fails with No output device available. The app keeps running without audio and shows an Audio engine failed to start notice. Plug in or enable an output, then save settings in the Audio section (or relaunch) to bring audio back. See Troubleshooting sound.
3. Load a track
Drag an audio file from your desktop onto a deck. You can also click the cover, which opens the library.
Checkpoint: the deck’s track info fills in, and No track loaded with Drop a track or click the cover disappears. Play starts the track.
Recovery: with no collection selected, the Collections tab’s track list reads Select a collection. Add a folder as described in Library, then drop a track onto the deck.
Where your data lives
Everything Mixar owns sits in one application-support directory: top.mixar.app on Linux and macOS, Mixar on Windows.
| Platform | Directory |
|---|---|
| Linux | $XDG_DATA_HOME/top.mixar.app, or ~/.local/share/top.mixar.app |
| macOS | ~/Library/Application Support/top.mixar.app |
| Windows | %APPDATA%\Mixar |
| File | What it holds |
|---|---|
library.db |
Tracks, collections, playlists, hot cues, loops, beat grids, waveform overviews |
settings.json |
Every preference, including controller trust and the chosen audio devices |
mixar.log |
Rust diagnostics, written from launch |
mappings/ |
Controller mapping bundles |
stems/, models/ |
Generated stem caches and the downloaded separation models |
Audio files are never moved or copied. A folder collection is a pointer to a directory you own. Backing up that folder backs up your whole Mixar setup; deleting it resets the app without touching your music.
Where to go next
| Task | Page |
|---|---|
| Get sound out, route the headphones | Audio setup |
| Fix silence, one side, or dropouts | Troubleshooting sound |
| Add a folder of music and analyze it | Library |
| Load a track and play it | Decks |