If you have searched this before, you have probably found three articles that contradict each other.
This covers a DAW the way it actually works in a session: the mechanism, the numbers that matter, and the decisions that follow from them.
Nothing below is theory for its own sake. Every number here is one you can check on a meter, and every step is one you can run on the next track you open.
Key takeaways
- Balance with faders before you reach for a plugin.
- Cut to solve problems, boost to flatter, and know which you are doing.
- Check in mono early and often.
- Leave 3 to 6 dB of headroom for mastering.
Metering that tells you the truth
- A true-peak meter with oversampling. Sample peak lies to you about what happens after encoding.
- An integrated LUFS meter measuring the whole track, not a section.
- A correlation meter to catch phase problems before they reach mono playback.
- A spectrum analyser with a long average, not a fast one. You are judging balance, not transients.
Your ears make the decision. Meters stop you from making a decision that is objectively wrong.
Exporting a master that survives
- Export 24-bit WAV at the session sample rate for distribution.
- Only dither if you are reducing to 16-bit, and put it last.
- Leave the true peak ceiling at -1 dBTP so lossy encoding has room.
- Encode to AAC yourself and listen. That is what your audience gets.
- Keep the unlimited version. You will need it for a remaster, a sync, or a vinyl cut.
How it translates on real systems
Almost nobody hears your record on the system you made it on. The point of every decision above is that it survives the journey.
| System | What it exposes | What to check |
|---|---|---|
| Phone speaker | No low end at all below roughly 500 Hz | Does the bass line still read from its harmonics? |
| Earbuds | Exaggerated width and sub, hyped top | Is anything sibilant or fatiguing? |
| Laptop | Thin midrange-only playback | Is the vocal still intelligible? |
| Car | Boomy low end and road noise | Does the low end turn to mush at 80 to 120 Hz? |
| Club system | Everything below 40 Hz, loud | Is the sub mono and controlled? |
If it works on a phone and in a car, it works almost everywhere else. Those two are the honest tests.
The mistakes that cost the most
These are not exotic. They are the five things that show up again and again in tracks that almost work.
- Judging at a different level each time. Loud always sounds better, so set a monitoring level and leave it.
- Solving a balance problem with a plugin. If the fader cannot fix the relationship, a compressor will only make the wrong balance more consistent.
- Working only on one system. A mix that only holds together on your monitors is not finished, it is calibrated to your room.
- Boosting where you should be cutting. Making something louder to beat a masking problem raises the whole noise floor of the arrangement.
- Never bypassing. If you have not compared against the unprocessed version in the last twenty minutes, you have lost your reference point.
Take a break every forty minutes. Ear fatigue does not announce itself, it just quietly moves your idea of what bright means.
What MaestroNet does with this
MaestroNet analyses the source before it processes anything: spectral balance against a genre reference curve, crest factor, stereo correlation across frequency, transient density, and where the energy actually sits.
The targets move with the style. The chain does not. That matters, because a system that swaps in a different EQ curve regardless of what you sent will fight a mix that was already correct.
- Loudness targeting to the platform standard, measured integrated across the whole track.
- True peak limiting with oversampling, so the AAC encode stays clean.
- Bass management below the crossover, keeping the low end mono and centred.
- Tonal correction referenced to the selected style, applied in broad strokes rather than narrow ones.
What it will not do is decide that the second chorus should feel bigger than the first. That is an interpretive call, and it stays yours.
Frequently asked questions
What is the most important thing to get right with a DAW?
Tonal balance and translation. A track that holds up on a phone, in a car and on monitors is finished. One that only works on your monitors is not.
What loudness should I target?
-14 LUFS integrated with a -1 dBTP ceiling covers almost all streaming. Go quieter for acoustic and classical material, louder only where the genre genuinely demands it.
How much headroom should the mix have?
Three to six decibels, with no limiter on the mix bus. That gives the mastering stage something to work with.
How do I know when it is finished?
When it holds up level-matched against a commercial reference, translates on several systems, keeps its low end in mono, and your changes have stopped improving it.
Hear it on your own track
Upload a mix and get a mastered version back in minutes. Free to try, no card required.
Related tools: AI Mastering · LUFS Meter and Audio Analyzer · True Peak Limiter
Related articles
Logic Pro vs Ableton Live: Which One Should You Use?
Mastering in Ableton Live, step by step: session setup, the chain order that works, the metering to trust, and an expo…
Best DAW for Electronic Music and Edm, Tested and Ranked
Best DAW for electronic music and edm explained step by step, with the settings that matter and the reasons behind the…
How to Master a Song in Ableton Live (Step by Step)
Mastering in Ableton Live, step by step: session setup, the chain order that works, the metering to trust, and an expo…
Best DAW for Hip-Hop and Beat Making, Tested and Ranked
Best DAW for Hip-Hop and beat making: the reasoning behind each move, the frequency ranges to check first, and how to…
