Support

Support.

Common questions below. If you don't find an answer, get in touch directly.

FAQ

Common questions.

Will SessionCodex move my sessions?

No. SessionCodex never moves, copies, or modifies your session files. It reads them in place, builds an index, and writes a small sidecar file (plain JSON) into a .dtxaudio/ folder alongside each session.

Your DAW projects stay exactly where your DAW saves them. The catalog sits over your library — it doesn't reorganize it.

Does it work without Pro Tools / Ableton / Logic / REAPER / Reason / Studio One / GarageBand installed?

Mostly, yes. SessionCodex reads each DAW's native session format directly — it doesn't need the DAW installed to catalog sessions made in that DAW.

The one exception is Pro Tools deep integration, which uses PTSL (Avid's gRPC interface) for live session inspection. That feature requires Pro Tools 2023.6 or later to be installed and running. File-level scanning of Pro Tools sessions still works without it.

Can I use it on my studio's main machine and my laptop?

Yes. The Perpetual License covers up to two of your own machines. Move drives, swap rooms, hand work to your laptop for a session away from the studio — the catalog travels with the work, because it lives in the sidecar files next to the sessions.

Does it work offline?

Yes. SessionCodex is local-first. Your library lives on your machine, the index lives on your machine, and search runs entirely locally. No internet connection is required to scan, search, organize, or open sessions.

What happens to my data if SessionCodex shuts down?

Every session SessionCodex knows about has a sidecar file written next to it — plain JSON, readable in any text editor. If SessionCodex disappeared tomorrow, your sessions wouldn't be affected, and the metadata next to them would still be there in a format anyone can parse.

No proprietary database, no cloud account, no lock-in.

Will there be a Windows version?

Not at launch. SessionCodex v1 is macOS-only. A Windows version isn't on the near-term roadmap — the engineering effort to reach feature parity (especially around PTSL and Logic packaging) is significant, and the audience we're starting with is heavily Mac-based.

If demand changes that calculus, we'll revisit.

Why not put it on the Mac App Store?

The Mac App Store sandbox restricts the kind of cross-DAW file access SessionCodex depends on. It needs to read sessions wherever your DAWs save them — and write sidecar files alongside those sessions — without per-folder prompts breaking the experience.

Selling directly is what makes the feature set possible. See the pricing page for the longer version.

Is there a free version?

The beta is free for invited testers. At launch, SessionCodex will be sold directly — one-time payment, no subscription for the core product. There isn't a perpetual free tier planned.

Can I get a refund?

Yes, within 14 days of purchase. Email support@sessioncodex.com and we'll refund your license — no questions asked.

If SessionCodex doesn't earn its place in your workflow within two weeks, it isn't going to.

Who builds this?

Derek Teaderman, working under DTX Audio in California. Day job: AV engineering for the City of Dublin. Nights and weekends: SessionCodex.

The features that ship are the features Derek uses every day. The features on the roadmap are the ones he's building next, because he needs them next. Not a venture-funded startup — one engineer building the tool he wished he had.

Contact

Get in touch.

Email
support@sessioncodex.com
General questions, refund requests, and anything you can't find an answer to above. Derek reads this address directly.
Beta channel
For beta testers: use the private feedback channel for build-specific issues — crashes, bugs, scan oddities, missing metadata from a particular session. The private link is sent at onboarding.
Beta access
Not yet a tester? Request beta access — requests are reviewed and offered as slots open up.