Back to corpus
research noteexperiment writeup candidatescore 18
Echelon SuperCollider Integration
1. Open SuperCollider IDE 2. Open `echelon_synths.scd` 3. Boot the server: `Cmd+B` (Mac) or `Ctrl+B` (Windows/Linux) 4. Evaluate the entire file: `Cmd+Shift+Enter` (Mac) or `Ctrl+Shift+Enter`
Full HTML reader
Read the full artifact
Extracted abstract or opening context
1. Open SuperCollider IDE 2. Open `echelon_synths.scd` 3. Boot the server: `Cmd+B` (Mac) or `Ctrl+B` (Windows/Linux) 4. Evaluate the entire file: `Cmd+Shift+Enter` (Mac) or `Ctrl+Shift+Enter`
### 🏠 House Music | Synth | Description | Key Parameters | |-------|-------------|----------------| | `houseKick` | Deep, punchy kick | freq, punch, decay | | `houseBass` | Warm, groovy bass | freq, cutoff, res | | `houseChord` | Stabby chord | freq, attack, release | | `housePad` | Lush, warm pad | freq, attack, cutoff | | `houseHiHat` | Closed hi-hat | decay | | `houseOpenHat` | Open hi-hat | decay | | `houseClap` | Classic clap | amp |
### ⚡ Techno | Synth | Description | Key Parameters | |-------|-------------|----------------| | `technoKick` | Hard, industrial kick | freq, punch, distort | | `acidBass` | 303-style acid | freq, cutoff, res, accent | | `technoLead` | Harsh metallic lead | freq, cutoff | | `industrialPerc` | Industrial percussion | freq, decay |
### 🎹 Jazz | Synth | Description | Key Parameters | |-------|-------------|----------------| | `jazzPiano` | Rhodes-style piano | freq, vel | | `uprightBass` | Acoustic upright bass | freq | | `brushedSnare` | Brushed snare drum | amp | | `jazzRide` | Jazz ride cymbal | amp |
### 🤖 Electro | Synth | Description | Key Parameters | |-------|-------------|----------------| | `electroBass` | Funky synth bass | freq, cutoff, res | | `robotVoice` | Vocoder-style voice | freq, formant | | `electroClap` | Electronic clap | amp | | `synthStab` | Funky chord stab | freq |
Promotion decision
What has to happen next
Attach run IDs, datasets, metrics, and reproduction commands.
Why this is not always a full paper yet
Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.