Atlas node · Tools · prototype platform

MOARkNOBS-42

Teensy-based MIDI/OSC hardware-test platform with documented mappings, feedback paths, validation methods, and limited dated board-backed receipts.

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.

Public source includes mapping and manifest contracts, validation tooling, and dated board-backed receipts for boot/configuration, Bridge apply/readback, and live-control round trips. Latency remains a documented measurement method rather than a current public performance result.

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 hardware-test research platform with 42 configurable control slots, six envelope-follower inputs, documented mappings, and limited board-backed validation. It is public as a prototype, not as a finished production controller.

What it lets people do

It is designed for performers and learners to examine how physical controls, documented mappings, feedback paths, and measurement protocols shape authorship in a live control system.

What is public now

Evidence status

Status: hardware-test prototype. The public repository contains dated board-backed receipts and prototype-board documentation, but it does not establish fabrication readiness, full power/display validation, or a public performance capture.

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.
  • No public fabrication BOM or verified fabrication bundle is available; the portfolio also lacks a linked calibration path.
  • 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; it does not itself report a current latency result.
  • Board-backed HIL receipts Status: public. Dated boot/configuration, Bridge-session, and live-control receipts; each states its own limits.
  • 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.