adcxyz
commented
5 years ago Longer Proposal:
Storable user settings actually store choices from repertoires.
NTMI has repertoires of:
- sound generating processes (so far, Ndefs)
- presets for these sound processes
- master effects patches
- presets for the master effects patches
- influx weight presets?
- influx weight modifiers (tanh compression, terrain mapping)
- (others?)
Basic repertoires exist within the project folder; User repertoires should exist locally in a user NTMI dir, in a known location such as ~/NTMI/.
From these repertoires, users should be able to assemble full setup pages, which will be stored as a single .scd file; loading one such file will configure one full user setup.
Such a file would include: q.numChans names of preferred sounds to load // or if not given, load all ... names of preferred presets for the sounds to load names of preferred masterfx patches to load names of preferred influx weight presets to load names of preferred influx weight modifiers to load /// four names of sounds to put into slots four names of presets to set the sounds in slots name of influx weight preset to use name of influx weight modifier to use name on stored masterFX setting to activate
A file with known name and location, such as userdir/ntmi_prefs.scd
just stores which preset to load on startup.
What can users make and store?
Users should be able to make and store:
Settings for individual Ndefs by name (on NdefPresetGui) - infinite
Presets for inphlux weights (by name or random seed) - max 8
Settings for masterfx / ProxyChain (names & params of active objects)
Presets for full setup page, consisting of: x Group of 4 Ndefs + front preset name (+ short list of preset names to use?) x Inphlux - preset name, zoom, touch/move mode x Masterfx settings (as stored by name, + short list?) x ? Windows shown and their position?