For an album, use an AI music cleaner as a controlled processing stage: choose source versions, test representative songs, review every output and assemble the sequence from approved exports. Keep the original mixes throughout.

Freeze the source versions

Give each song one source file and one track ID. Keep alternate mixes separately so an upload cannot silently switch from the vocal version to the instrumental. Note the sequence, fades and transitions shared by adjacent songs.

Use three folders: originals, processing outputs and approved delivery files. A simple status sheet prevents an experiment from becoming the final master by accident. Include the intended track number and the filename used for each processing attempt.

How batch upload works in the Studio

Active Yearly accounts can select up to five files per upload. Monthly accounts upload one at a time. Legacy Lifetime and Partner access also supports batches. A batch is a convenience for importing songs; it does not combine them into one audio file.

  1. Open the Studio and check your remaining track allowance.
  2. Select or drop up to five complete songs on an eligible plan.
  3. Start the upload and keep the tab open until all selected files have been sent.
  4. Follow each song in the processing queue.
  5. Open each finished track to download its audio and report.

Uploading five files does not promise five simultaneous processing jobs. Processing concurrency is managed by the service. If an upload stops, the Studio keeps the files that were not sent in the selection for retry; check the accepted count before resubmitting.

Each song has its own result. One Human Made prediction does not cover the other tracks in the album. Compare current plans for account access and allowances.

Run a pilot before processing the album

Choose contrasting arrangements. Listen for the properties that matter to your project: vocal tone, kick weight or the air around a quiet instrument. Keep the detector result as a separate column rather than the sole acceptance rule.

Use the same playback chain and comparable listening levels. Our catalogue test log records the listening decision, detection outcome and unavailable analyses. If the first output does not suit the music, investigate that tradeoff before repeating it across the album.

Review transitions and loudness together

A song can work alone yet feel wrong beside its neighbours. Play one ending into the next opening. Check for level jumps, changed fades and tonal differences that distract from the sequence. For a continuous mix, choose source boundaries with those transitions in mind.

Use the audio inspector to investigate loudness and peak differences you hear. Its readings are not a creative target for every song. If you make a further edit or master, associate any subsequent detection report with that new file.

Plan access and final delivery

Count the songs, allow time for exceptions and compare the current Demorphus quotas and billing options. A monthly allowance differs from the number of files accepted in one upload. Keep a final list of the approved filenames and their reports.

Suno Studio documents full-song, selected-range and multitrack WAV exports. Choose the source appropriate to the job: a finished mix and a collection of stems are different tasks. Avoid treating every exported stem as another finished song.

Prepared with AI assistance. Sources below.

Sources and documentation