Troubleshooting Uploads

Most upload failures in Resolut are caught at validation before any data is written, which means the fix is usually straightforward once you understand what the validator is objecting to. This guide walks through the most common categories of upload errors, what causes them, and how to resolve them.

If you're hitting an error not covered here, check the error code against the reference table below or contact support with the full error message and the name of the file you were uploading.

---

File Format Issues

These errors occur when the audio file itself doesn't meet Resolut's technical requirements. They're caught before metadata validation.

Unsupported Container Format

Error message: File format not supported. Accepted formats: WAV, FLAC, AIFF, MP3, AAC.

Resolut accepts WAV, FLAC, AIFF, MP3 (CBR and VBR), and AAC. It does not accept WMA, OGG, OPUS, APE, or proprietary DAW project files (.als, .logic, .ptx).

Fix: Export from your DAW or conversion tool to a supported format. For distribution-quality masters, use WAV (24-bit, 44.1 kHz or higher) or FLAC. MP3 is accepted for reference quality uploads but not recommended as a distribution master.

---

Wrong or Mismatched Codec

Error message: Codec mismatch: file extension indicates [FORMAT] but content is encoded as [CODEC].

This happens when a file has been renamed or re-wrapped without re-encoding — for example, a file saved as .wav that actually contains MP3-compressed audio inside a WAV container, or a .flac file with ALAC audio data.

Fix: Re-export the file properly from the original source, or use a tool like FFmpeg or XLD to verify and convert the actual codec. Don't just rename the file extension.

---

Unsupported Sample Rate

Error message: Sample rate [RATE] Hz is not supported. Accepted rates: 44100, 48000, 88200, 96000, 176400, 192000 Hz.

Resolut supports standard sample rates from 44.1 kHz to 192 kHz. Files at unusual rates (e.g., 22050 Hz from old digital transfers, 32000 Hz from broadcast sources, or 384000 Hz from some high-res workflows) are not accepted.

