workaround for modular bug!

Anything about the Scope modular synths

Moderators: valis, garyb

Post Reply
steffensen
Posts: 311
Joined: Fri Nov 08, 2002 4:00 pm
Location: Land of Polarbears
Contact:

Post by steffensen »

(if u dont want to read the whole story, just skip to the workaround.)

i get this little bug now and then, and im sure im not alone, where the modules state, dont get saved in the presets. (preset bug?)

even after replacing the module, it still wont save its settings. well, sometimes it actually works by just readding it, and resave the patch and presets, but most of the time it doesnt.

the other day i was building a rather big patch, and i had made several nice presets along the way, and as i added more stuff to my patch, i noticed the newly added modules didnt save its state in the presets. so i tried the readding technique, wich to my dispair, didnt work at all this time. :S

ok, im not a coder, so this is just a assumption, but it kinda feels like modular have the module locked somehow, like the module causing problems, are trapped in the binary of the patch somehow, like a ghost module if u will. so when i readd it, modular just think its the same module as before, and still wont treat it properly.

so, after some testing, i found out a workaround for this, finally. :smile:

workaround:
its time consuming, it tests your patience, but in some cases it might be worth it!

the trick is,
remove the failing module, (its important that u remove it from the patch, and resaves it all, otherwise im not sure this will work. it didnt for me anyway.)
reopen the patch, readd the same module again, but dont just add 1, add plenty! like 10,15 etc. sometimes it only takes perhaps 3..or 5.. but you never know really.
save those newly added modules current states in a preset, resave the patch and reopen it.
change the settings on the new modules, and click the preset you've saved to find out wich one of the new modules that get affected, and resets to the saved state.

when you have found a module that responds, remove the others and use the working one.
done.

as said, its time consuming and very testing for the old patience, but sometimes it might be worth it.
remember to do the workaround with the DSP hungry modules first, as you may need to readd them lots of times, before you trick modular to "unghost" it. :wink:

anyways, hope someone gets use of this, just thought id share it. :smile:
djmicron
Posts: 1181
Joined: Wed Jul 23, 2003 4:00 pm
Location: Milano

Post by djmicron »

on which modular shell do you have this kind of problem ?

I know that it's better to save the preset file with the same name of the patch and put it in the presets folder of scope, then save the patch, reopen it and all presets should works.

Someone prefer to work with the old modular shell with the old presets management that is more intuitive.
steffensen
Posts: 311
Joined: Fri Nov 08, 2002 4:00 pm
Location: Land of Polarbears
Contact:

Post by steffensen »

i use ModII shell, and i do just that, save the device and preset under the same name, as well as the preset file in the preset folder.

this is a bug many more than i have stumbled over tho, so i hope it can help someone out there, or just shine a little hope. :smile:

edit: btw, i dont think this have much to do with presets actually, more that some modules are failing. as u can read in my story above^.

<font size=-1>[ This Message was edited by: steffensen on 2006-03-18 03:13 ]</font>
Lima
Posts: 917
Joined: Mon Dec 29, 2003 4:00 pm
Location: Italy
Contact:

Post by Lima »

Hi Steffsen, I've experimented a similar throuble. I was doing a patch using 4 waldorf osc but in the presets there were saved the parameters only of 2 of them. I'll try your suggestions as soon as I repair my daw. Thanks! :smile:

<font size=-1>[ This Message was edited by: Lima on 2006-03-18 03:16 ]</font>
User avatar
astroman
Posts: 8446
Joined: Fri Feb 08, 2002 4:00 pm
Location: Germany

Post by astroman »

this is a very smart method for a work-around, respect :grin:

cheers, tom
Post Reply