Klaus^™ Live: your mix report now answers back

The gap we were leaving open

A good analysis raises questions. You read that your frequency balance scored 74 and your first thought is not “understood, moving on.” It is “why?”, or “is that actually a problem?”, or “what do I do about it without making the track thinner?”

Until now, those questions went somewhere else. Usually to a general-purpose chatbot that has never heard your track, cannot see a single one of your measurements, and will confidently give you advice that would apply equally to any record ever made. That is the second half of the job, and we were handing it away.

What Klaus^™ Live actually does

Klaus Live is a conversation attached to each analysis. Ask about the overall score, drill into one specific finding, or tap a dimension and ask what is dragging it down. Every answer is built from the numbers measured on your file, alongside the target that number was scored against.

That grounding is the difference between “your low end is a bit heavy” and “sub-bass is sitting at 44% of total energy against a target range of 24 to 40 for this genre, and your mono correlation below 120 Hz is still clean, so this is a balance decision rather than a phase problem.” One is a horoscope. The other is something you can act on tonight.

It knows your other tracks

This is the part we think matters most, and it is the part a tool scoped to a single upload structurally cannot do.

Klaus Live can read your own analysis history. So you can ask whether your low end is genuinely improving across releases, why the version you bounced last month scored higher than today’s, which weakness keeps reappearing no matter what you change, or which of your tracks is closest to release-ready.

Those are questions about you as a producer, not about one file. They get more useful the longer you use TrackScore^™, because the answer is drawn from your own catalogue rather than from general received wisdom about mixing.

It will tell you when we are wrong

Analysis is measurement, and measurement sometimes fails. Beat detection in particular can lock onto the wrong subdivision and report a tempo that is a clean multiple of the real one. Every tool in this category has that problem, including ours.

The difference is what happens next. If a reading does not reconcile with the rest of your track, for instance a tempo far outside the range for the genre you selected, Klaus says the measurement looks unreliable and gives the likely true value. It does not invent a musical explanation for a number that is probably a detection artifact, and it will not tell you to re-produce a finished record to chase one.

We built that rule in deliberately, because the failure mode it prevents is the worst one an analysis tool has. A confident, specific, well-written wrong answer costs a producer real hours and real trust. An admitted uncertainty costs neither.

It will also tell you to leave things alone

A target range is a description of what tends to get released, not a rule you have broken. Sitting slightly outside one is often a choice rather than a defect, and Klaus is allowed to say so. Ask whether something needs fixing and you may well be told that it does not, and which two things are worth your attention instead.

A tool that only ever finds problems is exhausting, and it trains you to stop believing it.

What has not changed

Your audio is still processed in memory and never stored. That has been true since the day we launched and Klaus Live does not alter it: the conversation works from the measurements and the written analysis, never from a retained copy of your file.

There is also no message counter. Klaus Live is included with every analysis, and a conversation about a track you already paid to analyze should not be rationed.

Try it on something you already know

The fastest way to judge it is to run a track you understand well, one whose strengths and problems you could already describe, and then argue with the results. Ask why a score is what it is. Push back on a finding. Ask what to fix first.

Save your track to a free account and the conversation opens on your analysis page.

Frequently asked questions

What is Klaus Live?

Klaus Live is a conversation attached to every TrackScore analysis. After your track is scored, you can ask follow-up questions about any dimension, any individual finding, or any track you have analyzed before. Answers are grounded in the values measured on your own file rather than general mixing advice.

How is this different from asking ChatGPT about my mix?

A general chatbot has never heard your track and has no measurements to work from, so it can only give you advice that would apply to anyone. Klaus Live starts from your file's actual loudness, frequency balance, stereo width, dynamics and arrangement, states the target each was scored against, and answers about your specific numbers.

Can Klaus compare my track to my previous uploads?

Yes, and this is the part most tools cannot do. Klaus Live can read your own analysis history, so you can ask whether your low end is improving across releases, why an earlier version scored higher, or which recurring issue keeps costing you points. A tool scoped to a single upload can only ever answer about that upload.

What happens if a measurement is wrong?

Klaus says so. If a reading does not reconcile with the rest of your track, for example a tempo that falls far outside the range for the genre you selected, Klaus flags the measurement as unreliable and gives the likely correct value instead of building an explanation on top of a bad number. This is deliberate: a confident wrong answer is worse than an admitted uncertainty.

Does Klaus Live cost extra?

No. It is included with every analysis and there is no message counter. Save your track to a free account to open the conversation.

Does TrackScore store my audio to power the chat?

No. Audio is processed in memory and never stored, which has been true since day one and does not change here. Klaus Live works from the measurements and the written analysis, never from a retained copy of your file.

Related reading: how Klaus writes its engineer notes and Bounce Check, for diffing two versions of a mix.