Find the problem before a reviewer does
Preflight QC checks metadata, audio, artwork and licensing the moment a release is submitted. The report is written for the person who has to fix it: what is wrong, where it is and what to change.
- Checks
- Metadata, audio, artwork, licensing
- Timing
- On submit, before human review
- Report
- Each issue with its fix
A report you can act on
A rejection code tells you something failed. Preflight tells you what to do about it. Each check passes, warns or fails, and anything short of a pass arrives with the reading, the requirement and the fix.
- Runs as soon as the release is submitted
- Warnings and failures come with the fix
- Fix and resubmit, and only what changed is checked again
Preflight check: Low Tide
Sample datalow-tide-master.wav3:41
0 of 6 checksOnly problems
- Artwork sizeQueued
- Sample rateQueued
- ClippingQueued
- Silence at startQueued
- LoudnessQueued
- Title capitalisationQueued
Scanning
Artwork, audio and metadata
What each check covers
Four groups of checks run on every release you submit.
- Metadata
- Titles, versions, artist roles, genres and explicit flags
- Audio
- Format, sample rate, bit depth, silence, clipping and duration
- Artwork
- Dimensions, aspect ratio, blur, and the text on the cover against the metadata
- Licensing
- Cover declarations, sample clearances and public-domain claims
Run it where the work happens
- Run it from the API
- Call Preflight from Engine and get the same report as JSON, so your own product can show it.
- Custom rules
- A white-label platform can add rules of its own, such as a house style for titles or a stricter artwork size.
- Severity levels
- Decide which findings block a submission and which only warn. A blocker stops the release. A warning travels with it.
- Batch checks
- Run Preflight across a catalog you already hold and get one list of what to fix.
Questions about Preflight QC
No. It catches what a machine can measure. A reviewer still reads the release for what a machine gets wrong, such as store style, name collisions and rights.
Yes. Batch checks run across releases you already hold and return one report.
They happen. A warning can be overridden with a note that explains why, and the note goes to the reviewer with the release.