(another one) workaround for the preset bug

Anything about the Scope modular synths

Moderators: valis, garyb

Post Reply
Lima
Posts: 917
Joined: Mon Dec 29, 2003 4:00 pm
Location: Italy
Contact:

(another one) workaround for the preset bug

Post by Lima »

The trick can takes more time than the one previously appeared ( see : http://www.planetz.com/forums/viewtopic ... und+preset ) but it works without following a kind of "try and error" procedure, so for certain not too big patches could be worthy.

Assuming that the user has already done a patch wich sounds great and he don't want to change it anymore, the procedure consists in a total rebuild of the patch under another name. Do the following steps in that order:

1) Open a new modular window

2) Drag and drop all the necessary modules WITHOUT connecting them. (I use to open also the old patch, so I can compare the two shells)

3) Save the modular now with another name. I usually save the modular in another path too (for example into the desktop)

4) Now open the preset list and create a new bank, then save a preset (for example "init"). Save it using the "save as" in the preset menu. Take care to choose the appropriate name (corresponding to the modular one)

5) Save and remove the modular. If it's asked to save the preset, answer YES.

6) Reload the patch. It should be already working. To check this try to move every parameter and then recall the init preset to see if they return in the original position.

7) Redo the cabling and then resave.

NOTE: I belive that the preset bug occurs when some cabled modules are removed. This could make a kind of "loosed pointer" issue somewhere inside the modular's preset structure. SO NEVER REMOVE ANY MODULE (i've got to test if the same occurs also adding new modules).

As you can see the workaround is very time consuming expecially for big patches. Imo it's worthy only as final step for the best patches.

:-)
Welcome to the dawning of a new empire
Lima
Posts: 917
Joined: Mon Dec 29, 2003 4:00 pm
Location: Italy
Contact:

Post by Lima »

NOTE: anyway some modules don't save the preset, but this is related to the module itself, not to the preset bug.

For example the 2x1 switches made by JB or the Fexor's elastic-XY don't save their preset.

To check if the module can save the preset, just open a new shell and add the module then save the preset (init). Then change the parameter and recall the preset.
Welcome to the dawning of a new empire
Post Reply