From the original SynthMaker forum (2004–2014), with its members’ names and dates.
rl ·
I don't know whether I had requested this before, currently I'm constantly searching through lots of schematics to find certain modules. Also in case I'm doing changes in modules I have to open lot's of schematics to be able to change the modules there too.
So how about a library system: The idea is to be able to save modules to files and use an "include" feature to include these "external" modules into schematics. That would help me to organize modules. When doing changes on a module, the changes should be automatically available in any referring schematic.
sunsynth ·
+1... Damn good Idea rl!
I also do this everytime...
currently I'm constantly searching through lots of schematics to find certain modules. Also in case I'm doing changes in modules I have to open lot's of schematics to be able to change the modules there too.
SUNsynth
Acrobat ·
rl wrote: I don't know whether I had requested this before, currently I'm constantly searching through lots of schematics to find certain modules. Also in case I'm doing changes in modules I have to open lot's of schematics to be able to change the modules there too.
So how about a library system: The idea is to be able to save modules to files and use an "include" feature to include these "external" modules into schematics. That would help me to organize modules. When doing changes on a module, the changes should be automatically available in any referring schematic.
I see it more as a "FREEZE" to modules: when freezed they take a different colour and follow RL's rules, otherwise they don't update themselves. Someway advertised explicitly like the "NO MORE SUPPORTED" red & white circling.
Afterall is like syncronizing but OVER ALL the .OSMs, right? 🙂
P.S.: a password must be provided to edit the inside, so taking both the requests for lockable modules.
exonerate ·
This is a very good idea, I think though we would need to thrash out the details of how we expect it should work.
I'm thinking it should work like this....
You have an osm which contains all the modules you want in that "library" then you can have an option to save the osm as a .lib (library file). Then for any project you want to use the modules in , there can be an option to include .lib files, once the lib file is included there could be a drop list somewhere where you can select the modules from the lib files you included, select which module you want then it will show up at the mouse cursor. I think it should be editable from within the project, also there should be something as acrobat suggested to distinguish that it is part of a library file, and an option to "make unique" so you can alter a module without it affecting all the others.
And of course when you include a .lib file only the modules used should be added to the vst at compile time.
@rl, I'm just wondering do you have any specific details of how you could see this working exactly? I'm thinking if we could get specifics down then it would give the devs more to start with.
I'm wondering actually if any other modular environment has something like this.......
Cheers 😉
Exo
rl ·
I'm wondering actually if any other modular environment has something like this.......
PD (http://puredata.info) does that.
Idea:
Just save a module to file. In another schematic instead of dragging a module from the toolbox, a module could be created by opening from file. Every time SM opens a schematic SM should re-read all included modules from file.
BTW, Missing Feature: it's not possible to copy 'n paste modules from one running Synthmaker program to another, only when both schematic are open in the same Synthmaker instance
philter5 ·
i think it might be also usefull if there is a folder in the toolbox with all the modules that are used in the current project.
for example: i´d like to select many modules at once to copy and paste them 🙂 . but selecting with clicking a rectangle around the modules is impossible because of their position 🙁 and clicking every single module while holding shift is not really a better way to do it 😠 . so i imagine a tree view where you can look at all used modules at once, view only the modules used in a specific layer, only the used math modules etc. then you can select a large amount of modules easily even if the are not in the same layer youre working at 😀 😀 😀 .
philter5 ·
...switching the visibility of special kinds of links (for example all poly streams in the whole schematic)
on & off could be a nice feature, too. 🙂
Wrote something here? To have a post removed or your name hidden, write to [email protected].