Format & parameters
Codec, sample rate, bit depth, bitrate versus what the deck accepts. The single biggest cause of "won't load." DigWash's core — caught per deck family, with a fix.
/// Trust pages · deck errors
The errors
we see coming.
There is no official Pioneer tool that tells you "this track will throw E-8302 on this deck." But most booth errors trace back to a handful of file problems — and a file analyser can catch a large slice of them before you ever plug the stick in. This page is honest about which slice: what DigWash catches today, what sharpens in V1, and what no file tool can predict.
§ The shape of it
A deck error has three halves.
The E-83xx family looks like one wall of cryptic codes. It isn't. It splits cleanly into three kinds of cause — and DigWash sits squarely on the first, is moving into the second, and stays honestly out of the third.
File integrity
The file itself is malformed: header/stream mismatch, non-standard MP3 frames, odd AIFF chunk order, corrupt downloads. Partly surfaced today; the V1 integrity layer closes the gap.
USB & hardware
Edited sticks, wrong filesystem, flaky ports, mainboard faults (E-8307, E-87xx). Out of scope — export discipline and hardware, not file content.
§ The map
Symptom → cause → what DigWash does.
Read left to right: the thing you see in the booth, the code most often behind it, the file problem that causes it, and — plainly — whether DigWash catches it today, sharpens it in V1, or leaves it honestly alone.
| Booth symptom | Code (ref.) | File cause | DigWash |
|---|---|---|---|
| Deck lists the track, then refuses to load it screen: UNSUPPORTED FILE TYPE | E-8305 · E-83xx | A codec the deck doesn't accept (FLAC/ALAC/OGG on an older player), or a supported codec sitting above the deck's bitrate, sample-rate or bit-depth ceiling. | DigWash catches this |
| Loads, then errors partway in — file looks valid but breaks on decode screen: PLAYER ERROR · CANNOT PLAY TRACK | E-8302 | The container and the audio inside it disagree — e.g. an MP3 stream inside a .flac wrapper, or a header that describes something the stream isn't. Strict decoders (CDJ-3000) throw where older decks limp along. | Partly — surfaced today, sharper in V1 |
| Corrupt, truncated, or half-downloaded file won't open screen: PLAYER ERROR | E-8302 · E-8305 | A damaged download, an interrupted copy, or a header so broken the decoder can't even reach the audio. | Partly — surfaced today, sharper in V1 |
| Re-encoded or ancient-encoder MP3 that a strict decoder rejects screen: MP3 DECODER ERROR | E-8304 · E-8302 | A lossy-to-lossy re-encode or a very old encoder can leave frames that don't conform to the MP3 spec. Some decks decode them, the strict ones don't. | Partly — surfaced today, sharper in V1 |
| Odd WAV/AIFF structure — very slow load, or a load failure screen: PLAYER ERROR | E-8302 | Non-standard chunk order (audio written before the header), or a malformed header some editors and converters leave behind. | Coming in V1 |
| Exotic characters in the filename or tags trip the firmware screen: CANNOT PLAY TRACK | E-83xx | Some characters in a filename or tag field are handled unpredictably by certain firmware and surface as a read error. | Coming in V1 |
| USB stick edited by hand after a rekordbox export screen: CANNOT PLAY TRACK | E-8302 | Files moved or deleted inside /CONTENT after export, while rekordbox's table of contents still points at them. | Out of scope |
| USB port or stick not recognised screen: USB / DEVICE ERROR | E-8307 · E-8305 | Wrong filesystem, a corrupted stick, or a flaky USB port. | Out of scope |
| Deck faults at start-up or mid-set, unrelated to any file screen: HARDWARE / FIRMWARE ERROR | E-8307 · E-87xx (e.g. E-8709) | An internal hardware or firmware fault. Nothing in a file causes these. | Out of scope |
- The format/parameter rows are the same engine as the compatibility matrix — five deck families, published ceilings, an honest "can't tell" when the codec is unrecognised.
- A wash never hides a problem it can't fix: DigWash only offers
convertwhen a compatibility copy genuinely makes the file load on a deck family that refused the original. - "Partly" means the signal already exists inside the tool but isn't loud enough yet — V1 promotes it to a first-class problem with a fix, not a buried line.
§ In plain words
What each row means for you.
DigWash catches this
Deck lists the track, then refuses to load it
Every check maps the file against five real deck families and names exactly which won't load it — then offers a wash that produces a copy that will.
Partly — surfaced today, sharper in V1
Loads, then errors partway in — file looks valid but breaks on decode
DigWash already detects the container/codec mismatch and warns on it. V1 promotes it from a buried note to a first-class problem with a one-line fix.
Partly — surfaced today, sharper in V1
Corrupt, truncated, or half-downloaded file won't open
If DigWash can't read a file it flags it today as “unknown.” V1 will call it what it is — a broken file the deck will refuse — instead of a quiet shrug.
Partly — surfaced today, sharper in V1
Re-encoded or ancient-encoder MP3 that a strict decoder rejects
DigWash already spots the acoustic fingerprint of a re-encode (“suspected transcode”). Validating the actual MP3 frame headers is a V1 integrity check.
Coming in V1
Odd WAV/AIFF structure — very slow load, or a load failure
DigWash doesn't scan chunk order yet — that's on the V1 list. But every wash re-writes a clean, conformant AIFF, so running a convert already removes this class of problem.
Coming in V1
Exotic characters in the filename or tags trip the firmware
A filename/tag character-safety check is on the V1 list, run over the whole crate before you export.
Out of scope
USB stick edited by hand after a rekordbox export
Out of scope: DigWash prepares files before export — it doesn't manage the exported stick's table of contents. Rule of thumb: once you export, don't touch the stick by hand.
Out of scope
USB port or stick not recognised
Partly in reach: DigWash models which filesystems each deck family accepts (FAT16 · FAT32 · exFAT · HFS+), so a future crate step can warn before you format. Physical ports and clean ejection stay in your hands.
Out of scope
Deck faults at start-up or mid-set, unrelated to any file
Out of scope, and honestly so: no file analyser can predict a mainboard or firmware fault. This is a Pioneer service matter.
§ The V1 objective
The integrity layer.
DigWash today is strongest on the format half. The V1 goal is to close the integrity half — the malformed-file problems that throw E-8302 / E-8304 / E-8305 on a strict decoder — the same class of check other tools run against a library, but done entirely on your own machine, offline, before you export.
- MP3 frame validation — flag non-standard or corrupt frames that a strict decoder (CDJ-3000) rejects, before the booth does.
- WAV/AIFF header & chunk-order check — catch the odd structure that loads slowly or fails, and point at the wash that re-writes it clean.
- A loud "unreadable file" verdict — a broken or truncated file gets named as broken, not filed under "unknown."
- Filename & tag character safety — surface the exotic characters that trip some firmware, across the whole crate.
This page is the honest baseline. As each V1 check lands, its row above moves from "Coming in V1" to "DigWash catches this" — and this page changes with the tool, not ahead of it.
§ Beta call — turn a booth error into evidence
Saw a code we should map?
If a track threw an error on a real deck, that's the evidence that sharpens this page. Send us four things:
- Deck model — exactly as printed on the unit (e.g. CDJ-3000).
- Firmware version — from the deck's settings/info screen.
- The code & screen — e.g. "E-8302 CANNOT PLAY TRACK," and when it appeared (on load, mid-track).
- The file — its facts from a DigWash check, or the file itself if you can share it.
§ Continue