Where is wave data stored?

[trogluddite]

I'm not sure if that would be a bug or a feature: it sounds a bit...dangerous.

There certainly are times when a bit of care is required to ensure that resources aren't embedded, or even to insist to downloaders that they copy a module straight to their toolbox without playing with it first. It can also slow down access to the toolbox, as thumbnail images for modules which have a GUI are generated in real-time by loading them as "mini-schematics" and executing their drawing routines. This has been known to cause start-up crashes due to buggy toolbox modules, or problems with Ruby code where global objects defined in toolbox modules are made visible to schematics by the shared Ruby interpreter instance. A thumbnail cache would be preferable, IMHO.

On the whole though, given the intent to appeal to non-programmers and novices, I think it was the right choice to minimise the need for explicit resource management; but I do I think that the documentation should have included at least a little guidance on the potential pitfalls.

[Spogg]

Indeed trog!

One thing to watch out for is preset parameters stored inside knobs and controls which have been saved into the toolbox.

The user guide tells us that if there is no preset parameter, the default setting will be adopted. However, the hidden preset parameter list (from an earlier project) will be saved and indexed by the Preset Manager. This means that “Program 17”, irrespective of the name associated with it, will call up the stored parameter value in slot 17. There is no way to clear this data other than to replace the preset parameter prim in the knob from the toolbox, which will be empty.

In practice it’s not really a problem because you will normally create new presets for a new project and thus the stored parameters will be overwritten. However, if you allow 128 presets but only provide say 30 new presets, the user may be puzzled by seeing the knobs jump around for the higher Program numbers. Some of these undefined presets could possibly inadvertently set up illegal conditions leading to horrid noises or lock-up, depending on the topology of the synth etc.

So my recommendation would be to make your presets, then provide a few INIT presets at the end of the list, and these settings will all be defined.

Cheers

Spogg