Fix: Resample using a high-quality SRC algorithm. For distribution masters, 44.1 kHz is standard for streaming; 48 kHz is standard for sync/video delivery. Avoid resampling up (it doesn't improve quality and wastes storage).

---

Bit Depth Out of Range

Error message: Bit depth [BITS]-bit is not supported. Accepted depths: 16, 24, 32 (float).

8-bit audio and 64-bit float are not accepted. This is uncommon but occasionally appears with old digitized recordings or misconfigured export settings.

Fix: Re-export at 16-bit, 24-bit, or 32-bit float depending on your source.

---

File Appears to Be Silent or Corrupted

Error message: Audio validation failed: file appears to be silent or contains no valid audio data.

This occurs when a file uploads successfully but the audio content fails internal validation — either the file is genuinely silent (an accidental blank export), or the file is corrupted and Resolut can't decode it.

Fix: Play the file locally before uploading to confirm it contains audio. If it plays locally but fails validation, try re-exporting it from the source. Corrupted files sometimes result from interrupted exports or disk errors. If the file plays locally but consistently fails in Resolut, contact support with a sample of the file.

---

Metadata Validation Errors

These errors occur after your file is accepted but before the asset is created. They indicate required or formatted data is missing or incorrect.

Missing Required Fields

Error message: Validation failed: the following required fields are missing: [FIELD LIST].

The minimum required fields for a recording asset are: Track Title, Primary Artist, and either ISRC or a confirmed request to auto-assign one. For compositions linked to a recording, Title and at least one Writer are required.

Fix: Review the required field list in the error message and fill them in. If you're doing a bulk upload via CSV, check that your column headers exactly match the template headers — a column named Artist Name won't be recognized if the template expects Primary Artist.

---

ISRC Format Invalid

Error message: ISRC format invalid: expected CC-XXX-YY-NNNNN, received [VALUE].

The ISRC validator checks for the standard 12-character format. Common mistakes:

• Wrong length (11 or 13 characters)
• Hyphens included when the field expects them stripped (or vice versa)
• Lowercase characters (ISRCs are uppercase)
• A UPC/EAN barcode entered in the ISRC field by mistake

Fix: Double-check the ISRC against the format CC-XXX-YY-NNNNN (country code, registrant code, year, 5-digit sequence). Resolut's ISRC field accepts both hyphenated and unhyphenated forms — the validator normalizes them — so don't worry about hyphens, but do verify the character count and case.

---

Ownership Splits Don't Total 100%

Error message: Rights validation failed: [RIGHTS TYPE] ownership shares total [PERCENTAGE]%, not 100%.

Resolut enforces that ownership shares for each rights type (composition, master) must sum to exactly 100% across all listed parties. This error fires when the sum is off — either above or below.

Fix: Review all parties listed in the rights section and ensure their shares add up to exactly 100%. Common causes:

• A co-writer was accidentally entered twice
• A party was removed but their share wasn't redistributed
• Rounding errors from entering percentages with too many decimal places (use up to 4 decimal places maximum)
• Controlled/uncontrolled share fields were confused — only enter your controlled share, not the total

---

Metadata Error Code Reference

Error Code	Field	Meaning	Fix
META-001	ISRC	Format invalid (length, characters, or case)	Correct to CC-XXX-YY-NNNNN format, uppercase
META-002	ISWC	Format invalid (must start with T-, 11 chars total)	Correct to T-NNNNNNNNN-C format
META-003	Ownership splits	Shares don't sum to 100%	Adjust shares until total equals exactly 100%
META-004	Track title	Required field missing or empty	Provide a non-empty track title
META-005	Primary artist	Required field missing or empty	Provide a non-empty primary artist name
META-006	Release date	Date format invalid (must be YYYY-MM-DD)	Use ISO 8601 date format: 2024-03-15
META-007	IPI number	IPI format invalid (must be 11 digits)	Verify the IPI number with the relevant PRO
META-008	Territory codes	One or more territory codes are not valid ISO 3166-1 alpha-2 codes	Use two-letter country codes (e.g., US, GB, DE)
META-009	Genre	Genre value not in accepted list	Use a value from the genre dropdown; custom genres not supported
META-010	Language code	Language code invalid (must be ISO 639-1)	Use two-letter language codes (e.g., en, es, fr)
META-011	ISRC	ISRC is already registered to a different asset in this catalog	Check for accidental duplication; see Conflict Errors below
META-012	UPC/EAN	Barcode checksum validation failed	Verify the UPC/EAN with your barcode issuer; avoid manual entry

---

Conflict Errors

Conflict errors mean Resolut has found a collision between what you're uploading and data that already exists in the system. These require a judgment call, not just a format fix.

Duplicate ISRC

Error message: Conflict: ISRC [VALUE] is already assigned to asset "[ASSET NAME]" in your catalog.

An ISRC can only identify one recording. If you're seeing this error, either:

1. You're trying to upload the same recording twice (a genuine duplicate — delete one)
2. You've reused an ISRC that should have been unique (a mistake — assign a new ISRC to the new recording)
3. The ISRC was assigned by a distributor for a different version and carried over incorrectly (check provenance)

Fix: Review the existing asset named in the error. If it's truly the same recording, don't create a new one — update the existing asset instead. If it's a different recording that was mistakenly given the same ISRC, assign a new ISRC to the incoming recording.

---

ISRC Registered to a Different Organization

Error message: Conflict: ISRC [VALUE] appears in the global registry as belonging to a different registrant. Please verify ownership before proceeding.

This is a softer warning rather than a hard block. It means the ISRC's registrant prefix belongs to a different organization — which could indicate an error, a legitimate transfer you've not documented, or a case where a distributor assigned the ISRC using their own registrant code.

Fix: If you legitimately own this recording and the ISRC was assigned by a previous distributor or label using their registrant code, you can acknowledge the warning and proceed. Resolut will note the discrepancy. If you're not sure, don't proceed — contact your previous distributor to clarify ISRC ownership before uploading.

---

Ownership Dispute Flag

Error message: Conflict: one or more parties listed in the rights profile have filed a competing claim for this work (ISWC: [VALUE]).

This means another organization on Resolut has a conflicting rights registration for the same composition. This can happen with:

• Covers registered without the correct original work ISWC
• Works that were co-written with parties now at different publishers
• Administrative errors in historical registrations

Fix: This conflict requires human review. Open the conflicting claim from the rights section of the asset to see which organization is making the competing claim. If you believe your registration is correct, you can formally dispute it — this creates a resolution workflow that notifies both parties. Do not proceed with distribution if a dispute is open on the composition side.

---

Timeout and Size Issues

File Too Large

Error message: Upload rejected: file size [SIZE] MB exceeds the maximum allowed size of [LIMIT] MB.

File size limits by plan:

• Artist/Independent: 500 MB per file
• Label / Publisher: 1 GB per file
• Distributor / Enterprise: 2 GB per file (configurable)

For reference, a 24-bit/96 kHz stereo WAV file runs about 1 GB per hour of audio, so a standard 4-minute track is around 70 MB. If you're hitting size limits on a normal-length track, check that you haven't accidentally exported a multi-track or surround file.

Fix: If the file legitimately exceeds your plan's limit (e.g., a long-form classical work), contact support to request a temporary limit increase, or contact sales about upgrading your plan. Don't compress the master just to fit the limit — maintain audio quality and find the right path for large files.

---

Connection Timeout During Upload

Error message: Upload timed out. The connection was interrupted before the file finished uploading.

Large files on slow or unstable connections will time out. Resolut's uploader uses resumable uploads for files over 50 MB — if you see a timeout, the upload can often be resumed rather than restarted.

Fix:

1. Check your internet connection stability — uploads over Wi-Fi on congested networks are a common culprit
2. Refresh the upload page — if the upload was resumable, you'll see a "Resume upload" option
3. For very large files, prefer a wired Ethernet connection over Wi-Fi
4. If you're behind a corporate proxy or VPN that terminates long-lived connections, try uploading outside the VPN

If timeouts persist on a reliable connection for files under 200 MB, there may be a network issue on our side — contact support with the file size, your approximate location, and the timestamp of the failure.

---

Storage Quota Exceeded

Error message: Upload rejected: you have used [USED] of your [LIMIT] storage quota. Upgrade your plan or remove assets to free space.

Fix: Review your catalog for draft or duplicate assets that can be deleted. Storage counts against your plan quota are calculated on confirmed assets — draft assets in progress also consume quota. Go to Settings → Billing → Storage to see a breakdown of what's using your quota.

---

CSV Import Errors

Resolut's bulk import tool accepts CSV files using a specific template. These errors occur when the CSV structure or content doesn't match what the importer expects.

Column Headers Don't Match Template

Error message: CSV import failed: unrecognized column headers: [LIST]. Expected headers: [LIST].

The importer uses exact header matching — it's case-sensitive and whitespace-sensitive. A column named Track Title (with a trailing space) or track title (lowercase) will not be recognized.

Fix: Download the current CSV template from the import dialog and use it as your starting point. Don't rename headers, don't add spaces, and don't reorder columns (column order doesn't matter, but headers must match exactly). If you're generating the CSV programmatically, strip leading/trailing whitespace from all header values.

