Colour was 35 call sites and ~29 distinct literals spread across four widget
files, with no egui Style or Visuals set at all - so the hand-painted widgets
were hand-coloured while ParamSlider and the labels sat on stock egui defaults,
which is most of why the UI did not read as one thing.
The audit turned up more than duplication. Two different panel blacks
((16,16,20) and (20,20,24)) for the same intended surface; three reds, two
greens and two blues close enough to look like mistakes; eight greys doing
about four jobs. And a genuine collision: blue/green/orange meant LOW/MID/HIGH
in the crossover and input/output/gain-reduction in the scope, so orange meant
"the high band" in one widget and "gain reduction" in the one beside it.
The rule that resolves it, and that the module documents: channel hue is
chrome, functional colour is data. A pixel showing a value comes from the
functional palette and means the same thing in every channel; a pixel saying
which channel you are looking at comes from that channel's hue and never
touches the data. The scope turns out not to need arbitration at all - it is
tabbed, one channel at a time, so its three traces never compete with a hue.
Two tiers. Seeds are a short hand-picked list: four channel hues, the
functional colours, six neutrals. Everything else derives from a hue via
`channel()`, so recolouring a channel is one constant. Derivation is const fn -
including the HSV conversion, written out because ecolor's is not const - so
the whole table is built at compile time and costs nothing at runtime.
Chosen so the hues describe the colours already in use: the derived crossover
strips land within 1-3 units of the literals they replace. The two drag handles
shift by ~17 on one channel, being now consistently saturated with the rest.
Also lands the one deliberate visual change: the meter's four cells were
identical and distinguishable only by the label underneath, which is where
channel identity was hardest to read. They now carry a dark channel wash and an
accent rule, while the bars stay strictly functional.
Visuals are wired from the same seeds in the editor's build closure, so egui's
own widgets stop looking foreign. meter.rs's local level_color is gone; the
palette owns the headroom ramp rather than there being two places to edit it.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LU1NRL7fAaZTtFMTTPn2b1
Retires the working codename now rather than at 1.0, because the two identity
constants a DAW uses to recognise a plugin across sessions can only be changed
for free while nothing has saved a project with it. Verified: zero references
to the plugin across all 69 FL project backups, under any identity string.
Derived spellings:
Cargo package codename_206 -> bari_206
bundle / DAW name Codename 206 |
206 prototype -> Bari 206 (unified; drops "prototype")
Rust types Codename206(Params) -> Bari206(Params)
CLAP_ID com.mikkeli.codename-206
-> org.novoyuuparosk.bari-206
VST3_CLASS_ID Codename206Maxi! -> Bari206Multiband
CLAP_ID moves to reverse-DNS on a domain actually controlled, and stops
disagreeing with a VENDOR that was already Novoyuuparosk. VST3_CLASS_ID stays
exactly 16 bytes and drops "Maxi", which sat close to Image-Line's Maximus and
Maximizer in the same product category.
Author identity converges on Mikkeli Matlock <mikkeli@novoyuuparosk.org>;
Cargo authors had been carrying a personal gmail address while Plugin::EMAIL
already used the org one. VENDOR stays Novoyuuparosk, which is the org rather
than the person, and copyright stays with the person.
Deliberately unchanged: the repo, its remote, the local directory and the
homepage URL all keep "codename-206". Renaming those buys nothing and costs a
Gitea rename, a remote rewrite and a directory move, so the bare "codename-206"
is current branding rather than residue - and is the one spelling the STALE
list must not contain.
Driven by check-branding.sh rather than by grep: setting the canonical block
listed all 26 sites, including .github/workflows/ci.yaml, which no explicit
check covered. That gap is now closed by a positive check on the CI bundle
command, so a future rename fails in seconds instead of after a full compile.
STALE now carries both the retired and the new spellings, so the next rename
is self-checking too.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LU1NRL7fAaZTtFMTTPn2b1
Commit 057d630 switched this repo from GPL-3.0 to Apache-2.0, which the
build contradicts: src/lib.rs calls nih_export_vst3! unconditionally and
nih_plug is taken with default features, so every build links vst3-sys —
GPLv3-or-later by its own authors' choice. deploy.ps1 then installs that
binary. The declared licence and the artifact's actual terms disagreed,
and the original GPL-3.0 was correct.
Given the intent to distribute non-profit and open-source, GPL costs
nothing here, so this restores it rather than dropping VST3 to keep a
permissive licence.
Also adds the ISC notice owed to Robbert van der Helm: the plugin
scaffolding derives from the NIH-plug cookiecutter template and example
plugins, whose one condition is that the copyright and permission notice
travel with all copies. The README credited the template under Reference
Material, which is courtesy, not compliance. ISC is GPL-compatible, so the
notice is retained in NOTICE rather than superseded.
Corrects the README's claim that Steinberg's SDK licence must be accepted
before distributing. No SDK source is vendored or redistributed, so there
is nothing to accept at build time. The binding constraint is vst3-sys's
GPLv3; Steinberg's trademark in "VST" is a separate regime that no source
licence resolves.
Copyright in the Irene <irene@novoyuuparosk.org> commits is held by the
repository owner (an agent identity), so no third-party agreement was
needed for this relicense.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WHt4DykxXaQnyaJfyS8KCn
Replace the two plain crossover sliders with a horizontal log-frequency strip
(LOW/MID/HIGH) and two draggable handles, plus number boxes (double-click to
type). Handles and boxes enforce a dynamic limit so lo/mid never crosses
mid/hi, on top of each param's own range. Lives in the editor/ widget module.
Known limitation: the lo<=hi limit is editor-only, so host automation can write
the two params past each other (briefly inverting the mid band). The DSP clamps
to monotonic, but FL's automation can misbehave once inverted. Left as-is.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Mikkeli Matlock
mikkeli
irene