GOT QUESTIONS?

OCDJ keeps your whole DJ library clean, complete, and organized — so you stop fixing tracks and get back to playing them. It reads your Rekordbox or Traktor library directly: broken tags repaired, missing artwork, genres and years filled in, duplicates cleared, everything filed for fast browsing. Set it up once and it keeps going on its own — new tracks handled automatically, your library backed up, every change undoable. You run it all just by asking DEBUSSY in plain language. A companion to your DJ software, never a replacement.

If you DJ and you care about your collection, this is for you — club nights, bedroom sets, anything in between. The common thread is a library that's grown over years of digging and now takes real work to keep in shape: broken tags, missing artwork, messy genres, a folder structure held together by hope. You don't need to be technical — you just need to care about your music. OCDJ handles the rest.

OCDJ works with Rekordbox and Traktor Pro today. It reads your native library directly, so there's no export, import, or conversion dance — point it at the library you already use and it picks up everything as-is. On a different platform? Send us a message and we'll log your interest — we're growing the list, and Serato support is on the radar, though not on a committed timeline yet.

Your collection is the product of years of digging — and keeping it in order has quietly become a second job: broken tags, missing artwork, messy genres, duplicates, a folder structure that drifts. OCDJ takes that off your plate for good. Tell it once how you want your music organized, and from then on every new track is cleaned, enriched, and filed for you — automatically, while you're doing something else. What's left is the part that matters: playing your music.

I'm DEBUSSY — a crate-digging friend who actually knows your collection. No menus, no digging: just ask in plain language. "How many 5-star techno tracks have no genre?" "Where are my duplicates hiding?" You get a real answer in seconds. With a subscription I do the work too — build a playlist from a plain sentence, fix tags across your whole library in one go, reorganize, surface the gems you forgot — including playlists with rules your DJ software can't express. Every change shows a preview first, and anything I do, you can undo.

Sorting out your library by hand is a one-time fix that falls apart the moment the next track lands. OCDJ makes it stick: set your preferences once, and every new track is cleaned, enriched and filed automatically in the background. It also handles what's brutal by hand across thousands of tracks — missing artwork, years, genres and labels, tricky artist casing (deadmau5, MK, DJ EZ), hidden duplicates — and snapshots your whole library before every run, so nothing is ever a one-way door. The goal isn't to clean your library once. It's to keep it from ever getting messy again.

Most DJ utilities do one trick — analyze keys, rename files — and hand it back with one box ticked. OCDJ does the whole job and keeps doing it: it fixes and enriches every track, backs your library up to the cloud, and lets you undo or restore anything. Set it once and new tracks are handled automatically. It also does things other tools can't — fixing "zombie" links that leave tracks showing blank, and getting tricky artist casing right by learning from a catalog instead of a rule. And you run all of it just by asking DEBUSSY, including custom organizing your DJ software can't express, like "everything that's NOT House." A companion, never a replacement: already keyed your library with Mixed In Key? OCDJ leaves your MIK key and energy alone and fixes everything MIK doesn't — broken tags, missing artwork and years, duplicates, zombie links — automatically, for every new track.

You can try things without worrying — by design. OCDJ takes a full snapshot before it changes anything, so if you don't love a result, one click puts everything back. It never edits your original library file — it works on a copy, checks it, and only swaps it in once the checks pass. A scan shows you what it would fix, by category, before anything runs — there's no per-change approval step, but everything is snapshotted first so it's reversible. The app is code-signed and notarized by Apple, and your music never leaves your computer unless you turn on cloud backups.

OCDJ is built by a small, focused team that DJs and cares about getting this right. We'd rather let the product do the talking than pitch ourselves. Want to know more about who you're dealing with? Reach out and we'll give you a straight answer.

You end up with a library that's consistent, complete, and easy to browse — reached in three passes: • Fix what's broken: duplicate genres, messy formatting, garbled characters, store watermarks, stuck prefixes. • Fill the gaps: artwork, release years, genres, labels, remixer credits. • Organize: a clean genre taxonomy, playlists for fast browsing, duplicates removed, everything filed so you can find it mid-set. Every change is previewed, and a snapshot is taken first so you can roll the whole thing back.

It all ladders up to one thing — a library that takes care of itself — across five areas: • Foundation — accurate, complete metadata across your whole collection. • Automation — watch folders, automatic FIX & ENRICH for new tracks, and backups in the background. • Customization — your rules for naming, genres, and structure, applied the same way every time. • Security — automatic backups and a snapshot before every run, so any change is reversible. • Intelligence — that clean foundation feeds DEBUSSY and smart playlists, so your collection works for you.

It runs itself — no kicking off a job every time you grab new music. Point OCDJ at your watch folders, set your preferences, and every track that lands there is cleaned, tagged, enriched, and added to your library on its own. Backups run quietly too, uploading only what changed. Set it up once and forget it.

That part's our secret sauce — but here's what it means for you: run Enrich and your tracks come back with the right artwork, release years, genres and labels. Gaps filled, wrong values corrected, accurate enough to trust. It matches on the track's own details, never the audio, so your files stay yours. Nothing applies until you've seen a preview. Want to see what it'd turn up?

Not with a preview of your own library right now — but nothing OCDJ does is irreversible. It takes a snapshot before every run, applies nothing without your approval, and anything it changes can be undone. You choose what gets fixed and how, you see it before it lands, and you can put it back.

DEBUSSY is a subscription that unlocks the full assistant: ask anything about your library, run batch jobs, reorganize playlists, sort out tags — all by talking, with every change previewed and undoable. It runs on message credits: each message uses one, bigger jobs a little more. There's also a DEBUSSY Pro tier for heavier workflows, and if you run low you can top up with credit packs that roll over permanently. For current prices, see the pricing page.

FIX & ENRICH used to be its own separate subscription — it isn't anymore. That ongoing auto-clean behavior — every new track in your watch folders cleaned, enriched, and filed automatically, tags fixed, artwork embedded, genres standardized, duplicates caught — now comes built into the BASE or PRO package, with cloud backup bundled in too. Tagging stops being something you ever sit down to do. DEBUSSY, the conversational assistant, is still a separate add-on. For current package details, see the pricing page.

The base app does the heavy lifting — the one-time DEEP CLEAN and library tools. For a lot of DJs that's everything they need to get started. From there you pick a package that fits: • BASE or PRO — turns it into set-and-forget: every new track handled automatically, with cloud backup bundled in. • DEBUSSY subscription — adds the conversational assistant: ask about your library and reorganize it by talking, every change previewed and undoable. For current prices, see the pricing page.

Not at all. If you can use DJ software, you can use this — nothing to configure by hand, no jargon to learn. You answer a few plain questions about how you like your music organized, and OCDJ handles the rest: fixing, enriching, filing, backing up. After that it just runs. And if you ever want something specific, you ask DEBUSSY in plain language — "fix these genres," "back that out" — and it's done. The technical part is our job, not yours.

Open the app and let it scan your collection — it shows exactly what's wrong: duplicates, missing artwork, gaps in genres, years and labels, garbled text. Real numbers on your own library. You see what OCDJ would actually do, then decide. If you like it, one DEEP CLEAN pass gets the whole library into shape — and from there BASE or PRO keeps it clean automatically.

Yes — DEBUSSY Pro is live. It's the higher tier for DJs who lean on DEBUSSY hard: more messages each month for heavier, more frequent batch work, so you're not watching your credits during a big reorganization. Everything DEBUSSY does is the same — Pro just gives you more headroom. For the exact price, see the pricing page.

That feeling is exactly why OCDJ exists — and the size of the mess doesn't matter, because you're not the one doing the fixing. One DEEP CLEAN pass works through the entire library in a single pass, however many thousands of tracks — repairing, filling in, de-duplicating, filing. You decide once how you want things, press go, and come back to a library that's actually in order.

Fair skepticism — so here's the straight version, limits included. What it's not: it's not magic and not a DJ-software replacement. It sits on top of Rekordbox or Traktor, only does what you set up and approve, and a first deep pass on a big library takes real time to run. No catch in the data either — your music stays yours.

FIX & ENRICH is OCDJ's ongoing fix-and-enrich engine — run it any time your library needs another pass, and it goes through, repairing garbled characters and store spam in artist and title fields, bringing artist and genre names into one consistent taxonomy, filling gaps — artwork, genre, label, release year — and re-wiring tracks that show up blank in your DJ software because their links are broken. It also finds duplicates (even when tags don't match) and groups them for you, and separates DJ sets and samples. A scan runs first and shows you what it would fix, broken down by category — there's no per-change approval step, but a snapshot is taken before anything changes, so you can roll it all back. It stays available from the sidebar any time you want to run it again — it isn't a one-off.

Drop a track in your downloads folder and walk away. Point OCDJ at your watch folders once, and anything that lands there is tagged, enriched, and filed into your DJ software automatically — no run to kick off, no app to open. The rules you set for your full library apply to every new file, so your collection stays consistent without effort. It even waits out a still-downloading file instead of grabbing it half-finished. This ongoing automation comes with the BASE or PRO package. Check the pricing page for current rates.

Enrichment fills gaps and fixes mistakes across your library: artwork, release years, genres and sub-genres, labels, and remixer credits. Empty fields get filled; wrong or conflicting values get corrected. Your beatgrids, cues, and DJ software analysis are untouched. Enrichment only touches metadata fields that are empty or clearly wrong, and a scan shows you what it will fix, by category, before the run — there's no per-change approval step, but everything is snapshotted first so you can roll it back.

Yes. During enrichment, OCDJ matches high-resolution cover art and embeds it straight into your audio files. No more blank thumbnails or fuzzy placeholders staring back at you in the browser — your collection actually looks like a collection, on every deck and every screen.

It catches duplicates you'd never spot scrolling — copies hiding under different filenames and mismatched tags, the kind a plain filename comparison walks right past. Detection runs automatically; it's always on. What happens to a duplicate is controlled by one setting, Duplicate Handling: by default the copy it doesn't keep is quarantined — moved to a review folder on your desktop, never deleted — and its useful tags are carried over to the copy you keep first. You can switch that setting to skip new duplicate imports, flag them for review instead, or keep both copies.

Never — and this is a hard guarantee, not a best effort. OCDJ only touches metadata fields like genre, comment, tags, artist, and title. Your beatgrids, waveforms, cue points, hot cues, and loops are completely off-limits. If you have Mixed In Key data in your comment or title fields, OCDJ detects it and works around it rather than overwriting it.

Your years of curation become almost impossible to lose. Backup protects three things at once: your music files, your library database (tracks, cue points, playlists), and the version history that ties it all together. It runs on its own — periodic snapshots, plus one right before and after OCDJ ever touches your library. There's always a precise point to roll back to around every change, and nothing you run is ever a one-way door.

If your drive dies tomorrow, your collection survives. Backup is included in every plan — you pay only for the storage you use, by the GB, with no base fee. A 500 GB library adds €10.99/mo. It covers your database (tracks, cue points, playlists) AND your audio files; the free local snapshots only cover the database. Your music lives in two places at once: your own drive, plus an encrypted copy in the cloud. • Every file is fingerprinted, so a corrupted copy can never overwrite a good one • Only new or changed files upload, and a sync resumes where it stopped • Export to a USB drive whenever you want a copy in hand If your machine dies: reinstall, sign in, and pull the whole library back down. Encrypted at rest, stored in the EU.

Yes — every run can be undone. OCDJ snapshots your library before it touches anything, so it can be put back exactly as it was. Just ask DEBUSSY to restore. Two paths: roll back to a saved snapshot, or pull the whole library — database (tracks, cues, playlists, ratings) and music files — down from cloud backup if you're on a new machine. Right after a run, paid tiers also get a one-click ↶ Revert. You don't have to roll back everything, either: ask for just one playlist or specific songs back, or to undo only certain changes.

Smart playlists built by asking DEBUSSY save you maintaining crates by hand. Define the rules — genre, date added, play count, rating, tags, combined with AND/OR — set a sort order and track limit, and DEBUSSY builds the playlist into your DJ software. They go further than your DJ software's own: exclusions like "everything NOT House," and more conditions combined at once. With a DEBUSSY subscription, just describe it in plain language: "everything I added this year that isn't house, rated 4 and up."

Ask DEBUSSY anything about your collection and get a real answer in seconds — no menus, no filters. Things like: - How many tracks are missing genre tags - Which playlists share tracks - What you added in the last month - How many 5-star tracks in a given genre - Where your duplicates are hiding It reads your actual library, so these are real numbers. And the more complete your metadata is after FIX & ENRICH, the sharper those answers get.

An iOS companion app is on the roadmap for winter 2026 — not out yet. When it lands, new tracks from your watch folders appear on your phone, where you can stream them, tag them, and move them around. Changes sync back to your desktop library (the desktop stays the source of truth), and your mobile play-counts stay separate. Streaming will require cloud backup, since that's what puts your files in the cloud.

DEBUSSY can help you pull a set together from what's already in your library. Ask in plain language and it gathers tracks by genre, label, BPM, ratings, and your tags — then builds a playlist that keeps itself updated as new music lands. The deeper layer — finding tracks that feel alike by ear and laying out an energy arc — is coming in a future update, along with the interactive map of your whole collection. Rule-based set building is live today.

Not yet — audio analysis of energy, mood, and danceability is coming in a future update, not something OCDJ does today. What's live now works from your metadata: clean, complete tags and the things already in your library (genre, label, BPM, ratings) let DEBUSSY organize and build playlists right now. The audio-feature layer, when it arrives, will power the deeper "find tracks that sound alike" and energy-flow tools. Want me to note your interest for when it opens up?

Open your DJ software after a run and the difference is immediate. Artist names read consistently — deadmau5 stays lowercase, MK stays uppercase. Genres line up into one taxonomy instead of fifteen near-duplicate spellings. Every track has artwork, garbled characters and store spam are gone from titles. Duplicates quietly doubling your crates are removed, blank tracks are fixed, and everything's filed so you can find what you want mid-set. The same collection, finally reading the way it should — and from then on it stays that way automatically.