---

Character Encoding Issues

Error message: CSV import failed: file encoding could not be determined, or contains characters outside the expected encoding.

Resolut's CSV importer expects UTF-8 encoding. Files saved as Windows-1252 (common from older Excel installations), Latin-1, or with a BOM marker can cause this error, especially if they contain non-ASCII characters (accented letters, CJK characters, special symbols in artist names).

Fix: Save your CSV as UTF-8. In Excel: File → Save As → CSV UTF-8 (Comma delimited). In Google Sheets: File → Download → CSV (Google Sheets exports UTF-8 by default). In code: ensure you're opening and writing files with explicit encoding='utf-8' parameters.

---

Date Format Errors

Error message: Row [N]: date value "[VALUE]" in column "[COLUMN]" is not a valid date. Expected format: YYYY-MM-DD.

Resolut uses ISO 8601 date format (YYYY-MM-DD) for all date fields. Common wrong formats:

• 03/15/2024 (US format)
• 15/03/2024 (EU format)
• March 15, 2024 (long form)
• 15-Mar-24 (abbreviated)

Fix: Convert all date columns to YYYY-MM-DD format before import. In Excel, format the column as "Custom" with the format code YYYY-MM-DD. In Google Sheets, use the TEXT(date_cell, "YYYY-MM-DD") formula to convert.

---

Row-Level Validation Failures

Error message: CSV import partially failed. [N] rows imported successfully, [M] rows failed. Download the error report for details.

When a CSV has a mix of valid and invalid rows, Resolut imports the valid rows and skips the invalid ones, providing a downloadable error report showing exactly which rows failed and why.

Fix: Download the error report from the import results panel. The report shows the original row number, the failing column, and the specific validation error. Fix those rows in your CSV and re-import — Resolut will skip any ISRCs that already exist from the first import, so you won't get duplicates.

---

Too Many Rows

Error message: CSV import rejected: file contains [N] rows, which exceeds the maximum of [LIMIT] rows per import.

Import limits by plan:

• Artist/Independent: 500 rows per import
• Label / Publisher: 5,000 rows per import
• Distributor / Enterprise: 50,000 rows per import (configurable)

Fix: Split your CSV into smaller batches and import them sequentially. There's no waiting period between imports. If you regularly need to import at scale above your plan limit, contact sales about a Distributor or Enterprise plan.