Updated Home (markdown)
Document the banks, the browser and the MIDI control Two pages the manual did not have, for two things it did not have when it was written. Banks and patches: why a bank is a hundred and twenty-eight slots and not as many as it holds, the browser and the four shapes a Synth1 bank arrives in, why writing a patch cannot load on click, and where a sound is kept in each of the three builds -- which differs because who owns the persisting differs. MIDI control: what the specification decides and what is left to you, the Sound Controllers and why honouring them means a keyboard works on being plugged in, and the three quite different routes these messages take into a browser, a CLAP and a VST3. That last one is worth writing down: VST3 has no event for a controller or a program change at all, and a program list is what a host looks for before it will route one. Getting started now has the CLAP, including that all three files have to travel together -- a .clap copied on its own plays and shows the host's generic controls, which reads as a broken plugin rather than a missing folder.
Just the pronunciation Where the name comes from is not the reader's problem; how to say it is.
Say how the name is pronounced It is a portmanteau nobody can be expected to guess at: the first syllable is Spanish, not English, so it is keh and not kwee.
Split the manual into pages One 27 KB page was a scroll, not a manual. The sections were already self-contained, so each becomes a page: the landing page keeps what a reader arriving cold needs -- what the instrument is and how it is wired -- and hands off from there. Adds a sidebar on every page and previous/next links at the foot of each, so the whole thing still reads in order for anyone who wants to read it in order. Every internal anchor that pointed at another section is now a link to that page.
The manual: theory, mathematics, and the patch archetypes Replaces the placeholder page. Covers what the instrument is and how to run it, the signal path, the synthesis theory behind each section, the formulas the DSP actually uses, how the 99 parameters are stored -- which is the part most likely to bite anyone generating patches -- the sixteen factory archetypes and how to build each one, both patch formats, the layering, and the measurement habits the project relies on.
Initial Home page