SERATO
CRASHES OR FREEZES

Serato separate two faults before giving any instruction. A crash is when "The software unexpectedly closes or quits", with a message like "Serato DJ has stopped working", and the audio stops at once. A hang is when "The software freezes or becomes unresponsive" but stays open. For a hang, their advice is to let it crash on its own rather than force-quit, because a forced quit throws away the crash log they need.

Why the log matters more than the minute you lose. A crash that has a log can be reported and fixed, for you and for everyone else with the same setup. A crash with no log is a story. If you can afford to wait, wait.

Their order is five steps: update Serato and make sure the operating system is up to date and supported; disconnect every USB device except keyboard and mouse, restart, relaunch; launch Serato with no controller connected, in internal mode, and load a track that is known to work, which tells you whether the hardware or its driver is the cause; use the Analyze Files button to find corrupt tracks, which show "a white triangle with an exclamation point in the center", and remove or re-encode them; and create a fresh user account on macOS or Windows and test Serato from there.

The third step is the one to do first if you only do one. Internal mode, no controller, a track that has always worked. If Serato is stable like that, the fault is in the hardware or its driver and you have halved the search in a minute. If it still crashes, it is the software, the files or the computer, and the hardware is cleared.

Analyze Files is not only for beat grids. It is how Serato find a track that will crash the player when it is loaded, and it marks the track with a white triangle and an exclamation point. One bad file in a library of thousands is enough, and it will be the one you load at the worst moment.

Remove the marked tracks or re-encode them from the original, then analyse again. This is a table job, before the gig, and it is the one on this page that prevents the next crash rather than explaining the last one.

Two more from the same guide: if the crashes began after an update, revert to the earlier version; and check the hardware maker's own driver and firmware updates for a fault that is specific to one unit. Serato also ask you to contact their support before troubleshooting, because a crash that is a bug affects other people too.

Reverting is a legitimate move, not an admission. Keep the installer for the version that worked, and do not update Serato, the operating system or a driver in the days before a gig you cannot afford to lose. That rule is on the pre-gig checklist for a reason.

At the decks, the only fast move is a relaunch, and if it crashed while loading a particular track, do not load that track again. Nothing else on this page is a booth job.

If it crashes twice, take the laptop out of the set. Any drive you have already exported plays in the club's players with no computer involved, which is the reason this site asks you to carry one. Run the five steps tomorrow.