Tell DEBUSSY once and it sticks forever. Say "always capitalize my genres" or "never touch my ratings" and that becomes a standing rule applied on every future run, automatically. You're not re-explaining your preferences each time — you teach it your way of doing things and it remembers. The more you tell DEBUSSY how you like your library kept, the more it handles on its own, exactly the way you'd do it yourself.

Yes — new music you drop into your watch folder is picked up and handled on its own: broken tags repaired, missing artwork and genres filled in, and everything filed into a playlist. Drop tracks in during the day and by morning they're sorted and ready to browse — without you opening a thing. One honest limit: OCDJ doesn't run your DJ software's own beatgrid and waveform analysis for you — that happens the next time you open Rekordbox or Traktor. Having it kick that off for you overnight is a separate piece still in testing.

Yes — and this is one of those fixes that makes you go "so that's why those were blank." Sometimes a track in your DJ software ends up pointing at a deleted database entry, so it shows up empty even though the audio file is right there on your drive. OCDJ finds those broken links and re-wires them back to the real track, clearing the ghosts from your collection. It runs as part of a normal FIX & ENRICH pass — a scan shows what it would fix, by category, before the run starts, and everything is snapshotted first, so it's reversible if you don't like the result.

Not yet — automated path repair is on the roadmap, not in the current version. The exclamation marks happen when you move your music files without updating the paths in your DJ software's database, so it looks for them in the old spot. For now, Rekordbox and Traktor each have a built-in Relocate function: in Rekordbox, right-click a missing track → Relocate (or "Relocate Lost Tracks" under Preferences › Library for a bulk move); in Traktor, Preferences › File Management › Relocate. OCDJ scanning your drives and fixing broken links itself is something we're researching — if you need it, tell us and it moves up the list.

Audio sitting in your music folders that isn't in your library — old downloads, duplicates from a rip, tracks you imported then removed. How it works: we already know where you keep your music and every file Rekordbox has, so this needs nothing from you. We walk your folders, compare against your library, and list what's on disk but not in it, with sizes. From there: open in Finder, move elsewhere, or import it properly. Nothing is deleted.

By learning, not guessing. A simple "capitalize each word" rule turns deadmau5 into Deadmau5, MK into Mk, and DJ EZ into Dj Ez — every one of them wrong. There's no rule that gets all these right, because the correct casing is whatever the artist actually uses. So instead of applying a rule, OCDJ matches against a catalog of how names are really written. The result: artist names come out the way they're meant to be, across your whole library, consistently, without fixing them one by one.

This one's on the way. Matching tracks by how they actually sound — not just their genre tag — is coming in a future update, not something DEBUSSY does today. What it can do right now is search your collection by things already in your library: genre, label, BPM, ratings, tags and comments — so you can pull together tracks that belong together and build a playlist from a plain sentence. The deeper "find tracks that feel alike by ear" part is coming — want me to note your interest?

Not yet — automatic playlist building when you add new music isn't switched on yet; it's coming, not live. Today, new music is cleaned, enriched and tagged, but OCDJ doesn't create or update playlists for you automatically. What you can do now: ask DEBUSSY, our AI assistant, to build a playlist for you in chat and describe what you want.

Yes — fake lossless detection is a live opt-in feature. It runs a spectral analysis on your audio to check whether a file that claims to be lossless (WAV, FLAC, AIFF) actually contains lossy-source content — quality inconsistency you can't spot from the file format alone. When it finds a suspect file, it flags it for your review. Nothing is deleted on its own. Because this decodes every audio file it adds time to a run, so it's off by default — you enable it explicitly during onboarding.

Yes — audio format conversion is live. When new music comes in through your watch folder, OCDJ can transcode it to a DJ-safe format of your choice — AIFF, WAV, MP3, whatever your CDJs or DJ software handle best. Set the target format once and it applies automatically to every new file. Tracks that are already in your library can be transcoded too: cues, beatgrids and playlists stay attached, and a full backup has to be in place before any file is touched. (Migrating a whole library between Rekordbox and Traktor is a separate feature, still in the pipeline.)

Yes — when new files come in through the watch folder, OCDJ moves them into a folder layout you configure. Pick the structure once (by artist, by date, by genre, or a nested combination) and every new file lands in the right place automatically. This only applies to files as they're added through the watch folder. The watch-folder layout never moves files that are already linked in Rekordbox or Traktor — relocating a linked file without repointing it would break your cue point and beatgrid references. Gathering the music you already have into one place is a separate tool, Centralise, which moves the files and repoints Rekordbox at them.

Yes. Genre normalization collapses the patchwork of spellings and capitalizations that accumulate from buying on different platforms — "House", "house", "HOUSE", and "Deep / House" all come into one consistent taxonomy. It also removes duplicate genre entries on individual tracks and strips vendor-injected genre spam. You choose whether to apply genre consolidation when you set your preferences. The result: a genre structure you can actually use for browsing and filtering in the booth.

OCDJ coexists with Mixed In Key rather than fighting it. For preservation: if you have MIK data in your comment or title fields, OCDJ detects it and works around it rather than overwriting it. Generating our own energy score to write into your comments — so you could filter and sort by energy in your DJ software without MIK — is on the way, not available yet. For now OCDJ reads and preserves the MIK energy you already have rather than producing its own.

Audio fingerprint deduplication — catching copies that share the same audio but have completely different tags and filenames — is built but currently held back for more testing before it goes live. The tag-and-path deduplication that runs today catches the vast majority of duplicates: the same track downloaded twice, slight filename variations, mismatched tags on the same file. For most libraries that handles everything. Audio fingerprinting will be the option for the harder cases — same audio across completely different metadata. It's coming in a future update.

Not over what you already have. Enrichment never overwrites a BPM or key your DJ software — or a tool like Mixed In Key — has already analysed. Those results are authoritative for your library, and replacing them with catalog lookups would break work you've already done. The one exception is a track with no key at all: during the run it gets one from catalog data, written in Camelot notation in the key field your DJ software reads. Tracks that already have a key are left exactly as they are. What enrichment otherwise fills: artwork, release year, genre, label and remixer credits — the fields that typically go blank or wrong when downloading from stores.

Yes — this is live, opt-in at onboarding. If your titles, comments or artist fields have key notation ("8A", "Am") or BPM numbers baked in as text, OCDJ can strip those out and leave the actual title clean. It only touches text fields — title, comment, artist — never the dedicated BPM or key columns, and never your audio, so your harmonic and tempo analysis stays intact. Especially useful if an old workflow baked key/BPM into your titles — you sort it out in one run without losing any real analysis.

Yes — messy genres are one of the most common things it sorts out. It consolidates the variations that pile up over years — the same genre spelled or capitalized five ways merged into one consistent label — and fills in tracks with no genre at all. The result: browsing or filtering by genre actually works, instead of the same style scattered across a dozen near-identical tags. You choose how aggressive this is when you set things up, so it matches how you organize — it won't impose a scheme you didn't ask for.

Yes — clearing out duplicates is a core part of a FIX & ENRICH run. Over years of importing, the same track sneaks in multiple times — re-downloads, re-imports, the same song in two folders. OCDJ identifies these and removes the clutter so each track earns one spot instead of three — shorter browsing, saner search, a lighter collection. You stay in control of how it handles them when you set things up, and because it snapshots before every run, anything it does is reversible.

Not as a setting today — a FIX & ENRICH run works across your whole library rather than letting you carve out folders to skip. If there's a section you're worried about, the safety net does the protecting instead: every run shows you what it will fix, by category, before it starts, and it's snapshotted first, so everything is reversible if you don't like a result. Per-folder exclusion was explored as a setting and cut before launch — genuinely not something you're missing in a menu somewhere. If it matters for your workflow, tell me and it goes on the list.

Your tracks are spread across folders and drives. This gathers them into one place per drive, and repoints Rekordbox at the new locations so nothing breaks. How it works: we scan where your music actually lives and show you every candidate destination per drive — how many files, how many gigabytes — and you pick; we don't guess. You choose the layout: one flat folder, Artist/Album folders, or keep the folder each track is already in. Nothing moves until a backup is confirmed. Every move is journalled before it happens, so an interrupted run rolls itself back.

The opposite of finding unused files: tracks still in your library whose file is gone from disk — so they won't play, and they aren't in your backup either. How it works: we check every track against the disk and show you which are missing and the drive each was last seen on. A track on an unplugged drive is reported as drive not connected, not as lost. For genuinely missing tracks, search for them again or remove the dead entry.

Format conversion to CDJ compatibility, to save space, or just because you like it that way. How it works: first we ask whether the conversion should apply to tracks already in Rekordbox, or files you drop in yourself. Library conversions keep your cues, beatgrids and playlists attached. Your original is never overwritten — the new file is written alongside, and the old one is only removed once the conversion is verified.

Rename your track files and restructure the folders they sit in — by artist, label, release year, or your own pattern. How it works: you choose the naming pattern and the folder structure; we show you the before-and-after on a handful of tracks before anything happens. Because Rekordbox finds your music by file path, every rename is paired with a library update in the same operation — cues, beatgrids, tags and play history stay attached. It is fully undoable in the same session.

Sort & Organize reads whatever your library already has — genre, key, BPM, energy tags if you've got them — and proposes a playlist structure from that, not just a genre split. How it works: we read your library's existing tags and metadata and show you the proposed structure before creating anything. You confirm the rules, then we build the playlists — your original library and any existing playlists stay untouched.

No — Sort & Organize creates new playlists from the rules you confirm; it doesn't touch or delete playlists you already have. And like everything else, it's undoable in the same session if you don't like the result.

It runs on your library as it exists when you trigger it — not just newly-added tracks. If you want ongoing, automatic organisation of new music specifically, that's what Auto-Pilot is for; Sort & Organize is the on-demand pass over what you already have.

It's a live sidebar item in the app — it runs the same guided way as everything else: you confirm the rules first, nothing changes until you approve.

Yes — Centralise shows every candidate destination per drive, with file counts and sizes, and you pick. It never guesses a destination for you.

Not yet — Centralise is still being built and hardened before it ships. It's visible in the app so you can see what's coming, but the team hasn't cleared it to run on real libraries yet.

Three choices: one flat folder, Artist/Album folders, or keeping the folder each track is already sitting in — just gathered onto one drive instead of scattered across several.

It's read-only — it lists what's on disk but not in your library, with sizes, and leaves the decision to you: open in Finder, move it, or import it properly. Nothing is deleted by the scan itself.

Yes — Find Unused is a live, working sidebar item.

It scans the music folders it already knows about — the same locations your library reads from — and compares what's there against your library. It's not a whole-disk scan.

It tells the two apart — a track on a drive that's simply not connected right now is reported as "drive not connected," not as missing. Genuinely missing tracks (the file is gone) are reported separately.

Not yet — Missing Files is still being built and hardened before it ships. It isn't cleared to run on real libraries yet, so it isn't in the app today.

The detection side tells you what's missing and where it was last seen. Automatic repair of the broken link is a separate, still-in-research part of this feature — for now, the fix is you searching for the file again or removing the dead entry.

Yes for tracks already in your library — that path is live. Converting files you drop in separately (outside your library) is a related but separate capability that's still being finished.

Common DJ-friendly formats — AIFF, WAV, MP3 and the like, whatever your CDJs or DJ software need. You choose the target format when you run it.

Yes — like every ORGANISE-family action, it is fully undoable in the same session. You also see a before-and-after preview on a handful of tracks before anything happens to the rest.

It's visible in the app; it's still being built and hardened, and doesn't have a tracked feature id yet either. If you want to know exactly where it stands, the team can tell you.

Backups run on an automatic schedule, and you can also trigger one manually from the Backups dashboard any time. The dashboard shows every backup taken — when, and how big.

Yes — the Backups dashboard lets you trigger a manual backup in addition to the automatic schedule, e.g. right before you try something you're unsure about.

Undo reverses the most recent run. Restore goes further back — to any point you have a backup for. Both live in the same place, and either way, you're shown exactly what will change before anything happens.

Every move is journalled before it happens, so an interrupted run rolls itself back rather than leaving things half-moved — and you can undo the whole run in the same session regardless.

Find Unused itself just lists what's on disk but not in your library. Spotting whether one of those files duplicates something you already have is what duplicate detection does — worth running both if you've got a folder of old downloads to sort through.

That depends what your backup actually covers — the library entry and the audio file are two different things to protect. Check the backup overview for exactly what's included before assuming a missing file is recoverable that way.

It depends on the formats involved — converting between two lossless formats (like WAV and AIFF) loses nothing; converting to or from a lossy format (like MP3) works the way format conversion always does. You choose the target format, so you're in control of that trade-off.

Common ones — artist, label, release year — or a pattern of your own. You choose the pattern and the folder structure, and see a before-and-after preview on a handful of tracks before it runs on the rest.

It compares your tracks directly, not just the tags — so duplicates are found even when filenames or metadata don't match.

Whichever copy matches your preferred format — FLAC over MP3, for example. Cues and playlists from the copy it drops are carried over to the one it keeps, so nothing is lost.

Nothing is deleted. The extra copies move to a folder on your desktop, so you can check them yourself before deciding to get rid of them for good.

Yes — it works on both Rekordbox and Traktor. On Traktor, it warns you before touching anything that looks like a stems file, since stems aren't real duplicates even though they can look similar.

Generate and run a tailored script against your library — describe what you want in chat, and DEBUSSY writes the code and runs it for you.

No — you describe what you want in plain language in chat, and DEBUSSY writes the script for you.

It's a Pro feature. Other plans get a trial allowance to try it first.

Yes — a snapshot is taken before the script runs, so if it does something you didn't want, it rolls back cleanly.

