From the original SynthMaker forum (2004–2014), with its members’ names and dates.
sonicfire ·
what i would really like to see (in future) is the possibilty to have some kind of loading / unloading of pre-designed (build in SM) schematics/modules at runtime (when VST(i) is running in Host).
for a example if you want to develop something modular (reason for e.g.) you could add another instance of a module and so on ...
(was always dreaming of a way to do this) 😉
i´m not sure if this will work at all due to pre-compilation?
sonicfire ·
erm.... bad idea? 🙂
jorge ·
Hi sonicfire
Definitely not a bad idea, it just got me thinking and I need to think it more.
My first thought was if a VST version of SM would be what you're looking for.
sonicfire wrote: i´m not sure if this will work at all due to pre-compilation?
I think that's not a problem because the compiling is dynamic, it happens even inside a VST plugin when inside a host.
So would you want to have the toolbox showing so you could drag modules to the schematic? I'm sure there would be issues with the number of preset parameters changing etc
stefan ·
You could always just expose a number of automation parameters, and use a chunk based preset format instead. I think it's doable anyway 🙂
lalo ·
stefancrs wrote: You could always just expose a number of automation parameters, and use a chunk based preset format instead. I think it's doable anyway 🙂
😀
sonicfire ·
jorge wrote: My first thought was if a VST version of SM would be what you're looking for.
Yes, something like this.
Or at least perhaps some ways to route/connect audio between pre-built modules inside a VST. Would give the user the flexibility to route fx the way she/he wants.
(< coming from SE, and it´s always a pain to route audio in a VST, when you have, lets say some kind of multi-fx.)
jorge wrote: So would you want to have the toolbox showing so you could drag modules to the schematic? I'm sure there would be issues with the number of preset parameters changing etc
Thats true, but it depends on what kind of application you build. I´m sure there´s a way to handle presets only in modules/schematics or something?
Sorry if something in my post doesn´t make sense. I´m just writing down my ideas (with bad english 😉)
sonicfire ·
to clear it all up:
i was always dreaming of developing some kind of (simple) Reason as a VST-Plugin, where you just have a bunch of samplers and effects and could dynamically load up instances of them and route midi/audio between them.... 🙂
stefan ·
If it would only be a matter of routing, that's already doable 🙂 You could have a synth with 20 envelopes, 20 lfos, 20 oscillators etc and let the user do the routing. That's doable. And the stuff not connected won't be included in the process at all.
sonicfire ·
yes, but what i want/mean is more than just routing 🙂
rl ·
bidule?, energyXT?
stefan ·
It's probably not that much of a task to make the entire SM engine work like a vsti, except that you can't change preset parameters because the VST standard doesn't allow this. But one can still use vst automation and a chunk based preset format. Not something that is high priority to me, but it'll probably come in the future 🙂
sonicfire ·
I *REALLY* hope so! 😉
Wrote something here? To have a post removed or your name hidden, write to [email protected].