AI-generated music often arrives quickly and in many versions. That speed can hide practical problems: unclear filenames, inconsistent trims, clipped exports, mismatched loudness, accidental duplicates, and missing records about where a file came from. Audio preparation creates order before any destructive processing begins.
This guide does not prescribe a universal mastering chain. Genre, destination, source quality, and artistic intent all matter. Use meters and batch tools as evidence, not as substitutes for listening. Keep untouched source files so every decision can be reversed.
Create a non-destructive folder structure
Separate original downloads, selected candidates, edited mixes, masters, and final delivery files. A practical layout might use folders named 01-sources, 02-selects, 03-edits, 04-masters, and 05-publish. Copy files forward rather than overwriting the source.
Add a small project readme with the generation service, dates, prompt or project references, intended release, and any licensing notes. Do not place private keys or account credentials in this file. The purpose is traceability, not sensitive data storage.
Normalize filenames before the session
Use stable numbering and readable titles. Remove temporary suffixes only after you know which version is selected. A filename such as 03-quiet-circuit-source.wav communicates order, title, and state. Keep mix or master revisions explicit when several need to coexist.
Automated cleanup suggestions can save time, but review them. Parentheses may contain a meaningful mix name, and numbers may belong to the title. A preparation tool should propose a mapping rather than rename original files without confirmation.
Inspect duration and boundaries
Listen to the first and last seconds of every selected file. Check for unexpected silence, cut transients, clicks, reverb tails, and inconsistent fade lengths. Duration metadata helps find outliers, but a normal duration does not prove that the boundary sounds clean.
If the album will be joined into one video, decide whether gaps and crossfades belong in the audio editor or video timeline. That decision affects track timestamps. Write it down before generating the final chapter list.
Check format consistency
Record sample rate, bit depth, channel count, and codec. Avoid repeatedly converting between lossy formats. When possible, edit from the highest-quality source provided by the generation or production tool. Convert once for the final delivery requirement rather than at every intermediate step.
A browser may display type and duration but not expose every technical detail reliably. Use a trusted audio editor or inspection utility for final decisions. If a file fails to decode, do not assume it is corrupt; the browser may simply lack codec support.
Separate loudness matching from mastering
Loudness matching makes adjacent tracks feel less surprising, but mastering also considers tone, dynamics, stereo image, distortion, and translation. Two tracks with the same integrated loudness can still feel very different because of bass balance, transient density, or arrangement.
Measure before changing anything. Compare similar sections, not a quiet intro against a dense chorus. Apply conservative gain changes, watch true peaks, and audition level-matched before deciding that processing is an improvement. Avoid chasing a single loudness number without considering the destination.
Listen for artifacts common in generated audio
Check cymbals, sustained vocals, reverb tails, stereo ambience, and low bass for unstable textures or sudden changes. Processing can make artifacts more obvious. Strong limiting may exaggerate brittle high frequencies, while aggressive stereo widening can expose phase problems.
When an artifact is structural, a new generation or edit may be safer than trying to repair it with a heavy chain. Mark the issue in the candidate log so the same problem is not rediscovered later.
Run a deliberate quality-control pass
Listen to the sequence on more than one playback system at a comfortable, matched level. Check headphones for clicks and detail, speakers for balance, and a phone for whether the core elements survive. Do not use dangerously loud monitoring levels.
Export and archive with intent
Choose delivery settings based on the publishing platform and your editing workflow. Keep a lossless master before creating compressed distribution copies. Include version and date in project records, not necessarily in the public display title.
Finally, calculate timestamps from the actual final sequence. Archive the source notes, mastering settings, editor project, meter notes, mastered files, and final tracklist together. A clean archive makes later corrections and remasters far less risky than trying to reconstruct decisions from a downloads folder.