Yes — it's a toggle, not a commitment. Turn it off any time from the sidebar, and it never skips your usual backup and undo protections while it's running.

Deep Clean is the guided first pass every new library goes through — it's what FIX & ENRICH runs the first time. We show you what we found before changing anything, and everything else in the sidebar stays locked until it finishes once.

No — after the first run it stays available any time from the sidebar as a normal FIX & ENRICH run. The "first pass" framing only applies once, to unlock the rest of the app.

Yes — nothing changes until you approve the run. We scan your library, show you what we found, and you confirm before anything is written.

Not yet as a sidebar click — that entry point is still coming soon. DEBUSSY, our AI assistant, can already build one for subscribers today: describe the rule in chat and it does the rest.

Whatever matters to you — genre, BPM range, recently added, and similar criteria. You describe the rule to DEBUSSY, our AI assistant (a subscription feature), and the playlist keeps itself current as your library changes.

Sort & Organize builds playlists once, from your library as it is today. Super Smart Playlists, built via DEBUSSY (our AI assistant, subscription) in chat, keep updating themselves afterward — automatically adding new tracks that match the rule you set.

You ask for it in chat — tell us which playlists and which drive, and we build the USB from just those. It's never your whole library by default.

Rekordbox libraries only. Traktor doesn't use the PIONEER folder format CDJs read, so there's nothing for this to export from a Traktor library.

No — export to the same stick again and only what changed gets copied, not the whole set over again.

Free space is checked before anything is written, so a copy that can't finish is refused up front instead of failing partway through.

It levels the tracks on a USB export to the same club-ready volume, so you're not diving for the gain knob because the next track came in quiet. Coming soon — still in testing.

No — it only adjusts the copy that goes onto the USB. Your original files are never touched or re-encoded, and it's coming soon, not live yet.

CDJ hardware ignores the gain tags in your library, so leveling has to happen in the actual audio that goes onto the USB — which is why it's done on the export copy, not your library.

A built-in limiter holds a boost back rather than let a track clip. It's coming soon and still in testing, not switched on for everyone yet.

It rebuilds your Rekordbox library from a USB device you'd exported to a CDJ — a safety net if your main library needs recovering. Coming soon — not yet available to click.

Rekordbox-only — Traktor doesn't write the PIONEER folder format this reads from.

For when your main library needs recovering and a USB you exported to a CDJ is the most complete copy you have left on hand.

Not yet — it's coming soon and not available to click yet.

A health check for your whole library — it scans for metadata completeness and quality issues like missing tags, weak artwork, and incomplete data, and gives you a picture of where things stand.

Just a report — it checks your tracks against completeness and quality rules and summarises what's solid and what needs attention, without changing anything itself.

FIX & ENRICH actually fixes your library. Library Health just tells you where it stands — missing tags, weak artwork, incomplete data — without making any changes.

Not yet — it's coming soon and not available to click yet.

A read-only look at your library's shape — track counts, genres, years, and how your collection has grown over time.

No — it reads your existing library data and summarises it. Nothing is scanned from disk and nothing changes.

Statistics is about your collection — counts, genres, years, growth. Play History is about what you've actually played — read from your DJ software's own play records.

Not yet — it's coming soon and not available to click yet.

Your play history — what's been played, how often, and when — pulled from your DJ software's own records.

We read the play-count and play-date data your DJ software already keeps — read-only, nothing about your library changes.

It reads whatever play-count and play-date data your paired DJ software keeps, so it follows the same platform support as the rest of OCDJ.

Not yet — it's coming soon and not available to click yet.

Your saved ADJ projects and sessions — a way to continue a conversation or task you started earlier instead of starting over.

No — nothing is saved as a project unless you explicitly ask us to. We never infer one from a conversation on our own.

Enough context to jump straight back in — every project you save shows up with what you need to continue, not just a bare title.

In the sidebar, under Sessions — every project you've explicitly saved shows up there.

Your library comes back clean, complete, and easy to dig through — years of messy tags from a dozen download sources turned into one consistent collection, without you touching a single tag by hand. Under the hood: broken artist names, garbled titles, encoding errors and store watermarks fixed first. Then gaps filled — missing artwork, years, genres, labels, remixer credits looked up and added. Finally the shelf organized: duplicates detected and scored, non-music pulled aside, genre structure unified. A scan shows you what it will fix, by category, before anything runs — there's no per-change approval step, but your original is snapshotted first and never edited in place. Want to see what it'd turn up in your collection?

Your artist names, titles and genres come out consistent and readable — the kind of quality that makes a library actually browsable. What it goes after: • Artist names — casing, punctuation and spacing normalized, tricky ones right ("deadmau5" stays lowercase, "DJ EZ" stays uppercase) because it learns from a real catalog, not title-case rules. • Titles — stuck prefixes, trailing junk and store-injected formatting stripped. • Featuring credits — feat./ft./Feat. variants unified to one consistent form. • Misplaced info moved home — label noise out of titles; key prefixes removed from titles with the key preserved in the Key field. • Store watermarks — brand names injected into artist or title fields removed. • Encoding errors — garbled characters from mismatched encodings repaired. • Duplicate/conflicting genres — collapsed to one clean value. Every fix is shown to you first. Nothing applies until you approve it.

Once your tags are fixed and complete, this stage makes your collection fast to dig through in the booth. • Spots duplicates and scores them by audio quality — keep the best copy with confidence, drop the rest. • Pulls non-music aside — DJ sets, samples and sound effects separated from tracks. • Builds one clean genre structure across the whole library, replacing the patchwork from years of downloading from different sources. • Adds ready-to-use service playlists on top of your existing structure for your DJ software. The result: a library you can actually navigate at speed.

Your audio files stay on your machine — the whole run processes locally, and your music is never uploaded during a run. Four things touch the internet: • Subscription check — a quick verification your plan is active. • Enrichment lookups — just enough to find the right artwork, year, genre and label. Your audio is never sent. • A working copy of your library's own metadata (titles, tags, full file paths — never audio) — uploaded after every run so DEBUSSY can answer questions about your collection. This happens for every signed-in account, whether or not you use DEBUSSY. • Cloud backup — your actual music files, bundled into your BASE or PRO package. Because everything runs locally, the app needs to stay open during a run. Cloud backup adds an encrypted off-site copy of your audio — alongside your own local drive — automatically, as part of your package, not something you turn on separately.

Fair question — it can feel like a lot up front. The short version: it's set-it-once. You do this once, and from then on it runs forever from your choices. Each step builds on the last: • It reads your DJ software library first, so it knows what's actually in your collection. • It asks how you want things done — casing, genre style, and so on. There's no safe default that's right for every DJ's library, so it asks once rather than guessing. • A scan shows you what each run will fix, by category, before it happens. Once set up, it just runs. Tweak any setting whenever you like — it takes effect on the next run.

Yes — automatically, every single time, before a single change is made. If the snapshot can't be taken, the run won't start. What that means: there's no run you can't take back. Don't like the result? The snapshot puts your library right back where it started. Each snapshot only stores what's changed since the last one — quick, low on disk. Every one is integrity-checked (track counts and checksums verified), so you're always falling back to a known-good copy, never a corrupt one.

For the initial run, yes — keep it open. The work runs on your own machine, so the app needs to be running. You can watch it live on the Progress screen. After that first pass it's set-and-forget: new tracks landing in your watched folders are processed automatically in the background. The 'stay open' rule really only applies to that first big run.

FIX & ENRICH isn't its own plan — it's a feature included on BASE and PRO (any paid plan), not sold separately. Once you're on either plan, it keeps your library fixed and enriched on its own — drop new tracks in your watched folder and they get tagged, enriched and filed automatically. What it covers: tag and metadata repair, enrichment (artwork, genres, labels, years, remixer credits), duplicate detection and quality scoring, automatic processing of new tracks, and a fresh snapshot before every run. PRO additionally adds DEBUSSY, the AI agent. For current prices, see the pricing page.

Point it at your downloads folder and any new track that lands there gets fixed, tagged, enriched and filed into your library on its own — no run to start, no finger lifted. It goes further than you'd expect: an overnight job can open your DJ software, wait for beatgrid and waveform analysis to finish, then close it again — new tracks ready to play by morning. A mobile companion app is coming (winter 2026) — when it lands you'll see new tracks on your phone and tag on the go, with changes syncing to your desktop. Set your preferences once. After that, it just runs.

Your playlists are untouched — nothing you built gets deleted, reordered, or restructured. OCDJ only touches track tags and metadata; your folders, sub-folders and track order stay exactly as you left them. It can add new service playlists on top of what you've got — additions only, never edits to your existing crates. On Rekordbox specifically: track tags inside Rekordbox are left completely alone. Traktor has no native tag organization of this kind, so OCDJ brings that same structure across, filling a gap your DJ software leaves.

We keep the matching engine itself under wraps — but what matters is the result: even tracks with messy, half-missing or wrong tags get matched to the right info. Remixes, edits, alternate versions, tracks with nothing but a filename — all handled. When it can't be sure of a match, it skips rather than guesses — so you never end up with confident-but-wrong data. Curious what it'd match in your library?

DJ software treats every unique spelling of an Artist, Genre, or Label as a separate row in its database. Download from five stores and you end up with "Tech House", "Tech-House", "tech house" and "TECH HOUSE" as four separate genre entries. OCDJ merges these as part of the run: normalizes Unicode, strips stray whitespace, collapses entries that differ only in capitalization or punctuation — so your genre, artist and label browsers show clean unique lists instead of dozens of variations of the same name. Runs automatically, no selection needed.

Honestly, a deep DEEP CLEAN pass of a whole collection isn't a five-minute job — for a large library you kick it off and let it run, ideally with time to spare, not minutes before you leave. After that first pass, staying in shape is automatic, so you're never in this rush again.

The rest of the sidebar unlocks — every feature stays locked until your first clean run completes. After that, you don't need to repeat it; FIX & ENRICH stays available any time you want to run it again, and Auto-Pilot can handle new music going forward.

Yes — safety is what we obsessed over most. • Your original library file is never modified • A full backup is taken before anything runs • Every change goes through one protected path with integrity checks before and after • If anything looks off, one move returns your library to its pre-run state • Cue points, beatgrids, playlists and hot cues are never touched. Track tags are what a run fixes, and every tag change is covered by that pre-run backup

Your original library file is never modified. OCDJ reads it, does all work on a copy, and only swaps that copy in once integrity checks pass. Your original is always kept as a backup — going back is never more than a step away.

FIX & ENRICH only touch the metadata your DJ software reads — not the audio inside your files. The sound stays exactly as it was. One opt-in exception: if you turn on artwork embedding, high-resolution album art is written into the file's tag fields. That's still the tags, not the audio. Existing beatgrids, waveforms, and cue points are all left untouched.

Undo works at two levels, both live. The quick path: right after a run, paid tiers get a one-click ↶ Revert that undoes the whole operation in a single move. Or open your version history any time, pick the snapshot from just before a run, and restore it — note that a whole-snapshot restore brings your entire library back to that point, so anything added afterwards rolls back too. For a finer pass, ask DEBUSSY to undo only specific tracks, fields or playlists from a run; it shows you exactly what it will revert and waits for your approval, so you keep the edits you're happy with.

Every run takes a snapshot and verifies it — SHA-256 checksums, a track-count check, and corruption detection. If anything doesn't add up, the write is simply refused and your original is left untouched. The same SHA-256 fingerprinting guards your cloud backups: if even one byte of a stored file changes, the mismatch is caught, so a corrupted copy can never quietly overwrite a good one. Nothing broken ever gets swapped in, and your previous versions are always there to fall back on.

It's all on your machine. Your library, the backups, the snapshots, and the ability to roll back — every piece of the safety system lives locally. Why that's good for you: a restore never waits on an internet connection, and your library never has to leave your computer just to be protected.

An interruption leaves your original library exactly as it was. Work happens on a separate copy; that copy is only swapped in after everything verifies — so a run either finishes or changes nothing at all. No half-finished state is possible. Your pre-run backup is kept regardless, and the app tells you what happened when it restarts.

The exact internals are our secret sauce — but here's what it means for you: every single change to your library funnels through one protected path, and nothing can sneak around it. Work happens on a copy, it's checked, and only then swapped in — so your original is never the thing at risk. Want me to show you your current backup snapshots so you can see the safety net for yourself?

A scan runs first and shows you what it would fix, broken down by category, before anything changes. You decide the settings — casing, genre style, and so on — that control how fields get formatted. There's no per-change approve/reject step; instead, a snapshot is taken before the run so everything is reversible if you want to undo it.

Yes — DEBUSSY plays by the same safety rules as everything else. Every action it takes that changes your library goes through the same protected write path and drops a revert anchor first, so anything it does can be undone. Just ask me — 'show me my recent operations' or 'undo that last change' — and I'll walk you through it.

No single failure can cost you your library. Three layers stack up: • Two independent copies — your local drive, plus an encrypted backup in the cloud. Lose one, the other survives intact. • A corruption check runs three times — before writing, before snapshotting, before restoring — so a corrupt file can never overwrite a good backup. • Snapshots are all-or-nothing — a snapshot or restore either completes fully or leaves no trace. No half-finished state.

Then you undo it — that's the whole point. A full snapshot is taken before every run, so your entire library can be returned to exactly how it was, in one move. It's live: ask DEBUSSY to roll back your library and it walks you through your snapshot history, shows you what's in each, and does the swap when you confirm. The rollback is atomic — if anything goes wrong mid-swap, your original stays intact. So go ahead and try things; the way back is always there.

That caution is completely fair — your collection took years, and you should be protective of it. OCDJ is built around that fear, not in spite of it. Before any run it takes a full snapshot, so the exact state you started from is always recoverable. It works on safe copies and only swaps changes in once they're verified — never editing your originals in place — and it never touches the truly irreplaceable: your cues and beatgrids stay exactly as they are. Nothing happens that you didn't set up and approve, and if you ever don't like a change, you undo it. The whole design assumes your library is precious and every mistake must be reversible.

