Replacing an audio file after delivery

Once a release is delivered to a DSP, the DSP will NOT allow you to change the audio file unless BOTH of the following are true:

1. You are replacing the file because of a technical issue (crackle, silence, etc.)
2. AND the duration of the new audio file is very close to the duration of the old file. Different DSPs have different criteria for this, but a good rule of thumb is that if the new file is more than 2 seconds different in duration, your update may be rejected by the DSP. If your audio is more than 2 seconds different and you do not have time to wait and see whether the DSP(s) will accept your update, you are better off using Solution #2 below.

Solution 1: Your audio replacement meets the above requirements

You can replace your audio following these steps:

1. Go to Catalog and click on the release that contains the track you want to update.
2. In the release's left-hand menu, click Tracks.
3. Find the track whose audio you want to replace. Click the three-dot menu (⋮) on the track row and select Edit.
4. In the track editor, you'll see the Add Audio File section (step 1 of 3). If an audio file is already uploaded, you'll see an audio player with the waveform.
5. Click the Replace button at the top-right corner of the audio player to upload your new audio file.
6. Once your file has finished uploading, click Update to save your changes.
7. Redistribute your release to the DSP(s).

Solution 2: Your audio replacement does NOT meet the above requirements

If you need to change the audio file because you uploaded the wrong audio from another track, or if your new audio file is more than 2 seconds different in duration, then you will need to do the following:

1. Create a new release with the new audio file.
2. You should reuse the same ISRC if that is indeed the correct ISRC for the track.
3. However, you should NOT use the same UPC as your previous release.
4. Once your new release is created, deliver it to the DSP(s).
5. Wait 48 hours (or for Apple Music, wait 6 days), and then take down your old release. The reason to wait is to ensure that the new release has time to link to the old one so it can replace it in listeners' favorites, playlists, etc. If you need to remove the old release faster, you can — but if the new release doesn't rack-link with the old one, you can always open a support ticket afterward.

Related articles

• Changes you can and cannot make once your release is distributed
• Delivering Dolby Atmos Music: A complete guide for Revelator Pro users
• Delivering HD Audio
• How to edit the release date after distribution