DISTROBOLT ARTIST GUIDES
Match perceived loudness across an album
Album loudness consistency is a musical sequencing decision as well as a measurement task. Compare adjacent tracks and intentional contrasts rather than forcing every song to the same integrated value.
Listen in the intended order
Use the approved album sequence and a stable monitoring level. Check the transitions, quiet openings, powerful endings and space between tracks. Record where a jump feels accidental. A sparse acoustic song and a dense full-band recording can need different treatment to preserve the intended experience.
Use measurements as context
Keep relevant loudness and true-peak measurements next to listening notes for each master. Similar integrated numbers do not guarantee identical perceived impact. ITU’s measurement framework helps describe signals, but it does not choose the artistic balance for an album.
Separate mastering from playback normalisation
Spotify describes album-level normalisation that preserves relative gain between tracks in that playback context. That does not repair an unintended balance in the delivered masters or guarantee identical behaviour in every listening mode. Review the source album as well as the actual destination experience where practical.
Approve changes as an album
Ask the mastering engineer to assess the transition and musical purpose before changing levels or processing. Review revised tracks in context and keep the final sequence and file versions together. Do not replace one master without checking neighbouring tracks and any timing dependencies. No automatic album-balancing service or fixed loudness rule is promised here.
Sources and review
Reviewed 4 November 2026. Platform requirements and plan terms can change. Examples are planning aids, not a promise of account access, release acceptance or earnings.
Continue your release planning
- WAV or FLAC for distribution: choose a lossless master
- Check true peaks and clipping before final delivery
- Approve a mastering revision with a clear version record
Ask the DistroBolt team about your release. Send a concise question and release reference; never send account passwords or verification codes.