Tag write-back
Write Mixar's BPM and key into your audio files so other DJ software shows the same values.
Mixar keeps tempo, key, cues, and grids in its own database. Tag write-back is the one optional exception: it also writes the BPM and key Mixar determined into each audio file’s own tags. Rekordbox, Serato, Traktor, Mixxx, or Mixed In Key then show the same numbers when you load that file there.
It is off by default, and nothing is written to your files until you turn it on.
Turning it on
- Open Settings → Library → File tags.
- Flip the switch in the card header.
- Save the change.
With the switch off, Mixar never opens an audio file for writing, whatever else you do.
Applying it to music you already analyzed
Write-back happens as part of analysis (and when you save a manual beat grid), so the switch only affects tracks analyzed from then on.
To update a library you analyzed earlier:
- Turn the setting on and save.
- Open a collection’s three-dot menu and start analysis with Force re-analysis enabled. Without it, tracks that already have a BPM or key are skipped, and a skipped track is never written.
Forcing re-analysis replaces Mixar’s stored BPM and key with its own analysis result before writing it back. Your files’ existing tags are overwritten too. Forcing is not the only way that can happen today. The confidence-based merge can also prefer the analysis result over a value that is already there, without asking. That is a known problem: analysis must not replace existing BPM/key without explicit consent (#552). Until it is fixed, leave forcing off and leave files whose tags you trust out of the analysis run.
Checking that it worked
- Analyze a track in Mixar with write-back on.
- Open the same file in another player or DJ app.
- Its BPM and key should match what Mixar’s library shows, except for the BPM rounding on MP3, WAV, and AIFF (see One rounding caveat).
If a file shows no values, it is most likely one of the skipped types below. It could also be a track analyzed before you turned the switch on (see applying it to music you already analyzed).
What gets written
| Value | Where it goes |
|---|---|
| BPM | The file’s tempo tag |
| Key | The file’s initial-key tag, in musical notation (Am, F#m) |
| Rating | The file’s star-rating field (1–5) |
| Comment, year, track/disc number, colour label | The matching tag field |
Nothing else is touched. Mixar does not write title, artist, album, or genre. It does not write hot cues, saved loops, or beat grids either: those stay in Mixar’s database. Everything else already in the file (cover art, ReplayGain, other apps’ data) is left exactly as it was.
Which files it can write
| File type | Result |
|---|---|
| MP3, WAV, AIFF, AAC | Everything, in the ID3 tag (the rating goes into each reader’s own POPM frame; see below) |
| FLAC, OGG, Opus | Everything, in the Vorbis comment block |
| M4A / MP4 | Everything, in the iTunes-style metadata atoms |
| APE, WavPack, Musepack | Comment, year, track/disc number and colour; BPM, key and rating are skipped (these formats have no standard field for them) |
Native NI Stem files (.stem.mp4) |
Skipped; see below |
A skipped file is left exactly as it was. Mixar logs the reason instead of guessing.
Why .stem.mp4 files are skipped
They are MP4 files, but not ordinary ones. A Stem container holds four audio tracks plus a stem manifest that lists each layer’s name and color. Traktor and Mixxx read that manifest when they load the file. Rewriting a tag means rewriting the file’s metadata section, which is exactly where that manifest lives. A mistake there loses the layer names (or breaks playback) in the other app. Mixar therefore leaves every Stem file alone and writes nothing into it.
What it does to your files
- Only differences are written. Write-back compares what Mixar stored against what the file already carries, and writes nothing when they match. Analyzing a library whose BPM and key do not change therefore leaves every file untouched. (A re-analysis that concludes a different value is a real difference and is written; see the consent note above.)
- Audio is never re-encoded. Write-back edits metadata only; the sound data is copied through untouched.
- Nothing partial. If a file cannot be written safely, Mixar skips it and leaves it byte-for-byte identical.
- Your database is still the source of truth. Mixar’s table and decks use the values it stored. The file tags are a copy for other software.
Rating on MP3
ID3 keeps star ratings in a POPM frame that is keyed by the app that wrote it. There is no single frame every reader agrees on. Mixar writes one frame per reader it mirrors, namely Traktor, MusicBrainz Picard, MusicBee and Windows Media Player, so they all show the same star count. A rating frame another app owns is re-written on the stepped scale those apps use, so its star count is kept. FLAC, OGG, Opus, M4A and MP4 carry the rating in their formats’ own field.
One rounding caveat
MP3, WAV, and AIFF store BPM as a whole number. If Mixar measured 127.98, the file gets 128. Other apps will show the rounded number while Mixar keeps the precise value, so the two can differ by up to half a BPM. FLAC, OGG, Opus, and M4A keep the exact value.
Turning it off again
Flip the switch off and Mixar stops writing. Tags already written stay in your files: they are normal metadata now. To remove them, clear the BPM and key fields in a tag editor or in whichever DJ app you use.
Related
- Library overview: collections, analysis, and where Mixar keeps its data.
- Internals, per-format detail, and known limits: Tag write-back (developers).