NOMIAPPS / MIXXX2.7.0-nomi
INDEPENDENT DEVELOPMENT

Road to Mixxx 3.0

A performance-first desktop fork. Built around the way you mix.

Read the project docs
NomiApps forkSnapshot · 06 Sep 2026Current focus · validationAI-authored draft · awaiting your review
MX-06 landed. The core surfaces are implemented. The critical path is now rig sessions, restart round-trips and clean-install evidence (MX-07–MX-09). Validation may uncover further fixes.

The road ahead

Open a card for scope, evidence and the finish line.

Implemented

6

The foundation already in place.

In motion

0

Current work and integration.

MX-06 has landed. No implementation task is currently tracked here.

To validate

3

Prove it on the rig.

Later

2

Keep the first release focused.

FROM WORKING BUILD TO DAILY DRIVER

A focused route to release

Validation sequence · no new deadline
01Implemented

Core surfaces landed

Samplers and effects complete the performance surface. The landed baseline is ee9d09b2cc and its binary is fresh.

Build evidence recorded · rig sign-off remains open.
02Next · MX-07 & MX-08

Use it hard

Mix on the actual rig. Exercise controllers, stems, touch, display changes and saved state. Resolve reproducible faults.

Gate: evidence from complete mixing sessions.
03Then · MX-09

Make it repeatable

Freeze release scope, verify a clean installation, document setup and produce a reproducible release candidate.

Gate: the same candidate passes the release checklist.
PROJECT DOCUMENTATION

One place for the decisions.

The roadmap follows the NomiApps fork. Each feature document carries its own scope, evidence and acceptance criteria.

Download roadmap as Markdown
01 Product scope

Target a dependable Windows desktop and touch DJ workflow on the upstream 2.7 engine with the New UI: decks, waveforms, stems, library, mixer, samplers, effects and controller access.

“Road to Mixxx 3.0” names the New UI roadmap. The fork binary reports 2.7.0-nomi; the title is not an engine-version claim.

Retain access to legacy preferences while the new settings surface develops. Android, a full preferences rewrite, portrait layouts and AI Auto DJ are proposed later work, subject to your priorities.

02 What the statuses mean

Implemented: repository history or project notes establish the implementation. Hardware acceptance may remain open.

In motion: implementation work not yet landed. MX-06, contributed by Grok, has moved to Implemented.

To validate: a release requirement needs recorded evidence. Later: an idea or proposed deferral, outside the initial release plan.

03 Release checklist
  • Core two- and four-deck journeys pass on the target rig.
  • Library views, smart-crate definitions, sorting and settings survive restart; selected crate scope intentionally does not.
  • Controllers, touch and mouse produce consistent control state.
  • Complete mixing sessions have no unresolved crashes or audible dropouts attributable to the candidate.
  • A clean installation launches with documented audio and controller setup.
  • The tested revision, known issues and recovery instructions accompany the release.

All checks are pending evidence. Set session duration and supported hardware before the validation pass.

04 Evidence & maintenance

Verified update dated 6 September 2026: C:/StreamDeck/src/mixxx-shared, baseline ee9d09b2cc, 19 commits beyond the prior snapshot. The fork trunk is origin/main; upstream Mixxx is upstream/main. The checked worktree is clean and matches its origin tracking ref.

The freshness check passes against 2005 compiled-in sources. No hardware acceptance is recorded; all six release checks remain open. Historical PREFERENCES.md, TESTING.md, RESPONSIVE-REFLOW-SCOPE.md and AUTODJ-AI-SCOPE.md live in C:/StreamDeck/mixxx-pr-kit, outside the source worktrees. This page is a curated snapshot, not a live repository monitor.

For each update, record the worktree, revision, what changed and the rig-test outcome. Move a feature only when its evidence supports the new status.