Aluminium

[neilbgr]

• Repo: https://github.com/neilbgr/Aluminium
• License: GPL-3.0-or-later
• Commit: 9ff323e02c8fa4c45752fb8e4c66ed895d62d6ad

Aluminium is a small collection of utility Rack modules built around a
polyphonic MIDI-CV keyboard workflow:

• Zones — splits a polyphonic MIDI-CV keyboard signal (V/OCT, GATE,
  VELOCITY, AFTERTOUCH, RETRIGGER) into two note-range zones, each
  independently configurable as polyphonic passthrough or monophonic with
  note-priority (last/highest/lowest) and true legato gate behavior.
• Pads — 16 gate outputs, one per learned note, driven by a polyphonic
  V/OCT + GATE cable (e.g. from Core MIDI-CV or Zones); learn a cell by
  clicking it and playing (or typing) the note, with an optional per-cell
  Latch mode.
• PadX — Pads expander that extracts a freely-labeled polyphonic lane
  (Velocity, Aftertouch, Retrigger, ...) into 16 mono outputs, one per note
  Pads has learned.

README with manual/screenshots: https://github.com/neilbgr/Aluminium/blob/main/README.md

[cschol]

Static analysis issues: neilbgr/Aluminium#1

[neilbgr]

Version: 2.0.2
Commit: 3103107724b8cb45a45425a56153b278e0b32e9d

Fixed the cppcheck warning from the static analysis check (neilbgr/Aluminium#1):

src/PadX.hpp:16: warning: Member variable 'PadXMessage::activeChannel' has no initializer. [uninitMemberVarNoCtor]

activeChannel is now initialized to -1 (the "no channel" sentinel already used elsewhere in the code) for all 16 cells.

[neilbgr]

Pads: clicking elsewhere on the panel now confirms an in-progress typed note
(same as Enter) instead of always discarding it; clicking outside the panel
still cancels. A few doc fixes and a tag cleanup on PadX.

New Version: 2.1.0
Commit hash: 903dd24cf08ca0b87161346dc30f40022029dd03
repo: https://github.com/neilbgr/Aluminium

[neilbgr]

The commit referenced above (9ff323e02c8fa4c45752fb8e4c66ed895d62d6ad) no longer exists — I rewrote this repo's git history to remove a personal email address from the commit metadata. The content is unchanged; the same commit (same tree, same message, same date) now lives at:

fb4ead348fba52d0614ae023efd7b38f1c40d658

Tag v2.0.1 still points to it under the same name, so nothing else about the submission changes.