From the original SynthMaker forum (2004–2014), with its members’ names and dates.
infuzion ·
Every 2 months or so someone either does not know they have to turn on a switch to see all of the toolbox, or accidentally turns it off & forgets how to turn it back on. There really is no point to having the Developer Mode "feature". There are not enough modules to make more than the generic-SM-looking simplest synth that eats up your CPU (which makes it seem more amateurish). One has to have access to the R&D parts to do more than that.
Let's face it, SM is a programmer-geek tool. It's not at the stage to slap stuff together like SE is, & you really have download a bunch of user-made modules to make interesting stuff there also. I think the intention for the Developer Mode was to make more "user friendly" but IMHO it would be more friendly to just remove the switches.
Plus it would give use a bit more screen space also, & smaller OSMs.
cheers
Tzarls ·
I think you mean "developer mode", not R&D? Although R&D also doesn´t have much sense either, so +1 for this one (be it Developer Mode, R&D or both).
aliasant ·
+1
infuzion ·
Tzarls wrote: I think you mean "developer mode", not R&D? Although R&D also doesn´t have much sense either, so +1 for this one (be it Developer Mode, R&D or both).
oops yea, changed, ty
attic ·
+1 It is confusing to the new users me being one off those.
Acrobat ·
Well, lets see it in a positive way: the "developer" primitive lets you hide some modules from the toolbox and that's a very useful feature, it can be used to create a separation between, for example, modules that are definitive and modules that you still want to improve or any other useful classification or hierarchy. 😉
attic ·
Acrobat wrote: Well, lets see it in a positive way: the "developer" primitive lets you hide some modules from the toolbox and that's a very useful feature, it can be used to create a separation between, for example, modules that are definitive and modules that you still want to improve or any other useful classification or hierarchy. 😉
Ok, but lets make sure that users are well informed that it is there. 😉
infuzion ·
Acrobat wrote: Well, lets see it in a positive way: the "developer" primitive lets you hide some modules from the toolbox and that's a very useful feature, it can be used to create a separation between, for example, modules that are definitive and modules that you still want to improve or any other useful classification or hierarchy. 😉
Again, "hiding" modules by adding a primitive is pointless when one can just keep those "experimental" modules in a separate install like with the Analog Modelling Kit, or better still in a demo OSM.
If it ships with SM, it should be instantly available. If it is too dangerous, then ship separately.
Wrote something here? To have a post removed or your name hidden, write to [email protected].