How to Update Audio Files in the FUGA Interface

Introduction

This article explains how to update audio files for an existing product in the FUGA Interface. Users can replace individual audio assets and redeliver the product to Digital Service Providers (DSPs), ensuring the latest version is available to consumers.

Overview

Updating audio in the FUGA Interface involves replacing an existing audio file at the asset level and reinitiating delivery to selected DSPs. This is commonly done when improving file quality, correcting errors, or addressing compliance issues.

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

Requirements

• Access to the product and its audio assets in the FUGA Interface
• Updated audio file in a supported format (e.g., WAV, FLAC)
• Appropriate rights and metadata to maintain International Standard Recording Code (ISRC) consistency, unless a new ISRC is required
• Product must not be finalized (or should be reopened if previously finalized)

Instructions

1. Navigate to the relevant product in the FUGA Interface.
2. Go to the Assets tab.
3. Locate the track you wish to update.
4. Click on Unlock & Edit
5. Select the existing audio file and choose Replace All Files.

1. Upload the new audio file.
2. Review and confirm metadata consistency:
   • If audio content remains the same, retain the existing ISRC.
   • If the audio content changes significantly (e.g., new mix or version), assign a new ISRC.
3. Save the changes.
4. Reinitiate delivery:
   • Go to the Deliveries tab.
   • Select the relevant DSPs.
   • Click Redeliver.

Important Notes

• Replacing an audio file will not automatically trigger redelivery. Manual redelivery is required for the updated asset to reach DSPs.
• If the product is already released and audio differs substantially, it is best practice to create a new product entirely.
• Ensure that new audio meets DSP technical specifications and FUGA's quality control requirements.

Troubleshooting

• Updated audio not appearing on DSPs: Check if redelivery was completed successfully. If not, reinitiate the delivery.
• File format not accepted: Confirm that the audio file adheres to supported formats (e.g., WAV or FLAC, 16–24-bit, 44.1 kHz).

Best Practices

• Update audio assets well before the consumer release date to avoid last-minute issues.
• Always verify metadata and file content before initiating redelivery.

• Keep a record of changes and delivery attempts for audit and support purposes.

   

Contact Support

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