Sick and tired of messed up presets

darkrezin · Post by **darkrezin** » Tue Nov 25, 2003 3:22 pm

An excellent point, and I think I have to agree.

Also, I find the random speculation here from Braincell (for example) very amusing. Software companies sometimes cannot reveal everything about the development process, due to many reasons.

Working for a software company myself, I can say for certain that this kind of angered speculation is 99% of the time totally distanced from the truth.

peace

braincell · Post by **braincell** » Wed Nov 26, 2003 10:18 am

One thing that fosters angered speculation is when a company doesn't offer any information regarding the problem or what they are doing to fix it if anything. It's as if nothing is wrong.

darkrezin · Post by **darkrezin** » Wed Nov 26, 2003 11:24 am

I agree to an extent, but we all know they are working on SFP4.. I want the bug fixed as much as anyone, but until SFP4 is here, why bother wasting energy on it? If, when SFP4 is here, the bug is still there, I think that's a valid time to get annoyed about it, but until then, why not try to work around the problem as at0mic suggested?

peace

powerpulsarian · Post by **powerpulsarian** » Wed Dec 31, 2003 8:25 pm

here's a solution... buy a Nord G2

because now the big quesitons is whether there will ever even be a SFP 4.0 or any other updates to the platorm or the modular system

i really hope so

regardless, i really wish Creamware would let us know that they have our interests in mind and give an update on what they are doing, even if it is just to confirm that the problem will be fixed when SFP 4.0 is released and no earlier

we paid good money for this program and deserve at least that much

braincell · Post by **braincell** » Thu Jan 01, 2004 12:47 pm

Just to add my 2 cents to the many dollars I already put in. I bought a Nord Lead 1 many years ago. It's easy to use. I love the sound of it and it has never bombed!

valis · Post by **valis** » Thu Jan 01, 2004 7:51 pm

Would you abandon your Lead if Nord were to go bankrupt?

Bill Doughty · Post by **Bill Doughty** » Tue Jun 08, 2004 11:26 am

Has anyone checked to see if the bug still exists in SP4? I am reluctant to upgrade, but would be more motivated to if they fixed this terrible, awful bug.

roy thinnes · Post by **roy thinnes** » Sat Jun 12, 2004 7:14 pm

Maybe this isn't of any use for anyone who have these preset probs, but I have to tell you that after reinstalling my system a year ago (with different music/internet partitions), keeping the music part absolutely clean (only Cubase,Sfp,Acid...) I never had any problems with this stuff.One thing, too, is that I usually don't edit a saved patch.It's possible, though, if the additional modules are not editable (such as inverter,Gate Or...).I hope I am not a minority here - and I think telling people about the marvellous Nord Modular is not of any use for us Creamware Modular talkers.Ok, if you give to me the new G2 I would take it.No, honestly, this thing is cool, no doubt.

<font size=-1>[ This Message was edited by: roy thinnes on 2004-06-12 20:16 ]</font>

braineeter · Post by **braineeter** » Sat Jul 10, 2004 8:06 pm

I tried out one of the suggestions from the top of this thread -- redoing Mod patches from the ground-up, and spinning off presets only after the patch is fully complete....this seems to have helped greatly (although it is alot of work)...

I guess the conclusion is that if you create a Mod patch, spin off some presets, and then go back and change the patch's structure (eg. add/delete modules, change routings, etc), the 'saved preset settings' problem will be that much worse....

But even where i've redone patches from scratch, some modules still don't seem to work in terms of saved preset settings -- all of the Flexor oscillators and filters continue to give me problems in this regards....

---> after posting the previous msg last night, i discovered that Flexor preset settings actually do get saved. When you change a setting on a Flexor module, for some reason the 'Compare' button doesn't light up on your preset list, but nevertheless the new setting(s) do(es) take
hold once the preset is saved (and of course you have to save the preset file too).

So IOW i think the technique mentioned at the top of this thread does work -- take one of the patches with which you're having the preset problem....re-make the patch from scratch, then redo your presets.... after completing the patch, as long as you don't add/remove any modules or change any routings, your presets should work

Regards
GK

<font size=-1>[ This Message was edited by: braineeter on 2004-07-11 06:59 ]</font>

fra77x · Post by **fra77x** » Mon Aug 16, 2004 6:32 am

The procedure i use to avoid the broken preset list problem. (i encountered that for the first time with jlk's matrix which is ensential for me (jlk i would appreciate a 12x12 matrix!). After any change to the modular structure i create a new preset list- new bank -new preset- save preset list -save modular patch. And finally i use it in XTC mode!!!

at0m · Post by **at0m** » Mon Aug 16, 2004 11:53 am

Yes, that's the proper work-around

I always disregard the presets pop-up. The whole point of modular is to create a synth that fits the momentary needs, not? Then how can the presets correspond to this modified processor?

Admittedly, Ken's carefully tweaked 73 rhodes patch has some great presets. But if we'd throw in an LFO or sequencer, the preset list goes pearshape. Who cares for the preset % pop-up, the original basic parameters will still be remembered...

One tip: delete the Clock module from a patch when you load it, and replace it with a new one. Set it to the tune's BPM, and presets won't screw up the tempo of the patch anymore :] You will get the pop-up, but at least the tempo won't change on every preset. In DP the programmer has the option of including the parameters he wants for the preset list, in modular this is our trick to inhibit a module from changing upon preset selection.

Have fun patching!