This article explains how to remove or replace Dolby Atmos files within the FUGA Interface, including post-delivery restrictions and DSP-specific behaviors. It also outlines how redelivery impacts the availability of Dolby Atmos content.
Overview and Requirements
Dolby Atmos files can only be replaced or deleted while a release is in Draft status. Once a product has been delivered to Digital Service Providers (DSPs), changes to Dolby Atmos assets require redelivery. Some DSPs do not support automated removal, which may require manual follow-up.
Each Dolby Atmos file must have a unique International Standard Recording Code (ISRC) that differs from its stereo version.
Replacing Dolby Atmos Files (Draft Status)
To replace a Dolby Atmos file in the FUGA Interface:
- Locate the relevant track under the Assets tab of your draft release
- Click the bin icon next to the existing Dolby Atmos file to remove it
- Click Upload Dolby Atmos to add the new file
- Assign a new, unique ISRC to the replacement Dolby Atmos audio
Note: You must complete the replacement process while the release is still in Draft status.
Removing Dolby Atmos Files (Draft and Delivered Releases)
If the release is in Draft:
- You can delete the Dolby Atmos file by clicking the delete icon next to the audio file
If the release has been delivered:
- You must remove the Dolby Atmos file and trigger a redelivery for the change to reflect on supported DSPs
- You can also redeliver previously delivered products to add Dolby Atmos files for the first time. While you must assign a unique ISRC for each Dolby Atmos version, this does not constitute a tracklist change and will not trigger metadata validation errors.
- Navigate to the asset, remove the Dolby Atmos file, and redeliver the release
DSPs That Do Not Support Automated Dolby Atmos Removal
The following DSPs do not support automated removal of Dolby Atmos recordings following a redelivery:
- Amazon Music
- Deezer
- Genie
- TIDAL
If you distribute to these platforms via a direct deal or through Merlin, please contact the DSP directly to request removal.
If you distribute via FUGA Aggregation:
- Reach out to support@fuga.com
- Provide the Universal Product Code (UPC), affected ISRCs, and a list of DSPs where Atmos should be removed
Troubleshooting
- DSP badge removal may not be immediate; confirm the updated asset state post-redelivery
- Assigning the same ISRC as the stereo version will cause ingestion errors. Always use a unique ISRC
Related Notes
- For instructions on how to deliver Dolby Atmos files, see our article on "Delivering Dolby Atmos Audio via the FUGA Interface, API, and XML"
- For DSP-specific visibility guidelines, refer to "Controlling Dolby Atmos Availability and Visibility on DSPs"