-
Notifications
You must be signed in to change notification settings - Fork 0
Choosing a Workspace
FWG separates one-patch editing, deliberate Morph design, broad random discovery, and controlled variation because they are different jobs. Choose the workspace by the decision you want to make next.
| Situation | Workspace |
|---|---|
| “I want to understand one generator.” | Playground |
| “I want to draw or import one endpoint waveform.” | Playground |
| “I have two endpoint sounds and want a transition between them.” | Morph |
| “I want one deliberate complete patch and export.” | Morph |
| “I want many unrelated complete patches.” | Bulk Random |
| “I found something close and want nearby alternatives.” | Bulk Explorer |
| “I want a repeatable custom variation recipe.” | Bulk Explorer |
| “I need exact cycles, output PCM samples, frequency, duration, or Pitch Offset conversion.” | Calculators |
“I want an MPC folder and format.json.” |
Morph, Bulk, or Explorer with MPC Mode |
Playground owns one endpoint-style sound state and does not export files. Use it to learn a generator, draw/import a waveform, or design a source that may later become START or END.
Morph owns START, END, their relationship, and export settings. Use it when the relationship between two complete endpoint patches matters—or when you simply want one deliberate export under full control.
Each iteration may create a new, unrelated complete patch.
Use it for:
- broad discovery;
- quick collection building;
- high-volume auditioning;
- searching without a known centre;
- deliberately strange accidents.
Each iteration starts from a known complete state and follows the variation rules you allow.
Use it for:
- controlled alternatives;
- related patch families;
- tuning a near-miss;
- preserving an identity while widening or narrowing selected parameters;
- repeatable custom random systems.
Use Morph when you know the START, END, Morph, and export state you want.
Use Explorer when the exact result is not final, but you know the neighbourhood worth searching.
For an ordinary sample, the sound only needs to work as audio.
For a wavetable, nominal-root-cycle geometry, wavetable-frame behaviour, scanning, and the destination instrument also matter. Cycle-stepped transition, Phase-Coherent Mode, and coherent Bulk pools can help when appropriate, but mechanical validity is not the same thing as musical usefulness.
Documentation rule: The executable code is authoritative. This Wiki describes the supported Fractured Wavetable Generator v3.0 contract and workflows.
- Generator Families
- Classic Waveforms
- Classic Split
- Drawn Waveform
- Drawn Wave-Shape Recipes
- Source Taps and Routing
- Wavetable Types
- Modulation and Filter
- Pitch, MIDI, and Pitch Offset
- Source and Result Windows
- Visualisers
- Morph Render Modes
- Morph Curve and Cycle Stepping
- Phase-Coherent Mode
- Loop Safety and Table Safety
- Creating Wavetables
- Creating Samples, Drones, Hits, Transitions, and Multisamples
- MPC Wavetable Mode
- Installing and Auditioning on MPC
- Render and Export Settings
- Auditioning, Curation, and Building a Personal Library
- Saving, Loading, and JSON Sidecars
- Sharing and Cleaning JSON Sidecars
- Randomisation and Seeds
- Keyboard Shortcuts
- Browser Requirements and Performance
- Troubleshooting
- FAQ
- Glossary
- Compatibility and Versioning
- Version 3 Release Notes
- Drawn Mathematical Reference
- Signal Path and Core Concepts
- Meditations on the 512-Sample Core
- Scanning Generator Wrapper Architecture
- Deterministic Randomisation — Technical Reference
- Render Diagnostics and Support
- Proof of Zero Prior-Work Knowledge and Forensic Evidence
- Authenticating and Timestamping FWG Outputs
- License, Provenance, and Outputs