From the original SynthMaker forum (2004–2014), with its members’ names and dates.
bManic ·
Hi Malc, jorge and lalo (you guys are the only ones I've seen posting lately!)
One question: Will synthmaker continue to feature the .exe and .dll (vsti and vstfx) compiling? Was toying with ideas of using synthmaker for teaching (I'm really interested in pedagogics and will probably take some courses in this). It would be extremely cool to be able to make small .exe files and distribute them among pupils as homework!! Think about it! " Here's your assignement for next week. Complete the schematics and make a fully working 2pole LP filter. "
Amazing possibilities! And if you keep the graphic area as clear as the old version then it'll be a very useful tool for learning/teaching.
Also, how many low level components can we get to play with in the coming beta? Is there enough to start building some serious stuff already? Mainly meaning the maths modules and logic modules. What about help files? I loved the way jorgen sent me the helps as emails. Very clear and easy to understand.
Keep up the good work guys!
Cheers!
bManic
malc ·
Hi bManic,
SM will continue to support the features you're talking about (I might need to confirm this absolutely with Jorge though). None of this is in the new version yet, but it will be.
I like your idea about homework!
On the issue of components, we're trying to get a minimal set together that work well together and don't crash. Better to do this than release a whole load that are buggy.
In total we're probably talking about 30 or so components. As I said before, the initial set of components will be used primarily to show what the new version can do.
I'd be interested to hear your reaction to that. We're not sure how that will go down. However what we are sure of is that it won't be long before we have much more than that so please keep the faith.
I'll try and get some more info to you about this.
Incidentally we're now calling everything a component. Components can then be one of two types: primitives and modules (the low-level components are the primitives etc. etc. pretty much as before).
It's quite important to have a clear and unambiguous language for describing the application and this is something we've been thinking about alot.
All this leads nicely onto help and documentation. There will be a user guide for SM. This will be in electronic form. There won't be a help file in the normal Windows sense, but the user guide will hopefully be very 'help'ful.
In addition to the user guide, we want to build a collection of short tutorials and how to's to show you what you can do with SM and how easy it is to do it!
I hope this answers everything,
all the best,
Malc.
bManic ·
Thanks Malc for the info!
I think primitives and modules is a very nice way of naming the difference in components. Maybe add macros too? Macros would then of course be composed by many modules. Anyways, I agree that it is extremely important to make up proper names for the components and also other parts of SM so that documentation and questions are easier to understand.
Btw. guys, take your time to perfect the thing. I'm in no need for a beta with hundreds of components! Not at all.. I'd be more than happy with some basic primitives to get me started so that I can learn the interface again and maybe do some basic things. I'm a beta tester at heart so expect lots of feedback! 😉
Also, on a side note. I just finished setting up my system. Going after my genelec monitors today so from now on I can do critical listening tests if you guys want me to check oscillators sound or something similar. I'd be more than happy to help.
Cheers!
bManic
[email removed]
lalo ·
Another betatester inside....i'm here 🙂
i'm excited about the new SM or whatever its name will be 😉
lalo
Wrote something here? To have a post removed or your name hidden, write to [email protected].