USB errors, files not loading, unsupported formats, and crashes.

Almost no booth problem is a hardware failure at the first diagnosis. When music stops or a file refuses to open, first identify your link in the chain: physical medium, file path, format, or software itself. The five most recurring symptoms—USB absent, File not loading, Unsupported format, Software failure, and Crash—share one method: reproduce the failure, isolate one variable, and change only one thing at a time.

During a gig you have seconds, not minutes, so practise this checking order beforehand. If you have done it twice at home, the third time in the booth will be mechanical. At the end you will find a three-minute routine avoiding most scares, and the next guide for when the issue moves from files to networking.

USB absent: from file system to port

This symptom has two versions worth separating immediately. If the USB does not appear on the computer, the problem is in the system: dead port, damaged cable, driver, or a drive using an unsupported file system. If absent on the player or mixer while the computer sees it correctly, the exported library or medium format is at fault.

Start with the cheapest checks: change USB ports, test the cable on another device, and connect the stick directly without a hub or multiport card. On Windows, open Disk Management to check whether the operating system assigns a drive letter; if not, the drive is incompatible or damaged. On macOS, use Disk Utility. DJ equipment commonly supports FAT16, FAT32, and exFAT, plus HFS and HFS+ on Apple; macOS can only read NTFS, so a library written to NTFS from Windows may behave unexpectedly on other equipment.

If the computer sees it but the player does not, inspect the exported library format. Exports use device-library formats that must match the player’s model and firmware; a library prepared for another generation may show an empty list. The official rekordbox FAQ describes this case: unrecognised memory devices and missing tracks, resolved by updating software and re-exporting the library from the computer.

Files not loading: broken paths and problem files

The file exists, appears in the software list, but nothing happens on loading, or a missing-file marker appears. It is almost always a path: the file moved, was renamed, the drive letter changed, or the library was edited outside the application.

In rekordbox, an externally imported track goes missing if its drive letter changes from the original import; the classic symptom is File is Missing, solved by relinking the library folder or restoring the original drive letter. The same logic applies to manual folder reorganisation: moving and relinking is better than deleting and reanalysing the whole library.

Serato marks questionable files with a yellow triangle in the status column. It warns that a problem file may play incorrectly and destabilise the library, recommending downloading again or re-encoding; files of 2 GB or more are unsupported. Before a gig, find and resolve those triangles: untreated corruption is a failure scheduled for the moment you load the file.

Also check read permissions, read-only mounted drives, and accented or special-character paths changed by a system update.

Unsupported format: what each device supports

The message is literal: unsupported format, or an error code on the player display. It is not a track fault but a mismatch between the file and supported formats.

Serato publishes supported formats: MP3, OGG, ALAC, FLAC, AIF and AIFF, WAV, WL.MP3, MP4, M4A, and AAC, the last only on macOS. Locally downloaded DRM-protected files do not play, and Apple Music lossless tracks arrive in an unsupported .movpkg container; Serato’s solution is lowering download quality and downloading again. Serato also documents a Windows case: .aac shows unsupported file type and clicks, while .m4a and .mp4 work normally.

On players, the error appears as a code. AlphaTheta help identifies E-8304 and E-8305 as unsupported formats, recommending a supported file, and E-8302 as corruption preventing reading, recommending another-device testing and reimporting. Before blaming the stick, convert to a safe format—320 kbps MP3 or WAV—and test again: if the same file works on another device, the issue lies in the file rather than the equipment.

Software failure and crashes: isolate the cause

Separate two often-confused words. Crash: the application suddenly closes. Hang: it freezes and must be forcibly closed. Ableton’s documentation insists on the distinction because diagnosis differs: crashes almost always occur at a reproducible moment—opening a project, loading a plug-in, or connecting a device—and locating that moment is half the work.

Checking order: update software, operating system, and audio-interface drivers; close everything else; update or disable third-party plug-ins (in Ableton, holding the alternate key during startup disables plug-in scanning, testing whether a plug-in is responsible); check whether failure occurs at startup, with one project, with a USB device, or after installing something new. Save crash reports: they are the only reliable clue when failure cannot be reproduced at will.

In the booth, the operational rule is simple: if software crashes twice with the same project, stop using that project for the night and switch to your prepared alternative. Do not spend the set debugging.

Errors that are not your fault

Not every problem is yours. Software-version, library-format, and firmware incompatibilities can be resolved by updates; manufacturers withdraw versions after USB export faults; operating-system and driver incompatibilities may appear only after automatic updates.

Check in this order: what changed yesterday? A system update, DJ software update, new drive, reconfigured antivirus. If recent, roll back that update or apply an already-published subsequent patch. If nothing changed, the problem is the file or medium.

Document your working combination too: software version, player firmware, and operating-system version. A note on your phone is worth more than any forum thread when failure appears two hours before a gig. For library preparation and database errors, rekordbox: USB and database troubleshooting goes into greater detail.

Pre-gig checking routine

Three minutes, always the same, always in the same order. One: connect the USB to computer and player and check it appears on both. Two: load one track in each format you will use—MP3, WAV, or FLAC—on every deck and play five seconds. Three: inspect problem-file markers and free stick space. Four: start the software and check audio-interface detection. Five: close everything else and disconnect unused peripherals.

If something fails in these three minutes, you have time to correct it; if it fails at the start, you improvise. Save this routine in your before-and-after performance checklist and repeat it at every gig until automatic.

Next step

When files load correctly but problems affect players, mixers, and computer together, the source is usually networking. The next guide covers Link drops, frozen decks, and emergency loops.