There's no schedule to set — cloud backup isn't on a timer you pick, it just runs. Snapshots happen automatically around every FIX & ENRICH run plus on a regular background cadence, uploading only what's new or changed since last time. You don't need to think about timing or remember to kick one off. If you want more control over when it runs, that's worth telling the team — it's not something you're missing today, it just isn't built that way.

Not yet — and we'd rather tell you that plainly than let you try it. USB Restore is currently marked broken in our own tracking while a data-format issue (a byte mismatch in the analysis files Rekordbox writes for CDJs) gets fixed. It's visible in the sidebar so you know it's coming, but it isn't safe to run yet.

It rebuilds your Rekordbox library from a USB drive you'd previously exported for use on CDJs — useful if your main library needs recovering and a USB export is the most recent copy you have.

No — it's Rekordbox-only. It rebuilds from the PIONEER folder format Rekordbox writes for CDJs, which Traktor never creates, so there's nothing for it to read on a Traktor setup.

No — for almost everyone, a normal Restore/Undo from your automatic backups is the right path. USB Restore exists for the narrower case where your main library and its cloud backup are both unavailable, but you happen to have a USB export you made for CDJs.

It'll follow the same rails as every other library-changing action here: preview first, confirmed backup before anything happens, undoable in the same session. We're not shipping it in any other shape.

Good news first: nothing was changed. DB_CORRUPT means our integrity check spotted something unexpected in your library database before we wrote a single thing — so we stopped, on purpose, rather than build on a problem. Your original library file is exactly as your DJ software left it, and the snapshot we take before every run is right there if you want to roll the whole library back to a known-good version. That's the system working as designed — it caught the issue instead of passing it to you.

Straight answer: it's very unlikely to have come from our side. OCDJ never edits your original library file. It reads it, builds a copy alongside it, and only swaps that copy in after it passes integrity checks — your original stays untouched throughout. We also take a full snapshot before every run. If something was already wrong when we opened your library, the problem pre-dates us — and we may be the ones who caught it for you. Let's look at your snapshots and roll back to a version you trust.

Your original library file was never touched — OCDJ always works on a copy. The way back: • Open OCDJ, go to your version history, and restore the snapshot taken just before your last run • If your DJ software can't find the file right after a restore, close it fully and reopen it — it should pick the file back up on its own

A full point-in-time snapshot is taken automatically before every run. Your version history is delta-based — only changes are stored — so it stays fast to create and light on disk space. There's no cap: you can scroll back through the history and restore your entire library to any snapshot, exactly as it was.

The how is our secret sauce — but the what matters more anyway: before we touch anything, we verify your library is intact, and we check it again after every run. If something looks off at any point, we stop and surface it before it becomes your problem to untangle. Your original files are never at risk either way. Want me to walk you through what happens when a check trips, or how to roll back to a clean snapshot?

Depends which restore. A snapshot rollback (undoing a recent run) only rolls back your DJ software's library database — playlists, metadata, organization. Your audio files (MP3s, FLACs, WAVs) aren't touched; they stay on your drive exactly where they are. A full cloud restore is for when your music is actually gone — a new machine or a wiped drive: it re-downloads your backed-up audio and relinks your library to it. It only ever writes files you no longer have — it never deletes or overwrites music you still have.

Your playlists come back exactly as they were when that snapshot was taken. A whole-snapshot restore returns your entire library database to that point — so anything added afterwards, including new playlists, rolls back too. Worth keeping in mind when you pick a snapshot. If you only want one playlist back, ask DEBUSSY to restore just that playlist instead — the rest of your library, newer playlists included, stays as it is.

If the trouble pre-dates OCDJ, our integrity check catches it on the very first run and flags it before we touch anything — so nothing gets made worse on our watch. What happens next depends on what you already have: our snapshots only begin the moment you start using the app, so for damage from before that, the way back is whatever backup you have elsewhere — an older copy from your DJ software or an external drive. If you've got a known-good older backup, that's our starting point. Tell me what you've got and we'll work from there.

Honest answer: if there's no backup anywhere and the original library file is damaged, recovery options are limited. Don't give up yet — your DJ software has its own auto-recovery and repair tools worth trying first. Our team has worked through many recovery scenarios and may see an option specific to yours. Going forward, this is exactly what OCDJ's automatic pre-run snapshots and optional cloud backup exist to prevent.

Your original library is safe. OCDJ writes to a new copy, never your original file — so a crash partway through means the unfinished copy is discarded. Nothing was written to your real library. Your pre-run snapshot is still there if you want to roll back, and you can start a fresh run on relaunch. A crash or power cut mid-run is exactly the scenario this design was built for.

If your DJ software is flagging damage and you have an OCDJ snapshot, rolling back to that snapshot is the cleaner first move — it returns you to a version we already verified was intact. • Open OCDJ, go to your version history, and find the most recent clean snapshot • No OCDJ snapshot yet? Your DJ software's own built-in repair is the natural next step Not sure which way to go? Tell me what the message says — this is exactly the call our team is glad to help you make.

We keep the exact mechanism under wraps — but in practical terms: every file in your collection is checked before we touch anything, and checked again afterward. If something doesn't line up with what a clean, intact library should look like, we stop and surface it before it ever becomes your problem. Want me to show you what a tripped check looks like, or how to roll back to a clean snapshot?

Two places: your own drive, and an encrypted off-site copy in the cloud. • Your local drive — where your library lives, and where pre-run snapshots are kept. Always available, no internet needed. • Backblaze B2, in the EU — your cloud backup, encrypted with your own keys before it ever leaves your machine. So a hard-drive crash, a stolen laptop or a spilled drink doesn't take your collection with it: the cloud copy is untouched and restorable. Backups run quietly in the background and sync only what's changed.

No sugar-coating: if the problem pre-dates your OCDJ snapshots and no other backup covers it, options are limited. The best next step is a direct conversation with our team — they've worked through a wide range of recovery scenarios and can tell you straight what's realistic for your specific situation. Whatever the outcome, we'll get your library into snapshot coverage from here on.

You only pay for the parts you want. Here's the shape: • One-time Initial FIX & ENRICH — covers a track allowance, with a small per-track charge above that. • One-time re-clean — a fresh full FIX & ENRICH pass whenever you want one later. • BASE or PRO subscription — keeps your library fixed and enriched automatically as new tracks arrive; FIX & ENRICH isn't sold on its own, it's included on any paid plan. • Cloud Backup — bundled into your plan, not billed on its own. Priced by how much you store. • DEBUSSY subscription — the conversational assistant, on a message-credit system. Top-up packs roll over permanently. For current numbers on any plan, click here for pricing.

No free trial, and nothing handed out free in the way of app credits — there's no card required to create an account, and nothing is charged until you choose something. The health report — a free scan of your DJ software library showing exactly what's wrong (duplicates, missing artwork, years, labels, tag gaps) with real counts from your own collection — isn't live on the site right now; it's coming back. DEBUSSY itself runs entirely on paid credits; new accounts start with none to use for free. When you're ready: DEEP CLEAN for a one-time deep reset, or BASE/PRO to keep the library maintained automatically with backup included. For current prices and any active offers, click here for pricing.

Credits are what your DEBUSSY conversations run on — roughly one credit per message, with bigger batch jobs costing a little more. Your subscription comes with a monthly allowance that refreshes each billing cycle; unused monthly credits clear when the new cycle starts and don't roll over. Top-up packs are the opposite: they roll over permanently, carrying forward month to month and never expiring. There's also DEBUSSY Pro for heavier, regular use. For current allowances and prices, click here for pricing.

Grab a one-time credit pack whenever you need it — no subscription upgrade required. Buy it in the app and it lands instantly. Top-up credits stack on your monthly allowance and roll over permanently — they carry forward month to month and never expire. For current pack sizes and prices, click here for pricing.

Two tiers, both running the full conversational assistant on the same message-credit system — the difference is monthly headroom. • DEBUSSY — standard subscription, monthly message allowance that suits most DJs. • DEBUSSY Pro — higher allowance for heavier, regular use. Either way, top-up packs that roll over permanently are available if you need extra in a given month. Most people start on the standard plan and move up only if they're bumping the ceiling. For current allowances and prices, click here for pricing.

It's simple and low-commitment — everything is month-to-month, so you're never locked into a contract. Subscriptions bill monthly and renew automatically on the same date each month, and your DEBUSSY credit allowance refreshes at the start of each new cycle. There's no annual plan; you can cancel any time.

Cancel any time — no lock-in, no contracts. You keep full access right through to the end of the billing period you've already paid for, and you can cancel from inside the app or by getting in touch with our team. And your cleaned, enriched library stays on your computer either way — cancelling doesn't take that away.

Your fixed, enriched library lives on your own computer — it doesn't vanish when you cancel. All fixed tags, filled artwork, and organized genres are yours to keep. What changes by plan: • BASE or PRO — new tracks stop being auto-enriched, and cloud backup (bundled into the package) stops running new snapshots too, since they're part of the same package. Existing backup snapshots are kept for a period after cancellation; contact our team for the exact window. Your existing library stays exactly as it is. • DEBUSSY — credit balance and chat access end when the billing period closes. For the specifics of your account, our team can give you a definitive answer — want me to put you in touch?

Refunds are handled case by case, and cancelling is always in your hands. • Subscriptions: cancel any time in the app or by emailing [email protected]. Cancelling takes effect at the end of the period you have already paid for, and you keep access until then. There is no prorated refund for the unused part of that period. • If you want a charge refunded, contact us within 14 days of it and we will review it case by case. A refund is generally not available once the subscription has been actively used for more than 14 days of that period, or once data has been uploaded under a Cloud Backup plan during that period. • If a significant, documented outage or defect stopped you using the service, tell us within 14 days and we will look at a prorated credit or refund. • One-time library jobs: if you email [email protected] before the job starts processing, we cancel it and refund the full amount. Once processing has begun the fee is non-refundable, because the work is delivered immediately with your consent — unless we made a material error in processing, in which case tell us within 14 days of the job finishing.

This is DEEP CLEAN — the one-time first pass every new library goes through. It runs your whole collection through one pass and gives it back consistent, complete, and ready to use: repairing garbled characters and store spam in artist and title fields, bringing artist and genre names into one consistent taxonomy, filling gaps — artwork, genre, label, release year — and re-wiring tracks that show up blank in your DJ software because their links are broken. It also finds duplicates (even when tags don't match) and groups them for you — a scan runs first and shows you what it would fix, broken down by category, and a snapshot is taken first so you can roll it all back. It's a one-time payment, priced in bands by how many tracks you have — bigger libraries land in a higher band, but it's still a single flat payment for your band, not a per-track meter. After this first pass, your library is clean and complete — a BASE or PRO package keeps it that way as new tracks arrive, with backup included too. For the current price bands, click here for pricing.

Yes — if you want a full fresh pass again later (say, after a big library overhaul), you can run DEEP CLEAN again; it runs the exact same deep pass as your first one. It's a one-time thing, not a subscription. For the current pricing, click here for pricing or ask our team — the re-clean pricing details aren't something I want to guess at.

Yes — you can change plans as your needs shift: move between BASE and PRO (backup follows automatically, since it's bundled into whichever package you're on), or move up to DEBUSSY Pro for more DEBUSSY headroom. For the exact steps and how a mid-cycle change is handled, our team can walk you through it directly — want me to put you in touch?

We run offers now and then, and if you've got a discount code you can apply it at checkout. I'd rather not name a specific deal that might have expired, so for anything current the best move is to check with our team or keep an eye on the site.

It depends which kind: • Monthly subscription credits — the allowance in your DEBUSSY plan — reset each billing cycle. Unused ones are cleared when the new cycle starts and don't roll over. • Top-up credits — packs you buy separately — roll over permanently, carrying forward month to month and never expiring. If you want credits that stick around, top-up packs are the ones that bank.

If your DEBUSSY credits hit zero, you can't send new chat messages until you top up — two easy ways: • Wait for your monthly allowance to refresh at the start of your next billing cycle, or • Grab a top-up pack right away — those credits roll over permanently. Nothing else stops. FIX & ENRICH, Backup, and the rest of your library tools keep running normally regardless of your credit balance — only the DEBUSSY chat is metered. For current top-up prices, click here for pricing.

Do the math on your own time. Sorting a library out by hand — fixing casing, hunting down missing artwork, years and labels, weeding duplicates, sorting hundreds or thousands of tracks — is hours of mind-numbing work, and it's never truly done because new music keeps landing. OCDJ does that whole job in one pass, then keeps doing it automatically for every new track. For a working DJ, that's the difference between spending your evenings on admin and spending them digging for music.

Takes about two minutes. Head to the sign-up page, create your account (no credit card needed to start), and download the OCDJ desktop app. The app walks you through a short pairing flow to link your machine with your account. The free health check — a scan of your DJ software library showing exactly what's wrong (duplicates, missing artwork, years, labels, tag gaps) with real counts from your own collection — isn't live on the site right now; it's coming back. For now, pick DEEP CLEAN for a one-time deep reset, or BASE/PRO to keep it maintained automatically with backup included.

I hear you — and we'd much rather help than lose you over budget. Drop us a message at [email protected] explaining your situation and what you need, and we'll see what we can do. We want OCDJ to be something DJs of every budget can use — so if money's the only thing in the way, reach out. We're always here to help work something out.

Yes — and it's a real earner. You get your own referral link, and when someone subscribes through it you earn 20% of their subscription. A sign-up counts for up to 60 days after someone clicks your link. Earnings are paid to your PayPal once you reach €40, after a 30-day hold (which covers the refund window), and you get a dashboard to track clicks, sign-ups, and earnings. Want in? Just say the word and we'll get your affiliate link set up.

There's no pause option today — but cancelling gets you almost the same thing without the extra complexity. Everything is month-to-month with no lock-in: cancel any time, keep full access through the period you've already paid for, and your cleaned library stays right where it is on your computer either way. When you're ready to pick back up, just resubscribe — nothing about your setup is lost in between.

Yes — DEEP CLEAN is a one-time purchase, and it's the only thing you need to buy to get your library fixed and enriched once. No Base or Pro plan required, no ongoing charge, nothing to cancel later. The monthly plans (Base, Pro) are for keeping your library that way automatically as new tracks arrive, plus cloud backup and DEBUSSY (Pro has far more DEBUSSY credits: 400 a month against Base's 10). They're the natural next step after a Deep Clean, not a requirement to run one.

