DSP Robotics Support

Is there any way to acces all data of currently selected preset from preset manager? Accesing only from preset parameter module is very limiting. I'm looking for a way to access data for realtime manipulation (preset morphing for example). Send all values to array, do changes and then back to preset manager or directly send changes to all controls.

When you save the preset,
it is a text file.
Maybe you could manipulate the text to a degree?
AFAIK, this is the only way to access the presest data,
sorry.

I would do it in a way "Preset Manager <--> arrays <--> preset modules". So instead sending the parameters to manager via "P" node - they could be send to array containers (as strings, ints, floats), which can be manipulated. And only main atrrays would be stored as "presets". I haven't tested yet how it works, but I'm thinking to split it that way. Currently my project has c.a. 2000 parameters to store/load and it takes time... A lot of time.

Nix:
I know I can acces data via saved txt but this is not an option. Too bad that there is no other option for that.

Tester:
Well problem is how to acces data from preset manager to fill that array. With preset paramer module you can acces only one value if you feed it with parameter name. But I need acces to all values. Other problem will be again to send manipulated data to all controls since you again need parameter name. So I was looking for PresetManager<-->array<-->PresetManager.

Haven't used it yet, but i see there is a primitive "preset parameter array".

Plus - it's possible to do some manipulation on text files without using preset manager to store the data itself (i.e. PM works then with paths, not file content).

Preset parameter array is the same as preset parameter module. It is used in step/graphic LFO for example, so you still need parameter name to access data.

+1
I'd love to see some better access inside the Manager info too.
I have had some success with auto-saving/loading "temp" preset definition text files - but it gets really messy, and it's hard to make a simple module of it that anyone could just drop into their schematic.

tester wrote:Haven't used it yet, but i see there is a primitive "preset parameter array".

You have to be quite careful with these - in some hosts, presets where the array is a different size will corrupt the data when loaded. Putting the array as the last parameter can make them more reliable - but at the moment, that is a bit of PITA to do as well.