Here you'll find the most common situations you may run into and what to do about them. Most of the time it's not an error – the app is just preparing something in the background. For each problem there's a symptom (what you see), a cause (why it happens), and a fix (what to do).
The first track plays with a delay (~5 s), then it's fine
Cause: After a fresh load, the app first restores the index of your music files from the browser's memory. The first playback therefore waits a moment; once the index is ready, everything plays instantly.
Fix: Nothing to do – it's normal behavior. Wait those few seconds, it's only once at the start of the session. If you want tracks available right away, give the app a moment after loading the library before you click play.
Cover art (track covers) doesn't show up
Cause: The app takes covers from two places – from the index and from the image "baked" right into the track (embedded cover). When a particular track has no embedded cover, there's nothing to show.
Fix: For tracks without an embedded cover, the cover simply won't appear – the app doesn't download any from the internet (everything runs locally). If covers matter to you, add them to the files in your tag editor (e.g. Mp3tag) and reload the library. For the other tracks, covers appear automatically once indexing finishes.
Chrome on a tablet "isn't responding" (on startup or during indexing)
Cause: During a demanding operation (startup, building the index) the browser on a tablet may freeze for a moment and the system shows a message that the app isn't responding (an ANR). It's not a crash – the app is just working intensively and a slower tablet can't keep up with rendering it.
Fix: Click Wait and give it a few seconds – the operation will finish on its own. Don't close the app or the browser. For peace of mind: run the demanding first indexing when you don't need the tablet (overnight is fine).
After clearing the cache, the app loads the processor and rebuilds everything
Cause: There are two different things to clear in the browser. When you clear site data, the saved music index gets cleared too – and it has to be rebuilt from scratch, which loads the processor.
Fix: Clear only "Cached images and files". Don't clear "Site data / App data" for the domain open.djanalyzer.com – otherwise you lose the index and the app will have to rebuild it. If it has already happened, just let indexing finish in peace (once) and it will be fast again afterward.
Black screen or "the app crashed"
Cause: An isolated rendering freeze – typically after a long operation or switching between apps on a tablet.
Fix: Reload the app (hard refresh) – on desktop Ctrl+Shift+R, on a tablet pull the page down or close and open the app window. The index and database aren't lost in the process. The app also has automatic recovery, so it often fixes itself.
Indexing takes a very long time
Cause: A large library (even tens of thousands of tracks) on slow storage – typically a tablet – takes a long time to go through. The first complete indexing can thus take hours on a tablet.
Fix: Build the index once and let it finish – ideally overnight, when you don't need the device. The index gets saved (persisted), so the next startup is fast (about 5 s to restore). You can pause indexing anytime in Settings and resume it later. For tracks added later, don't rebuild everything – use reindexing ("Find new"), which is much faster. You can have an e-mail sent to you once indexing finishes.
In the Free version the tablet sends me to the pricing page
Cause: The touch modes Tablet/Phone (large elements, fullscreen player, bottom navigation) are features of the Pro plan. In the Free version the app runs on every device, but in desktop layout – and on a real tablet it therefore refers you to the pricing page for touch mode.
Fix: It's not an error – Free works fully on desktop (computer, laptop). If you want comfortable control and a fullscreen player right on a tablet/phone (e.g. at a ceremony), the Pro plan is needed. On desktop you have the full value of the app in Free with no limits.
Database health reports that it can't see m.db
Cause: The Database health and maintenance analysis runs right in the browser over your connected Engine library (via file access). When the library isn't connected, the tool has no database to access.
Fix: First connect your Engine library – in Settings (or on the Dashboard) select the root folder that contains the Database2 subfolder with m.db. After connecting, run the analysis again. This feature makes sense on desktop, where the app can read the selected folder.
The full m.db won't load on a tablet (it freezes or crashes)
Cause: The full m.db can easily be ~2 GB (it also contains covers and beat-grid data). A tablet has limited browser memory, so such a large file won't load into it.
Fix: Use a slim database – a lightweight copy with metadata only (artist, title, BPM, key, genre, cue points), reducing ~2 GB to ~5–25 MB. On desktop go to Settings → Export slim (creating a slim is Pro), the file gets saved into Database2 and downloaded at the same time. Then transfer it to the tablet (into Engine Library/Database2) or load it directly. Loading a finished slim is Free.
Newly added tracks aren't visible in the app
Cause: The index and the database show the state from when they were last loaded. Tracks added to Engine DJ after that the app doesn't "know" yet.
Fix: Run reindexing – in Settings → "Find new". It adds only the newly arrived tracks, so it's much faster than building the whole index again. If they're also missing from the lists and playlists, reload the Engine database too (the connected library) so the latest changes show up.
I forgot my licence key
Cause: The licence key is generated after registration and e-mail confirmation (even for the Free plan) and is entered in the app under Settings / Profile. Without it the app won't start.
Fix: You'll find the key in your account (the My account / Profile section on djanalyzer.com) and in the confirmation e-mail from registration. Copy it and paste it in the app under Settings → Profile. Once a licence is verified, it holds offline too, so you don't have to enter it every time. If you can't find the key anywhere, get in touch with support.