Atlas node · Tools · prototype platform

MOARkNOBS-42

Teensy-based MIDI controller platform that treats mappings, latency, feedback, and validation as part of the instrument rather than invisible engineering residue.

Repository →

What this makes visible

MOARkNOBS-42 is not only a box of controls. It is a way of making timing, mapping, feedback, and bodily decision visible enough to be played, taught, tested, and repaired.

The instrument matters because control is never neutral. A knob is a promise about what can be changed, when it can be changed, and who can understand the change while the room is moving.

The latency rig, mapping manifests, validation tools, and mode feedback keep that promise inspectable. The work asks the controller to show its behavior before it asks anyone to trust it.

The public claim stays with behavior, method, and legibility. It does not ask the prototype to pretend it is already a finished product.

What it is

MOARkNOBS-42 is a control-instrument research platform built around a deliberate 42-control grammar, visible mappings, mode feedback, and bench-tested documentation. It is public as a promising platform, not as a finished production controller.

What it lets people do

It lets performers and learners test how physical controls, mapping manifests, LED feedback, and measurable latency shape authorship in a live control system.

What is public now

Evidence status

Status: prototype platform. Public source and method notes exist, but stronger public proof still needs a current validation capture, a manifest example, and a bench photo of the present hardware state.

Next proof object: 30-second MIDI validation capture showing stable CC output, visible mode LED changes, and either a MIDI monitor or latency log in frame.

What remains unresolved

  • The current public page should not imply enclosure maturity, operator-independence, or production readiness.
  • A public BOM, calibration path, and current hardware photo are still missing.
  • Live-rig integration proof should stay modest until a concrete capture is linked.

Methods surfaced

Proof objects

  • Latency rig diagram Status: public. Public-safe diagram of the measurement framing around the instrument.
  • Latency characterization lab Status: public. Public method note for measuring latency and feel.
  • MIDI validation capture Status: needed. Current public proof still needs a short capture showing stable CC output and visible mode feedback.
  • live-rig Shows how the controller can move outward into a larger scene system.
  • StringField A neighboring embodied-interface line that pushes beyond knobs and panel logic.
  • seedBox Connects the control surface to portable instrument and teaching contexts.

Source trail

The Atlas is the relationship layer. Use the repository for current project-specific truth, and use studio-notes when methods, decisions, or teaching material need to travel across the fleet.

Where to go next

  • Open live-rig — See where the controller becomes part of a larger scene topology.
  • Open frZone — Follow the branch from control into analysis and triggering.
  • Open Horizon — Follow the branch from control into DSP and listening evidence.