Skip to content

Reports and Song History

Every AI Mix run tells you what it did, and everything is recorded with the song. There are four places to look, from quickest to most detailed:

  1. The status line at the bottom of the AI Mix screen
  2. The Last run summary at the top of the Detail panel
  3. Each target’s Measurement notes, On the strip now and History
  4. Window › Song History, the running list of every version of the song

The AI Mix is working panel covers the screen while a run works. It shows the phase (Analyzing, Matching, Checking the result), the current target and step, a progress bar of finished targets, the elapsed time and, once one target has finished, an estimate of the time left.

The progress bar counts targets as they finish, including targets that could not be processed. Changes are applied together only when the run finishes.

The panel closes and the status line in the footer summarizes the result in one paragraph: how many targets were matched, which steps ran (Balance, Pan, Space, ducking and so on), what was skipped and why, and any plug-in warnings. Hover the status line to read all of it.

Other endings read like this:

Status line What happened
Canceled; no changes applied You pressed Cancel. Your mix is exactly as it was.
AI Mix stopped on [target]: [reason]. No changes applied. A step failed. Nothing was changed.
Finished; no changes applied. See results. The run finished, but nothing measurably improved, so nothing was changed.
A message that the session changed You edited, played or recorded while the run worked. The result was thrown away.

If you stopped an AI fine-tune with Stop fine-tune, the match and the moves already kept are applied, and the status line says which targets now need measuring again.

At the top of the Detail panel, Last run: N matched, M skipped opens to list each target’s outcome:

Outcome Meaning
Matched Processing was applied and measurably moved the target toward its reference.
Already close No module measurably improved it, so it was left as it was.
With its stack It has no reference of its own and was matched as part of its Summing Stack.
Kept Its match from the last run was kept (see Only new or changed parts).
Levels only Its reference was used for level only.
Muted Muted, so AI Mix left it alone.
Skipped Not processed: powered off, no reference, a missing file, no installed plug-in, and so on. The reason is shown.
Not matched The match was refused, for example because an AI plug-in on it carries your automation.

A run that skipped or refused anything never reads as a full match; the count says so.

Select a target and open the sections at the bottom of its Detail panel:

  • Measurement notes: the measured differences from the reference in words, the engine’s notes, and the last match’s results. Each module shows its measured effect, for example “Kept · Tone gap 3.2 to 1.9 dB” or “Not kept: no measured improvement”.
  • On the strip now: the plug-ins on this target’s strip, by what they do, and who put them there (you or AI Mix).
  • What the AI did: every move the AI fine-tune tried on this target. See Quick re-runs and fine-tunes.
  • History: everything AI Mix and you did to this song, newest first.
  • Section notes: your notes on how each section should feel (read-only here).

Analysis reports are saved with the song, so the comparison is still there when you reopen it. A report measured before your last edit is marked as out of date; Measure or Match measures it again.

The History section lists the song’s events, newest first: analyses, matches, Balance, AI Mix runs, AI frames and fine-tunes, AI moves, your edits, undos and notes. Use the chips to show one kind of event, or All.

AI SUMMARY at the top has one line per role (lead vocal, drums, bass and so on) saying whether you kept the AI’s changes, changed them (and by how much), or undid them.

History is saved with the song and is not affected by Undo. It is information only: reading it changes nothing in your mix.

The How does it sound? field in the footer takes a one-line note about the mix, such as “vocal a bit buried in the chorus”. Press Return or Save note. Notes are saved with the song’s history (also when you save the song) and are read back later.

Window › Song History shows the running list of every version of the open song, newest first: when it was made, by whom, what changed, what was measured, and your verdicts on it.

Song History lives in the song’s folder (for example ~/Music/Wisdom Pro/<Song>/), so it spans every version of the song, not just the open file. If the open file has no song folder, press Start Song History Here to keep a history beside it (save the project first).

  • Search… filters by text.
  • Show: limits the list to All, Versions, Verdicts, Notes or Overrides (song settings, see Song settings and preferences).
  • The person filter shows entries by Anyone or by one author.
  • Benchmarks only shows only benchmark versions.

Select a row to see where the version came from, why it was made, what changed, what was measured and its verdicts. Then:

  • Play Bounce ▶ plays that version’s bounce at matched loudness; A/B with Open Song switches between it and the song you have open; Stop Bounce stops it.
  • Open opens that version (you are asked to save the current one first).
  • Reveal shows the file or bounce in Finder.
  • Add Verdict… records what you thought of a version, in your exact words, where you heard it (for example earbuds or van speakers), and the outcome.
  • Add Note… adds a note. Make This a Verdict turns a note into a verdict.
  • Correct… changes an entry. Entries are never deleted; a correction is added on top.
  • Copy as Text copies the entry. Open Song History.md opens the readable copy of the history in your text editor.

Writing to Song History is not an undo step. Use Correct… to change an entry.

Built so far:1,292 hours24.1 billion tokensabout $8,700 at API pricesupdated Nov 21, 2026 What these numbers mean