Skip to main content

How to Update Audio Files in the FUGA Interface

  • Updated

This article explains how to update audio files for an existing product in the FUGA Interface. You will learn how to replace audio assets at the track level, manage International Standard Recording Code (ISRC) requirements, and reinitiate delivery to Digital Service Providers (DSPs) to ensure the latest audio assets are live for consumers.

Overview

Updating audio in the FUGA Interface involves replacing an existing audio file at the asset level and reinitiating delivery to selected Digital Service Providers (DSPs). This is commonly done to improve file quality, correct audio errors, or address compliance requirements.

FUGA automatically manages format compatibility during delivery. For instance, a 24-bit audio file will be delivered as-is to DSPs that support high-resolution audio, and automatically downconverted to 16-bit for DSPs that do not.

Requirements

  • Updated audio file in a supported format (e.g., WAV or FLAC, 16–24-bit, 44.1 kHz or higher).
  • Appropriate rights and metadata to maintain International Standard Recording Code (ISRC) consistency, unless significant audio changes require a new ISRC.
  • Product must be reopened if it was previously finalized.

Instructions

  1. Navigate to the relevant product in the FUGA Interface.
  2. Scroll to the Tracklist section and click on the title of the track you wish to update (e.g., "Track Title (feat. Artist Name)").
  3. Click UNLOCK & EDIT.
  4. Select the existing audio file and click REPLACE ALL FILES.
  5. Upload the new audio file.
  6. Review and confirm metadata consistency:
    • If the audio content remains essentially the same (e.g., fixing a minor audio glitch), retain the existing ISRC.
    • If the audio content changes significantly (e.g., a new mix, edit, or version), assign a new ISRC.
  7. Save your changes.
  8. Reinitiate delivery:
    • Go to the Deliveries tab.
    • Select the target DSPs.
    • Click Redeliver.

Important Notes

  • Replacing an audio file does not automatically trigger redelivery to DSPs. Manual redelivery must be executed for updated assets to reach DSPs.
  • If a product is already live and the audio differs substantially, creating a new product listing may be required per DSP policies.
  • Always ensure that new audio files meet technical delivery requirements and quality control standards.

Troubleshooting

  • Updated audio not appearing on DSPs: Check the delivery status in the Deliveries tab to verify if the redelivery completed successfully. If failed or pending, reinitiate the redelivery.
  • File format rejected during upload: Confirm that your file is an uncompressed WAV or FLAC file, with a sample rate of 44.1 kHz or higher, and 16-bit or 24-bit depth.

Best Practices

  • Initiate audio asset updates well ahead of planned promotional dates to allow DSPs adequate processing time.
  • Always double-check track audio and metadata before confirming redelivery.
  • Keep records of changes and redelivery timestamps for audit and tracking purposes.

If you experience ongoing issues updating audio assets, contact your FUGA representative or reach out via our support channel at support@fuga.com.

Related articles