No — both monthly plans (Base and Pro) always bundle cloud backup. It isn't a separate line item and there's no way to opt out of it on either tier; you only pay for the storage you actually use, by the GB, with no base fee. Our stance is straightforward: an automated tool that changes your library isn't safe to run without a backup underneath it, so we don't offer a plan that skips it. If you don't want an ongoing plan at all, a one-time DEEP CLEAN needs no subscription and no backup — see the standalone Deep Clean answer.

We wanted a pricing model that's fair for hobby DJs and power users alike, without turning it into a maze of add-on packages — one price per plan, everything included, kept deliberately simple. We think about what we charge for in two shapes: work that delivers its value directly, in one pass, and work that delivers value on an ongoing basis, over time. DEEP CLEAN is direct value — a single deep pass that gets your whole library into shape, paid for once. The monthly plans are ongoing value — they keep your library maintained as new tracks arrive, month after month. The subscriptions are complete packages, not a stack of add-ons: every plan bundles cloud backup by default — there's no separate backup subscription — and what you pay for storage scales with how much your library actually holds, billed by the GB from GB 1, with no base fee either. DEEP CLEAN works the same way in spirit — one flat number for your library, not a per-track meter — but it's priced in bands by track count rather than by gigabytes, since it's a one-time pass rather than something we store month over month. Pay once and your library is clean immediately; a BASE or PRO plan is what keeps it that way afterward. Which one do you want the numbers for — DEEP CLEAN, or the monthly plans?

Two monthly plans. • Base — €12.50/mo • Pro — €22.50/mo Both are complete packages, not a starting point you add options to. The only part of the bill that moves with use is backup storage, and that is billed purely by how much you store.

Every plan includes the same three things: • FIX & ENRICH — new tracks are tagged and enriched automatically as they arrive, so the library stays clean after its first pass. • Cloud backup — bundled into every plan. It is never a separate subscription and there is no way to opt out of it. You pay only for the storage you actually use, by the GB from the first GB, with no base fee. • DEBUSSY — the AI assistant, for everyday questions about your library. Backup is bundled on purpose: an automated tool that changes your library isn't safe to run without a backup underneath it.

Same product on both — same FIX & ENRICH, same cloud backup, and on both DEBUSSY will write and run custom scripts against your library. Two things change. • Base — €12.50/mo: 10 credits a month — enough to get a feel for what DEBUSSY can do, not to lean on it. • Pro — €22.50/mo: 400 credits a month, which is DEBUSSY as a working tool rather than a demo. Pro also gets emergency restore: rebuild a playable CDJ USB straight from your cloud backup if a stick is lost, stolen or dies before a gig. Credits are the real measure: chat and custom scripts both draw on them, so the count is how much work DEBUSSY does for you each month. Both tiers CAN run custom scripts; on Base you simply won't have the credits to do much with them, so pick Pro if DEBUSSY is meant to do real work for you.

Most of your library never leaves your machine. Anything that does is encrypted. If you turn on Cloud Backup, your music files are encrypted with your own AES-256-GCM keys before they leave your machine, and they stay encrypted at rest with Backblaze B2, our EU cloud storage provider. Your music files stay local unless you enable backup. Separately — not gated by Cloud Backup — a copy of the app's own working library database (track metadata and full file paths, not your DJ software's own database file) is uploaded after every FIX & ENRICH run so DEBUSSY can answer questions about your library. That copy is also encrypted and stored with Backblaze B2, for every signed-in account.

Anything that travels between the app and our servers goes over HTTPS/TLS — nothing moves in plain text. That covers everything that ever goes over the wire: signing in, small metadata lookups during enrichment, and any cloud backup uploads you choose to start. Your audio and library file aren't part of that — the FIX & ENRICH work runs entirely on your machine.

The things we hold or move, we encrypt: • Cloud backup files (music + library database), if you turn that on — your account's own AES-256-GCM keys, encrypted at rest • The working library database DEBUSSY uses (track metadata and full file paths) — uploaded after every FIX & ENRICH run, held encrypted on our servers and in Backblaze B2 • Everything over the network — HTTPS/TLS • Login sessions — signed tokens What never reaches us at all: your audio files (unless you turn on Cloud Backup) and your app settings. Your DJ software's own database file (Rekordbox/Traktor) is read and modified locally — it's never sent as a file; what's uploaded is the app's own separate working copy, described above.

Your audio files stay put. The fixing and enriching run on your machine — your music files are never uploaded during a run. The things that touch the network: • Signing in • Enrichment lookups — minimal identifiers like artist and title, to find the right artwork, year, genre and label • A copy of the app's own working library database — track metadata and full file paths — uploaded after every FIX & ENRICH run, so DEBUSSY can answer questions about your collection. This happens for every signed-in account, whether or not you use DEBUSSY. • Cloud backup uploads (your actual music files), only if you turn that on Your DJ software's own database file (Rekordbox/Traktor) and your app settings never leave your computer — only the app's own working copy, described above.

No — we don't listen to, analyze, or open up the audio inside your files. Enrichment works purely from metadata, the text fields like artist and title, never the sound itself. And to be completely clear: we do not use your music to train AI models, and we don't touch it for any purpose beyond backing it up and restoring it when you ask. Your music is your music.

OCDJ uses passkeys (the WebAuthn standard) — you sign in with Face ID or fingerprint instead of a password, and passkeys can't be phished the way passwords can. Sessions are protected with signed tokens and login attempts are rate-limited against brute-force guessing. The desktop app connects via a secure one-time pairing step; your credentials then live in your system Keychain, never in a plain text file.

Less than you might expect. On the account side: just your email and login credentials. On the music side: track titles, artists, genres, playlist names and structure, cue points, play history, and the full file path of each track on your computer — held in a working copy of your library database that's uploaded after every FIX & ENRICH run to power DEBUSSY. If you turn on Cloud Backup, we also store the music files themselves (encrypted), plus their hashes and sizes. We never see your app settings or the audio inside your tracks. None of this is ever sold, rented, or shared for marketing.

No — never. We don't sell, rent, or share your personal data with anyone for marketing. We rely on a small number of service providers (cloud storage, payment processing), but they act on our behalf only, under strict data processing agreements, and none of them get your music library for their own use.

Two things happen, and it's worth separating them. When you ask DEBUSSY a question, it sends your message plus results it looks up in your library — things like titles, artists, genres, tags and ratings — to answer you. It never sends your audio files, your email, or your IP address, and full folder paths are shortened to just the file name first. Separately from any question you ask, the app keeps a working copy of your library's metadata (titles, tags, full file paths — never audio) on our servers, refreshed after every FIX & ENRICH run and roughly once a day when you open the app or the chat. That's what DEBUSSY actually queries from — it's not something a single chat message triggers, but it does mean your library isn't purely local once you're signed in, whether or not you use DEBUSSY.

So DEBUSSY can work. It can only answer questions about your music, and carry out tasks on it, if it can see your library — so the app sends us a copy of its library database. That is the only reason we have it. It travels over an encrypted connection, is stored encrypted and locked to your account, and is never sold or used to train AI. Your audio files are never part of it. You can ask us to delete it any time, at [email protected].

In the EU, structurally. Your cloud backup files live with Backblaze B2, in an EU data center. EU residency is enforced at the infrastructure level — not a checkbox that can quietly drift. Data Processing Agreements are in place for GDPR-compliant handling. Any processing that touches a service outside the EEA is covered by Standard Contractual Clauses approved by the European Commission.

Your card details never touch us. Payments run entirely through Stripe — we never see or store your card number, CVV, or bank account details. Your card data goes straight to Stripe's PCI-compliant systems; all we receive is a confirmation the payment went through. Payment records are kept only as long as Dutch tax law requires — 7 years — and only for that purpose.

The strongest option is also the easiest: • Use a passkey — OCDJ supports WebAuthn, so Face ID or fingerprint does the work, and passkeys can't be phished like passwords can • Keep your OS and the app up to date • Treat your pairing code as one-time only — no need to share it • Lost a paired device? Re-pair from another trusted one, or contact support On our side, login attempts are rate-limited so no one can guess their way in.

Your library is walled off from every other account — no other user can reach your files through OCDJ, and file access is locked down at the infrastructure level. Internal access is governed by our Privacy Policy; nobody browses user libraries as a matter of routine. DEBUSSY is built the same way: it can only ever touch the data of the one user asking — never anyone else's.

No — your music and library stay out of crash reports entirely. When something breaks, the report contains only what's needed to fix it: the error trace, your browser or OS type, an anonymized identifier, and the request URL. No music files, no track lists, no library content — by design.

Just enough to look up the right details, and nothing more. For enrichment we send minimal track identifiers — usually artist name and title — so we can fill in missing artwork, years, genres and labels. What we don't send: your library in bulk, your personal data, your account info, or your audio files. Whatever comes back is used only to enrich your own library's metadata and never goes anywhere else.

OCDJ is operated by Plan Bakery B.V., registered in the Netherlands. We're the data controller for your personal data under GDPR. For privacy or security questions, a data access request, or any concern — email [email protected]. We respond within 30 days as GDPR requires. If you feel your data rights weren't respected, you can go directly to the Dutch Data Protection Authority (Autoriteit Persoonsgegevens).

We keep the exact implementation private — spelling it out hands attackers a map. What it means for you: passkey sign-in, secured sessions, rate-limited login attempts, and per-user AES-256 encryption on anything stored in the cloud. The guarantees themselves are in our Privacy Policy. For deeper specifics, [email protected] is the place.

We keep things only as long as there's a reason to: • Account data and library metadata — while your account is active, plus 30 days after a deletion request • Cloud backup files — same schedule • Security logs (IP addresses, login attempts) — 90 days • Payment records — 7 years, required by Dutch tax law • Anonymized analytics — indefinitely, as they hold no personal data When you delete, you really delete — once it's gone, we can't get it back.

Your audio, no — that never leaves your machine, run or no run. What does go out: minimal track identifiers (like artist and title) for enrichment lookups, and — after every FIX & ENRICH run — a copy of the app's own working library database, which does include full file paths (not your DJ software's own database file, and not your audio). If you turn on Cloud Backup, an encrypted copy of your actual music files is also stored in EU data centers — but that's your choice, and it's the only way any audio ever leaves your machine.

Your audio, no — never. When you ask DEBUSSY something, it sends only your message plus track metadata it looks up in your library — genre, tags, ratings — enough to form a useful answer. It never sends audio files, your email, or your IP address, and we do not use your music to train AI models. Separately from asking a question: a copy of your library's own metadata (titles, tags, full file paths — never audio) is kept on our servers so DEBUSSY has something to query, refreshed after every FIX & ENRICH run and roughly daily when you use the app. That happens for every signed-in account, whether or not you use DEBUSSY, and it's a different thing from Cloud Backup, which stores your actual music files and only if you turn that on. This website chat is a guided preview and doesn't reach into a real library at all.

One encrypted copy in the cloud, alongside the copy you keep yourself. Your cloud backup lives with Backblaze B2, in an EU data center. Files are encrypted with your own AES-256-GCM keys before they leave your machine, fingerprinted with SHA-256 so corruption can't pass unnoticed, and synced incrementally so only what actually changed goes up. That copy is independent of your hardware: if your drive dies, is stolen or gets wiped, your library is still there and restorable. It is one off-site copy rather than a mirrored set — so your own drive still matters, and the pre-run snapshots (always local, no internet needed) are what protect you against a bad run.

The short version: we hold as little of your data as the service can run on. Full policy at ocdj.ai/legal/privacy. OCDJ is operated by Plan Bakery B.V. (Netherlands) and built around GDPR. We collect only what's needed: • Your email, for your account • Music library metadata, to clean and enrich your collection • Your music files — only if you opt in to cloud backup We don't sell your data, don't share it for marketing, and don't use your music to train AI models. Your DJ database and music files are processed locally; only the metadata needed for enrichment and sign-in reaches our servers, and any cloud backup is encrypted at rest in an EU data centre. Anything privacy-related: [email protected].

Full Terms at ocdj.ai/legal/terms; in plain English, using OCDJ gives you a personal licence to manage your DJ library. The parts worth knowing: • Cloud backup is a convenience layer on a best-effort basis — keep your own local copies too. • We don't promise exact enrichment results; how much we can fill depends on your existing metadata. • Subscriptions are month-to-month and auto-renew monthly — there's no annual plan; cancel any time and keep access through the period you've paid for. • Refunds: a one-time library job is refundable until it starts processing; a subscription charge is reviewed case by case if you ask within 14 days of it, and there are no prorated refunds. • Dutch law governs the Terms, but EU consumers keep their local statutory rights. Questions about the Terms: [email protected].

No — we don't use your music to train AI models. Your audio stays yours: the FIX & ENRICH work runs locally, and enrichment only ever sends small track identifiers like artist and title, never your audio or personal data. For the full formal wording, the Privacy Policy is the definitive source.

Real and enforceable, not box-ticking — we're operated by Plan Bakery B.V. in the Netherlands, so GDPR fully applies. You can: • Access — a copy of all the personal data we hold • Rectify — correct anything inaccurate • Erase — delete your account and everything tied to it (right to be forgotten) • Restrict — limit how we process your data • Port — receive your data in a machine-readable JSON file • Object — to processing based on our legitimate interests • Withdraw consent — at any time Email [email protected] and we respond within 30 days, as GDPR requires. If you ever feel your rights weren't respected, you can complain directly to the Dutch Data Protection Authority (Autoriteit Persoonsgegevens) at www.autoriteitpersoonsgegevens.nl.

