DSP Robotics Support

What 'helped' me debug some of my early [and continued] workings with the PreSet Manager was to do an ALL PROGRAM SAVE. Then track down that text file, load it up into Notepad, and inspect everything that was in there.

I was often surprise to find things that were left overs, or some test routine that was off to the side of my schematic. Or to learn that one of the MIDI Monitors left inside a module under test was messing with the list of parameters.

I now try to be more aware of the preset implications, but in the heat of trying to develop an idea and realize it into a schematic, I find that I need several 'cleaning' sessions to straighten up the mess

Notepad and printer ... very handy

RJHollins, that is bad news . i try things and then remove them from the schematic as well. too bad they're still there, Although they have been already deleted and the preset has been resaved. inspecting values in the text file is a very tricky task. i don't realy understand FS's PM registry logic. i wish the PM had a reset input to reset the current preset to zero values, and then, when yo save new preset, you don't get any Oppressive "surprises"

Oh ... I hope I didn't give the wrong impression !

If a component that has preset capabilities is removed from the schematic, I believe the PM updates internally to this change. If I ever was in doubt, I would just delete the PM module, and then re-insert the PM again.

What's handy is that the PM text file has info on the number of components it's finding. All the Names are listed [in the order they were made ... which can be a problem locating]. But I agree, it can be a bit tedious.

If I ever was in doubt, I would just delete the PM module, and then re-insert the PM again.

If doing that helps, maybe i should try it too. thanks for the advice. i also found string editing and saving
(after compiling) very difficult to perform in some situations. tryed using some string array mathods, with no success.

take a look at this schematic:



in this schematic, i tried to give every knob an "in place" editable label. it means that if, for example, the user wants to change the knob's names, he can do it, but... he must save the new names set as a bank. and this bank
should carry the new names for all the presets, untill it changed again. well... found that impossible to do!
because every time you change a preset, the labels got changed too. if you import a new bank, they freak out. which means...

the labels nead their own PM????

using 2 PMs is impossible because after exporting to vst format, both PMs freak out in the daw. using only one for this task is useless. so how is that should be done?...