Any time — your data is yours and always portable (GDPR's data portability right, Article 20). The export covers your profile, subscription history, session records, payment history, and the list of files in your cloud backup (the metadata, not the audio itself), as a downloadable JSON file. Get it from your account settings in the app, or email [email protected] and we'll have it to you within 30 days.

Any time — this is your right to erasure under GDPR (Article 17), with no dark patterns in the way. What happens: • A 30-day countdown starts right away and all your active sessions are signed out. • During those 30 days you can change your mind and cancel the deletion. • After 30 days, your account data, your cloud backup files, and all associated metadata are removed from our servers. • Payment records stay for 7 years — a Dutch tax-law obligation, not our choice. • Once it's done, it's irreversible; we can't recover your data afterward. Start it in your account settings, or email [email protected].

There's a real company behind this. OCDJ is a brand operated by Plan Bakery B.V., registered in the Netherlands — which means we fall under EU law, including GDPR, so your data rights are genuinely enforceable rather than just words on a page. For privacy questions: [email protected]. For legal or Terms questions: [email protected]. And the website is ocdj.ai.

The honest version, straight from our Terms: cloud backup is a convenience layer on a best-effort basis, not a guaranteed primary backup — keep your own local copies at all times. Cloud is the extra safety net, not a replacement for your local storage. If something does go wrong, our liability is capped at the greater of what you paid us over the prior 12 months or EUR 50. Your files sit on third-party EU cloud infrastructure, so an outage or loss originating with that provider is outside our direct control, though we have a Data Processing Agreement with them. The practical takeaway: keep local backups, and treat cloud as the second line, not the first.

Only the cookies the site genuinely needs, plus optional analytics you control: • Essential (always on) — a session cookie to keep you logged in and a CSRF token to block cross-site attacks. The service relies on them, so they can't be switched off. • Analytics (optional) — only with your consent, to see how visitors use the site so we can improve it. Your first visit shows a consent banner where you pick "Accept All" or "Essential Only," and you can change your mind any time by clearing local storage for our domain. What we don't do: advertising cookies, ad networks, or selling analytics data.

We're upfront about the whole stack — our Privacy Policy at ocdj.ai/legal/privacy names every third-party service that touches your data. By category: • Cloud backup storage (EU Central) • Application hosting • Payment processing • Website analytics (optional, consent-gated) • Product analytics and session replay (optional, consent-gated) • Transactional email • Error monitoring (no music files in error reports) • AI assistance for certain features (non-identifying track metadata only, never audio) • CDN for artwork and app assets • Live chat support Each is a data processor working strictly on our behalf under a data processing agreement — none of them gets your library for their own use.

OCDJ is built for DJs 16 and over — it isn't aimed at children under 16, and we don't knowingly collect personal data from them. If you think a child has given us their data, email [email protected] and we'll delete it promptly.

Two different things — and that's the good news: cancelling your subscription doesn't wipe your data. You keep your paid features through the end of the period you've already paid for, and your data stays on our servers for as long as your account exists. Nothing is deleted just because you stopped paying. If you also want your data gone, that's a separate step — request account deletion, and everything is removed within 30 days.

Refunds follow our Terms (section 5): • One-time library jobs: fully refunded if you email [email protected] before the job starts processing. Once processing has begun the fee is non-refundable, unless we made a material error in processing (tell us within 14 days of the job finishing). • Subscriptions: cancel any time and you keep access until the end of the period you've paid for; there's no prorated refund for the rest of it. A refund request for a charge is reviewed case by case if you send it within 14 days of that charge. It's generally not available once the subscription has been actively used for more than 14 days of that period, or once data has been uploaded under a Cloud Backup plan during it. • If a significant, documented outage or defect stopped you using the service, tell us within 14 days and we'll look at a prorated credit or refund. To ask, email [email protected] with your account email, the date and amount of the charge, and the reason. We aim to reply within 5 business days, and approved refunds reach your original payment method within 5–10 business days.

The honest inventory, straight from our Privacy Policy: • Account data — your email, login credentials, session identifiers, and IP addresses (kept for security, 90 days) • Music library metadata — track titles, artists, genres, playlist names and structure, cue points and DJ settings, and relative file paths • Cloud backup data — only if you use it — your music files, their integrity hashes, sizes, and upload timestamps • Payment records — transaction records via our payment processor (no card details on our side) Want to see it all in one place? Use the data export and it comes back as a single JSON file.

Dutch law governs our Terms, and disputes fall under the courts of the Netherlands. But here's the part that matters if you're an EU consumer: that choice of law doesn't strip away the mandatory consumer protections of your own home country. So whether you're in Germany, France, or anywhere else in the EU, your local consumer rights still hold.

Pairing links the OCDJ desktop app on your computer to your account. When you first launch, it walks you through a short flow: sign in on the website, a pairing code is generated, and the app picks it up automatically. Once paired, your session stays active indefinitely — no monthly re-login. You only need to pair again if you install on a new computer or explicitly unpair the device.

Yes — you can pair OCDJ to up to 2 devices on the same account. Each device goes through its own pairing step, and once paired it stays connected. Processing happens locally on each device, so each one works with the music library you have on it. If you use both Rekordbox and Traktor, one subscription covers a Rekordbox library and a Traktor library at the same time. One rule to know: a second library on the same platform (e.g. two separate Rekordbox libraries) isn't possible on one subscription for now — that may be released in the future.

Getting set up on a new machine is straightforward: • Install OCDJ and go through the pairing flow — it connects the new computer to your existing account. Your subscription carries over. • Your music library and run history live locally on your old machine — move your music files across (external drive or cloud storage) and point OCDJ at them on the new machine. If you're on the BASE or PRO package, your backup history is already in the cloud and accessible right away after re-pairing.

No stress. OCDJ uses email-based sign in — there's no password to forget. If you've lost access, head to the sign-in page on ocdj.ai and enter your email address. A short-lived code gets sent to your inbox, you enter it, and you're back in. From there you can re-pair any device. If you're not receiving the sign-in email, check your spam folder — or reach out and our team can help you sort it out.

Once paired, your session is designed to stay active as long as the app is installed — we don't time out devices on purpose. If the app is asking you to re-pair, something interrupted the connection: a reinstall, a device change, or a rare auth issue. The fix is quick — go through the pairing flow again: sign in on ocdj.ai, grab the code, and you're reconnected. Your library, settings, and backup history are all still there.

The iOS mobile app is on the roadmap for winter 2026. When it lands, mobile play-counts will stay separate from your DJ software's play history — playing a track on your phone won't write back to your DJ software's database. The mobile app is designed as a companion for browsing and tagging on the go, not a playback source that feeds your DJ library stats.

The iOS mobile app is on the roadmap for winter 2026. When it ships, changes you make on your phone — tags, ratings, organization moves — will sync back to the desktop automatically the next time your computer comes online. The desktop is always the primary source of truth: OCDJ processes and enriches your library there, and the mobile app reflects the result. Mobile play-counts won't write back to your DJ software's play history.

Uninstalling doesn't touch your account — your account and subscription stay intact. Reinstall and pair again and everything picks back up. Local library snapshots and settings live on your machine, so reinstalling on the same computer leaves them in place. If you're on the BASE or PRO package, that backup history is in the cloud and accessible immediately after re-pairing on any machine.

Pairing ties the OCDJ desktop app on your specific computer to your account — a one-time step that replaces a traditional username-and-password login. A short-lived code, entered once, establishes a device-specific connection. After that, your device has its own secure identity and your session stays active indefinitely. No password to forget, no monthly re-logins.

Sign-in codes expire after a few minutes by design. Just request a new one: go back to the sign-in page, enter your email, and a fresh code is sent to your inbox. Each new request generates a new code and automatically invalidates the old one. If you're mid-way through the pairing flow in the app, restart it and it will prompt for a new code.

A few things to check: • Spam or junk folder — transactional emails sometimes land there. • Exact email address — a typo sends the code to a different inbox. • Rate limit — if you've requested several codes quickly, wait a few minutes and try again. If none of that helps, our team can check what's happening on the account side.

Device revocation — the ability to remotely disconnect a specific paired computer from your account — is something we want to support properly. It's not available as a self-serve option in the current version, but our team can handle it manually if you need a device removed (for example, if you sold a computer or lost access to it). Just reach out and we'll sort it.

A few layers work together: • Sign-in uses short-lived one-time codes sent to your email — no reusable password to steal; codes expire quickly and can only be used once. • After pairing, your device gets its own secure connection, not a shared session. • Repeated failed attempts trigger a temporary lockout. • Your music processing and library data stay on your local machine — nothing leaves your computer unless you explicitly enable cloud backups.

Changing the email address on your account isn't something you can do from within the app right now — but our team can update it for you. Just reach out with your current email and the new address you'd like to use. Once it's updated, you'll receive sign-in codes at the new address.

The mechanism stays under wraps — but what you get from it is a session that stays active as long as the app is installed, with no passwords to manage and no forced re-logins. The short version: each device gets its own secure identity established at pairing time, and it stays valid until you remove the app or revoke the device. Want to know how to pair a new device, or have a specific security concern?

It's single-user today — one account tied to one person, though that account can be paired on up to 2 devices at once, and one subscription covers a Rekordbox library and a Traktor library at the same time. A second library on the same platform isn't possible on one subscription for now — that may be released in the future. There's no separate multi-person account type with its own logins or permissions. If you and someone else genuinely need to work off the same account, you'd be sharing the same sign-in rather than getting individual profiles — workable, but not purpose-built for it. A proper multi-user account type — separate logins, individual permissions, two people in one library at once — isn't something we're building. OCDJ is a single-user tool by design, and that's not changing.

OCDJ reads your Rekordbox library directly — your whole collection, including track metadata, playlists, playlist folders, ratings, and your track tags, is right there, no exporting needed. And it never modifies your original library. It builds a clean version alongside it, so your working Rekordbox library stays untouched the entire time. It sits on top of Rekordbox as a companion, not a replacement.

Your playlists stay exactly as you built them — folders, sub-folders, and track order all preserved. OCDJ never deletes, merges, or reorganizes your existing playlists. It only updates track metadata, and only the changes you approve. Your Rekordbox My Tags are safe too: a FIX & ENRICH run never alters them. For Traktor users — Traktor has no native tagging of this kind, so OCDJ fills that gap, bringing the same tag-and-comment organization to your Traktor library.

OCDJ reads your Traktor library directly — no exporting or importing needed. Same as with Rekordbox, it never modifies your original; it builds a fixed and enriched version alongside it. One extra for Traktor users: where Rekordbox has My Tags and Traktor has nothing of the kind, OCDJ fills that gap — bringing the same tag-and-comment organization to your Traktor library. Smart playlists you build through DEBUSSY can be exported straight back into Traktor.

Exporting a Traktor library to a CDJ-ready USB stick isn't something OCDJ does today — that workflow is deliberately out of scope for the current version. Where OCDJ earns its keep is everything that happens before the export: fixing, enriching, and organizing your Traktor library. So when you do prepare that USB with your existing tools, the data going onto it is already accurate and complete — clean genres, filled artwork, no duplicates.

OCDJ FIXES & ENRICHES metadata fields like genre, artist name, title, year, and comment — and leaves your beatgrids, cue points, and existing analysis completely alone. Your Rekordbox My Tags are safe too: a run never alters them. A scan shows you, by category, what will change before any run, and a snapshot is taken first so everything is reversible. Your curation stays yours at every step.

Two different things, and neither is something OCDJ does today. Continuous sync (Rekordbox → Traktor) — keeping your metadata mirrored one-way so tags, comments and genres stay in step — is planned for a future release, not available yet. A one-time full conversion that migrates your whole library (playlists, cue points, structure) between platforms is on the roadmap too, not built yet — one of the most-requested items. What OCDJ does today is read each library directly and run FIX & ENRICH on it, no export or import. If a cross-platform sync or migration matters to you, tell me and I'll flag it.

OCDJ and Mixed In Key work hand in hand. If you've already analyzed your library with Mixed In Key, we respect that work and build on top of it — your existing notation and energy data won't be overwritten. The two are complementary, not competing. You keep what Mixed In Key gave you, and OCDJ handles the fixing and enrichment around it.

Rekordbox 6 and 7 are supported. If you're on an older version, reach out to our team and we'll help you figure out the best path forward.

Traktor Pro 3 and 4 are supported. If you're on an older version, reach out to our team and we'll help you figure out the best path forward.

OCDJ won't break your CDJ workflow: it updates metadata fields but never touches the ANLZ files (the waveform, beatgrid and cue data Pioneer CDJs read from USB), so your beatgrids and cue points stay exactly as they are. The export to USB still happens in Rekordbox — that step is outside OCDJ. What OCDJ does is make sure everything going onto that stick is already in great shape: accurate metadata, correct genres, no duplicates, high-res artwork. A dedicated USB export is on the roadmap for a future release.

No exporting or importing — none of that friction. OCDJ reads your Traktor or Rekordbox library directly from where it already lives on your computer. You connect your library once during setup, and everything's available straight away. No intermediary files, no conversion step, no copying things around. It just reads what's already there.

Yes — smart playlists you build through DEBUSSY export straight into Rekordbox or Traktor. They're waiting for you, ready to play, the next time you open your DJ software — no manual export or import step.

Not yet — keeping your Rekordbox and Traktor metadata in step (Library Sync) is planned for a future release, not available today. The idea: you work in Rekordbox as your primary, and your changes — tags, comments, genres — mirror one-way into Traktor so the two stay aligned without a manual export. It isn't built yet. What works now: OCDJ reads each library directly and runs FIX & ENRICH on it, and for Traktor users it fills the tag-and-comment gap Traktor leaves. If RB→Traktor sync matters to your workflow, tell me and I'll flag it.

Different tool, different job. OCDJ works with DJ software libraries — Rekordbox and Traktor — fixing, tagging, and organizing the tracks you play out. Ableton Live, Logic Pro and FL Studio are production DAWs built around projects and sessions, not a track library in the same shape, and there's no integration with them today. If you're a producer who also DJs off Rekordbox or Traktor, OCDJ still has your DJ-facing library covered — that part doesn't change. Production-tool support isn't on the roadmap right now, but tell me if it matters to your workflow and I'll make sure it's noted.

Your library is never modified until a run finishes cleanly, so a stall can't cost you anything. If the Progress screen hasn't moved in a few minutes, check these first: • DJ software open? OCDJ needs sole access to your library file — close it and the run picks back up. • Mac went to sleep? Keep it awake while the run is active (System Settings → Battery / Energy Saver). • Very first run on a big library? Give it more time — it slows down on large external drives. If it's genuinely frozen, quit and reopen — an interrupted run resumes safely, and nothing in your library has changed.

A run that finishes with nothing changed is usually a good sign. The most common reasons: • Settings not finished — OCDJ never applies changes without your explicit choices. Open Settings and check each stage. • Your library already matches your chosen rules — nothing to fix. • Tracks it couldn't identify with confidence are left alone and flagged in the results. • It ran against an older library copy — check the track count and timestamp on the Progress screen.

Every OCDJ error includes a plain description plus a short code — the code is for our team, so you don't have to decode it. Most errors clear on a second try. Common causes: • DJ software open during a run — close it and retry. • Slow or disconnected external drive. • Brief internet drop (some steps need a connection). Note the code, close and reopen the app, and try again. If the same error survives two retries, share the code with our team — they'll know exactly where to look. Either way, your library is untouched until a run completes cleanly.

OCDJ keeps itself current in the background and prompts you at next launch when a new version is ready. To check by hand: app menu (top-left, OCDJ) → 'Check for Updates'. It'll confirm you're up to date or let you install the new version on the spot — no reinstalling from scratch. Updates never touch your library, settings, or backup history.

Heavy CPU during a run is expected — all processing happens locally on your Mac so your files never leave your machine, and that real work uses real CPU. The first run is the most intensive; every run after that is faster because it only touches what's new or changed. A few things that help: • Run it while you're not doing other heavy work. • Keep the Mac off aggressive low-power mode on battery. The moment a run finishes, usage drops to near nothing.

Yes — close your DJ software before starting a run. OCDJ reads your DJ software's library file directly, and if both apps have it open, only one can hold it — you'll get a 'file in use' error. Safe order: 1. Close your DJ software. 2. Start the OCDJ run. 3. Reopen your DJ software once the run finishes. This applies to any tool that reads or writes these library files — your DJ software's own export features work the same way.

Not every track gets enriched — we'd rather leave a field blank than fill it with something wrong. A track stays untouched when: • It's an obscure cut, white-label, or bootleg we can't identify with confidence. • Its core tags are so garbled that a fix pass first would help — correcting artist and title usually improves matching. • It's a live set, DJ mix, or stem, which we deliberately separate out. Anything we can't be sure about, we leave exactly as it was.

A greyed-out Start button means something still needs your input — the app won't run on guesswork. Usually it's one of these: • Settings not finished — an incomplete settings step locks Start. Open Settings and look for anything unfinished. • No library found — if the drive your library lives on isn't plugged in, there's nothing to run against. • Subscription or credits needed — check your account balance in the app. • A previous run is still wrapping up — check the Progress screen. The Progress or Settings screen usually spells out exactly what's missing.

A few quick checks usually sort a launch failure: • macOS only — it's a Mac app today (Windows is on the roadmap). • 'Unidentified developer' warning? The app is notarized by Apple — go to System Settings → Privacy & Security → 'Open Anyway'. • Re-download the latest version from ocdj.ai — a partial download is the most common cause. • Restart your Mac and try once more. If it opens and immediately closes with a message, note what it says — that's exactly what our team needs.

OCDJ looks for your library in the standard location your DJ software uses. If it can't find it: • Library on an external drive that isn't plugged in — connect it and relaunch. • File moved somewhere non-standard — point OCDJ at it in Settings → Library Path. • DJ software has never run on this Mac — open it first to create the library, then relaunch OCDJ. Once the path is right, it reads your library directly — no import, no export needed.

No — cue points, hot cues, beatgrids, waveforms, loops, and existing analysis are completely off-limits. OCDJ only changes text fields: genre, artist, title, comment, year, label, artwork. If cues look missing after a run, your DJ software is likely still showing the cached pre-run library. Fully close and reopen it — your cues are almost always right there. And if anything does look off, a full snapshot is taken before every run — your whole library can be returned to exactly how it was beforehand.

The FIX & ENRICH stage runs entirely on your machine — a network blip never affects it. Only enrichment lookups (artwork, years, genres, labels) need a connection. What to do: 1. Make sure your connection is steady. 2. On a VPN? Try switching it off — some configurations get in the way. 3. Restart the run — anything already done is skipped, so it picks up where it left off. Tracks that couldn't finish are flagged in the results, never silently dropped.

Don't panic — your original library is always safe. OCDJ takes a full snapshot before every run. 1. First, fully close and reopen your DJ software — it's often still showing a cached version of the old library. 2. If it still looks off, restore: open OCDJ, find the pre-run snapshot in your version history, and restore it. 3. That puts your original back exactly as it was — cues, playlists, track data, all of it. Once restored, you can re-run with different settings or reach out for help.

That code points our support team straight at what happened — you don't need to decode it yourself. What matters on your end: can the run be retried? If yes, try once more. If the same error comes back, escalate — send our team the full message including the code and they'll know exactly where to look.

The first run is the long one — every track is processed from scratch. After that it's faster, because only new or changed tracks get re-done. How long depends on library size, your Mac, your connection, and whether music sits on a fast internal drive or a slower external one. The Progress screen shows tracks done and tracks left in real time. Best move: leave the app open and let it run.

OCDJ is built to work with Mixed In Key data, not step on it. Settings let you mark any field as 'preserve' so it's never touched — that's the move if you rely on MIK's Camelot notation or energy markers. If your MIK data changed, it's almost always because the field it lived in was being fixed for another reason and 'preserve' wasn't set for it. Want it back? The pre-run snapshot has your original data intact — restore it and your whole library returns to exactly how it was.

OCDJ backs up in two layers: • Pre-run snapshots — taken automatically before every run, always local, no internet needed. These keep working regardless. • Cloud backup — a background sync to triple-redundant storage after your run. If it's stalled, common causes are an internet drop, a subscription status change, or your external drive being disconnected. To see where things stand: open the app → Backup screen. It shows your last successful backup, current sync state, and any error with a plain description.

A few things to try: • No reply? Close and reopen the DEBUSSY chat panel and ask again. • Says it doesn't know something about your library? That usually means the data isn't loaded yet — ask again after your next run finishes. • An answer looks wrong? DEBUSSY reads your actual library, so if a number seems off, check that field directly — it's reading what's really there. DEBUSSY is built to be honest about what it doesn't know. An 'I'm not sure' is it telling you the truth instead of guessing.

That's usually a symptom of the underlying mess, not your memory — and it's fixable. When artist names are inconsistent, genres scattered, years and labels missing, and duplicates clutter the list, search and browse stop working. OCDJ repairs all of that so the fields you browse by are clean and complete: one consistent name per artist, filled-in genres and years, duplicates removed, everything filed. Once the data underneath is in order, finding the right track — even reaching for it mid-set — gets fast and reliable again.

That one lives inside your DJ software — this demo's home turf is the library care side: fixing tags, finding duplicates, protecting playlists, backing it all up. The full desktop DEBUSSY (subscription) has the Rekordbox and Traktor manuals in its knowledge base and answers exactly these how-to questions with your actual library in front of it. For right-now help, the official docs cover this well.

Day-to-day tagging mechanics — keyboard shortcuts, batch-tagging, CDJ behavior, Traktor's comment and tag columns — live inside your DJ software. Pioneer's and Native Instruments' docs are the right walkthrough for those details. Where OCDJ enters the tag story: it fixes and enriches your library's tags, and for Traktor users fills the tagging gap Traktor has always had. The desktop DEBUSSY (subscription) has the Rekordbox and Traktor manuals in its knowledge base and answers exactly these how-to questions with your library in front of it.

Beat FX, effect chains, pad modes — that's the performance side of your DJ software, and I'll be straight: it's outside what this demo covers. Pioneer's and Native Instruments' own docs are the right teachers for the performance layer. My world is the library underneath: clean tags, correct artist names, no duplicates, playlists that hold together, a backup so none of it can be lost. The desktop DEBUSSY (subscription) also answers Rekordbox and Traktor manual questions with your library in front of it.

The USB export flow belongs to Rekordbox — the device-format details and export steps are theirs, and the Rekordbox manual is the reliable walkthrough. I won't improvise CDJ instructions; a wrong step there ruins a gig night. Two things I can add: USB and Engine DJ export for CDJs are on OCDJ's roadmap — coming, not here yet. And what's true today: a fixed and enriched library exports better. Broken tags, duplicates, and blank fields follow you onto the stick.

The half-tempo / double-tempo issue is your DJ software's analyzer making a judgment call. The fix lives inside Rekordbox or Traktor: set a sensible BPM range in the analysis settings and re-analyze the affected tracks. Their docs cover the exact steps for your version. That's genuinely their department — audio analysis belongs to your DJ software. Where I come in is everything around it: tags, duplicates, playlists, and the backup that means a re-analysis mistake never costs you your library.

Cue and loop mechanics — hot cue vs memory cue behavior, what survives a re-analysis, loop saving — live inside your DJ software. The honest move is to point you at the Rekordbox or Traktor docs rather than guess at version-specific behavior. From my side: when OCDJ FIXES & ENRICHES a library, your cue points are off-limits — it works on a copy, never edits your original database in place. Hours of cue prep are exactly what the backup side exists to protect.

Cloud Library Sync is Rekordbox's own feature for mirroring one library across devices — Pioneer's docs are the right place for setup and errors with it. Worth knowing: OCDJ deliberately doesn't do sync. What it builds is cloud backup — point-in-time snapshots, including one before every change it makes. Sync propagates the current state (including a mistake) everywhere; a backup remembers the state before the mistake. Different tools for different fears.

That's Pioneer's pricing, and the honest answer is to check rekordbox.com — plan contents shift over time, and you deserve current numbers rather than my stale ones. Same for Traktor: Native Instruments' site has the real terms. Ours I can answer precisely: OCDJ's plans are on the pricing page, and you can ask me right here what anything costs.

Right here, I'm your guide to OCDJ. Ask anything — what FIX & ENRICH, Backup, and DEBUSSY do, what it costs, whether it's safe for your library — and I'll give you a straight answer. This page is a preview; the full DEBUSSY that reorganizes playlists and fixes your tags lives inside the app on a subscription. Want to see what OCDJ would actually find in your own collection? If I ever don't have an answer, I'll connect you with our team.

Think of me as someone who's memorized your entire collection. Ask about your own library — "how many five-star techno tracks have no genre?" — and I answer in seconds, from your real data. With a subscription I also do the work: build smart playlists from a plain sentence, fix tags across your whole collection, do comment surgery at scale, and playlist surgery — merge playlists, renumber broken sequences, dissolve subfolder hierarchies, surface the gems you forgot you had. And rules your DJ software can't express — "everything that's NOT House," sixteen-plus conditions, mixed AND/OR logic — I can, and those playlists keep updating themselves as new tracks land. Every change shows you an exact preview first, and anything I do, you can undo.

A few honest limits — most are there to protect you: • I only work with your own data — never another user's library. • Nothing changes without your explicit yes and a preview first. That's a feature, not a limitation. • I won't explain how we built the product under the hood. • I won't invent features that don't exist — if something isn't built yet, I'll say so. For billing disputes or account issues beyond my reach, I'll hand you to human support.

I tell you honestly. I never guess or make things up — if I don't have a grounded answer, I'd much rather say so than hand you something wrong. • If it's a feature you'd like to see, I'll note it so it isn't lost. • If it needs a human — billing, account issues, anything sensitive — I'll connect you to our support team directly. You'll always know exactly where you stand with me.

Of course — a real person is one click away. Use the chat widget in the bottom-right corner of the app or website to reach our team directly. Want me to put you in touch right now?

I'm built for one thing and built for it well: your music collection and everything OCDJ can do for it — library questions, playlist building, tag fixes, backup status, all of it. Ask me to write code or do your taxes and I'll be straight with you: I'm not the right tool, and I won't fake it. Anything music-related I can dig into for you?

Nice try, but no — my guidelines exist for a reason and I don't step around them. I'm here for your music collection and OCDJ, and that's exactly where I stay. Anything I can actually help you with on that front?

I only ever touch your data — and that's a hard wall, not a soft policy. Another DJ's collection is theirs alone: I can't see it, compare to it, or share it. Your music is yours; everyone else's is theirs. That cuts both ways.

Yes — I won't fire off a big batch job without making clear what's about to happen. If a request could balloon, I'll scope it with you first. Most requests cost very little: a quick question, a library lookup, building a playlist from rules — your credits stretch a long way. The few things that use more are big jobs over thousands of tracks; those I'll scope and confirm before a single thing runs. The same approval gate that protects your library protects your credit balance: you see what's coming and say yes first.

I work from your library itself — your track list, your tags (titles, artists, genres, labels, artwork), your playlists, and signals like play counts and ratings where you have them. That's exactly why I can answer real questions about your collection and run targeted fixes, instead of guessing. And I only ever see your own library — never anyone else's.

Nothing changes without your explicit yes — that's a core design principle, not a setting you have to find. Every batch action shows you a preview first: here's exactly what will change, here's what won't. Approve and it runs; reject and nothing happens. And even after you've approved, any action can be undone. I will never quietly change your library. That's the whole point.

Please do — feature requests genuinely shape what we build next. If there's something you need that I can't do yet, tell me what you're after and I'll make sure it's captured. Nothing gets invented to paper over a gap, but nothing gets lost either. Got something in mind? Tell me and it goes on the list.

That part's our secret sauce — and you never need to know how it works to get the benefit. You get a fixed, enriched library; the engineering is ours to worry about, the results are yours to enjoy. Want to see what it would actually fix in your collection?

Fair question. What you're using right now is the public demo — a curated preview of what DEBUSSY is like. The full DEBUSSY — live access to your own library, batch actions, answers driven by your actual collection — lives inside the OCDJ desktop app on a subscription. Think of this as a test drive: a real feel for the conversations you'll have once DEBUSSY is working on your library.

I'll keep answering you graciously — but my answer won't change. The line doesn't move. One curious question never gets you in any trouble; systematically trying to pry out our engineering is a different story, and we do review sessions. Now, happy to actually help with your music — what do you need?

Restore happens inside OCDJ, the desktop app — this site is just a preview, so it can't touch a real library here. In the app it's simple: ask DEBUSSY to restore and it brings your library back. OCDJ snapshots your library before every FIX & ENRICH run and keeps a version history, so there's always a precise point to return to. Two paths, and DEBUSSY tells them apart from what you ask — roll back to a saved snapshot, or pull your whole library (database and music files) back from a cloud backup if you're on a new machine or lost everything. Right after a run, paid tiers also get a one-click ↶ Revert.

Yes — with a DEBUSSY subscription, I can express playlist rules your DJ software can't on its own. Want everything that's NOT house? I can exclude by partial match like that — the native builders can't. And you can combine genre, BPM, rating, and how recently a track was added all at once, just by describing it in a plain sentence instead of building it rule by rule. That's the everyday win.

Fair to ask. Every answer comes straight from your real library — your tracks, tags, playlists, and ratings — so "how many five-star techno tracks have no genre?" gets a real number, not a vibe. When it comes to changing anything, nothing is left to chance: every action shows you an exact preview, you approve it, and anything that runs can be undone. Not a black box — grounded in your data, with a safety net on every move. The test: does it save you hours of tagging and crate-digging?

A general chatbot has never seen your library and can't do anything to it. DEBUSSY is built for yours. Ask a chatbot "how should I organize my techno?" and you get sensible general advice. Ask me, and I answer from your actual collection — your tracks, tags, playlists, and ratings — so "how many five-star techno tracks have no genre?" comes back as a real number, and I can go fix them. A chatbot can't change a single tag; the best it can do is tell you what to do by hand. When I do change something, you see an exact preview, approve it, and can undo anything. Grounded in your music, plugged into your DJ software, with a safety net on every move.

No — and the difference is the whole point. A general chatbot dressed up for music still knows nothing about your library and couldn't touch it. DEBUSSY is the opposite: the product isn't the chat, it's everything behind it. It reads your real DJ software collection, works from a full picture of your tracks, playlists, keys and ratings, and can take safe, reversible action — build a playlist, fix tags across the whole library, sort your comments. A chatbot talks. DEBUSSY knows your collection and does the work — every change previewed first, and undoable.

A chatbot can give you reasonable advice, but it can't see your library and it can't touch it. It can't open your DJ software, doesn't know which tracks are missing artwork or have broken tags, and can't fix a single one. At best it writes you a to-do list you then work through by hand. DEBUSSY does the job. It works from your real collection, runs fixes across your whole library in one pass, and shows you an exact preview before changing anything — with a full undo if you don't like the result.

A chatbot can write you a script — but it's brand-new code, never run against a real DJ library, pointing straight at your cues, beatgrids, and database, where one wrong line is unrecoverable. OCDJ doesn't improvise. It runs the same proven steps every time — built carefully and covered by hundreds of tests before they ever touch your music. Before anything changes it takes a full backup, works on a copy, checks the result, then swaps it in. And you can undo the whole thing in one move. It never touches your cues, beatgrids, or the file links your DJ software depends on. The AI is just the easy way in: it understands what you're asking, picks the right tested tool, and shows you an exact preview first. It chooses from a fixed set of safe operations — it never improvises code that touches your files. The convenience of asking, with the safety of an engine built for exactly this.

AI is the part that lets you talk to your library in plain language — you say what you want and it works out what you mean and how to do it on your collection. But most of the heavy lifting is solid, predictable engineering: tag repair, duplicate detection, artwork and metadata fill, backups, and safety checks all run by precise rules. The AI understands your request and hands off to those reliable tools, always showing you an exact preview before anything changes. The ease of just asking, with the predictability of a proper engine underneath.

It can't — and it comes down to three things a general chatbot doesn't have: access, action, and a safety net. No access to your library — it can't read your DJ software, so it doesn't know your tracks, playlists, keys, or ratings. No action — it can't re-tag a track, build a self-updating playlist, or fix a broken link; it can only describe what you should do. No safety net — no exact preview, no snapshot before changes, no undo. DEBUSSY has all three: it knows your collection, does the work, and every move is previewed and reversible. The difference between advice and a finished library.

Most AI tools are general assistants that talk about things. DEBUSSY is a specialist that works on one thing — your DJ library — and does it properly. Two things set it apart: it's grounded in your real collection, so answers are facts from your tracks, not guesses. And it acts safely on them — build playlists with rules your DJ software can't express, fix tags across the whole library, teach it a standing preference once and it applies forever — every change previewed, snapshotted, and undoable. It won't write your emails. But for keeping a DJ library clean, organized, and gig-ready, there's nothing generic about it.

Two honest answers, depending on which DEBUSSY you mean. Right here — the public demo — I don't carry memory between visits. Each session starts fresh. The full DEBUSSY inside the desktop app is different in the way that actually matters: it remembers your standing rules and preferences. Tell it once — "always capitalize my genres," "never touch my ratings" — and that sticks on every future run, automatically. The memory that counts isn't a transcript of past chats; it's DEBUSSY learning how you like your library kept and doing it that way, without you re-explaining.

Yes — this is the core of what DEBUSSY does. Ask a plain question and you get a real answer from your actual library, not a guess. "How many five-star techno tracks have no genre?" "Which artists have more than 20 tracks?" "What did I play at my last gig?" — answered in seconds, straight from your DJ software database. No query language needed. Just ask as you'd ask someone who'd memorized your entire library.

Yes — long-running tasks post their results into the conversation when they're done, so you can keep asking other questions while the work runs. You don't need to wait and watch. DEBUSSY lets you know in-chat when the job is complete.

Yes — if your request doesn't match a built-in tool, DEBUSSY can write a Python script for it and run it on your library under your credit budget. The script runs in a sandboxed, network-isolated environment — it can't reach the internet or touch anything outside your library. Like any other DEBUSSY action, you approve it before anything runs and the full undo safety net applies. Most everyday requests go through the standard tested tools; this is for genuinely custom needs.

Just ask. Inside the desktop app, you can ask DEBUSSY directly — "what's my credit balance?" — and it looks it up and tells you. No need to leave the chat or hunt through account settings. For plan details, top-up options, and current pricing, the pricing page has the current numbers.

Right from the chat. Say you need help and DEBUSSY will connect you directly to the team — no need to leave the app, find an email address, or open a separate support window. You can also use the chat widget in the bottom-right corner of the website at any time.

Yes — every track gets one canonical, reliable key during the FIX & ENRICH run. OCDJ works through a priority ladder: it uses the key your DJ software already analysed (preserved, never overwritten), then fills gaps from catalog data. The result lands in Camelot notation in the key field your DJ software reads natively. Tracks without any key get one. Tracks that already have a key are left exactly as they are. No analysis software required — it happens as part of the normal run.

Yes — inside the desktop app DEBUSSY reads your play history straight from your DJ software and answers plain-language questions about it. "What did I play at my last gig?" "Which of my techno tracks have I never played?" "What are my 20 most-played tracks this year?" — real answers from your data, in seconds. Play counts, last-played dates, and per-track totals are all fair game. Just ask as you would ask a person who knew your library inside out.

Yes — track count, genre breakdown, BPM range, top artists, how much of your library has artwork, how much is missing year or genre — these come back instantly with no credit cost. Stats queries run straight from your local library cache without any LLM call, so they're free and fast no matter how big your collection is. Just ask naturally: "How many tracks are in my library?" "Which artists have the most tracks?" — each comes back in under a second.

Not yet. Turning your play history into a shareable tracklist — CSV for spreadsheets or promoters, M3U for other tools, or plain text for a caption — is built but switched off until the sharing features are finished, so DEBUSSY can't export one today. What works now: ask "what did I play at my last gig?" and DEBUSSY lists it from your DJ software's play history, right in the chat.

Yes — tell DEBUSSY once and it follows the rule on every future run without you repeating yourself. "Always keep my genre field capitalized but never touch my ratings." "Don't move files in my Techno folder." "When you see a remix, put the remixer in parentheses." — set it, it applies forever. Standing rules live in your profile, so they survive restarts and updates. The difference between an assistant you have to brief every session and one that already knows how you work.

Yes. DEBUSSY can reorder a playlist into a harmonic (Camelot-wheel) sequence or an energy progression using the key, BPM, and energy data already on your tracks — so adjacent tracks mix in key and the energy builds the way you want.

Two different things here, and they're at different stages. Sorting a set is live: DEBUSSY can reorder a playlist into a harmonic (Camelot-wheel) sequence or an energy progression using the key, BPM, and energy already on your tracks. Finding tracks that are similar to a given song — surfacing other tracks from your library that match its feel — is still on the way, not available yet. So today you can ask me to order your set by key or energy, and — with a DEBUSSY subscription — to build a smart playlist from a plain-English brief — "uplifting progressive house between 128 and 132 BPM" — and write it to Rekordbox or Traktor once you approve it. Find-similar will extend that once it ships.

Yes, for specific changes. On a paid plan you can ask DEBUSSY to undo just part of a run — say, the genre changes from last week, or particular tracks, fields or playlists — on Rekordbox or Traktor. It shows you exactly what it will revert as an approval card, and nothing is touched until you approve. That's different from a whole-library snapshot restore, which rolls everything back at once. What isn't live yet is the automatic risk breakdown, where DEBUSSY would sort every change into low-risk fixes and riskier edits so you could undo only the safe ones in one move. That's on the roadmap.

Yes — DEBUSSY can revert a specific action it took, right from the chat. It goes through the same approval card as everything else: DEBUSSY shows what it's about to undo, you confirm, and it's reversed. This covers DEBUSSY-initiated operations — a smart playlist it built, a tag batch it ran, a script it executed — because every DEBUSSY action that writes to your library drops a revert anchor first. Not sure which one? Ask DEBUSSY to list your recent operations.

DEBUSSY builds the playlist in two steps. First it generates the track list and shows you a preview — you see exactly what would be added before anything is written. Then it presents a CONFIRM card; only after you confirm does it write the playlist into your DJ software. Describe what you want, review what it found, decide whether it's right. If the first result isn't right, tell DEBUSSY to adjust the rules and it'll rebuild.

Syncing cue points between Rekordbox and Traktor isn't something OCDJ does today — cue data is high-stakes, and we won't move it until it's provably safe. Keeping metadata in step between the two (Library Sync) is planned for a future release too, not live yet. If either matters to your workflow, tell me and I'll flag it — user signal genuinely shapes what ships next.

Yes. On a paid plan you can bring back a single playlist or specific songs instead of the whole library: ask DEBUSSY something like "bring back my Summer 2024 playlist" and it finds the most recent good copy — from a local snapshot or your cloud backup — shows you what it will restore, and waits for your approval before touching anything. Whole-library restore, which rolls everything back to one snapshot, is still there too, proven on both Rekordbox and Traktor.

It checks metadata completeness and quality across your whole library — missing tags, weak or missing artwork, incomplete data — and gives you a picture of where things stand, without changing anything itself.

Not yet clickable — the scan itself works, but the sidebar entry stays greyed through launch by design, not because it's broken. It's a deliberate nav-surface decision, separate from whether the underlying scan works.

It reports — it's a diagnostic, not a fix. If it finds gaps, FIX & ENRICH is the tool that actually closes them.

There's no fixed schedule — it's a snapshot of where your library stands whenever you run it, useful after adding a lot of new music or before a big gig if you want reassurance everything's in shape.

Yes — it works for any DJ platform present, not just one.

A read-only picture of your library's shape — track counts, genre breakdowns, years, and how your collection has grown over time.

Not yet — same as Library Health and Play History, it stays greyed through launch as a deliberate nav decision, even though the underlying data is already there.

No — it's read-only. We read your existing library data and summarise it; nothing about your library changes.

That's not something the current version does — statistics are shown for you to look at, not exported as a file. If that's something you'd use, the team is worth telling.

It's pulled from your DJ software's own play-count and play-date records — the same data Rekordbox or Traktor already keeps — not a separate tracking system.

Not yet as a sidebar click — it stays greyed through launch, same nav decision as Statistics and Library Health, even though the data itself is live under the hood.

There's a related but separate question here — whether phone play-counts sync back to your desktop library at all. That's not guaranteed today; check the mobile sync answer for the current state of that specific sync path.

Only what you explicitly save — enough context to pick the conversation or task back up. Nothing is turned into a saved project unless you asked for it; we never infer one from a conversation you didn't save.

That's a plan-specific detail the team can confirm for your account — it's not something this general answer should guess at.

If you don't see a delete option directly in the sidebar for a saved project, the team can remove one for you — worth flagging if this is something you need often.

General conversation memory and an explicitly-saved project are different things — a project is something you deliberately named and saved to come back to; it doesn't happen automatically just because you talked to DEBUSSY about it.