From the original SynthMaker forum (2004–2014), with its members’ names and dates.
electrogear ·
Too much to learn! Too much flitting about from one topic to another! Not enough production!
Time for an SM rethink!
Here is my plan:
1: Read Sound-On-Sound's 'Synth Secrets episode 1 - 63. 2: Learn assembly language 3: Learn some more about SM modules and functionality 4: Learn some more 1 - 4: Develop some pretty GUI's 5: Come back and kick some ass
Don't know why I'm sharing this with you, just a little insight to my weird, twisted, slightly demonic brain.
Bye...
For now! :P
oddson ·
Some might disagree... but I say skip step two for now (and the foreseeable future).
infuzion ·
oddson wrote: Some might disagree... but I say skip step two for now (and the foreseeable future).
I would agree with oddson's disagreement; I only got into SSE because I learned ASM like 20 years ago, & I want to release commercial-quality VSTs. If you're releasing freeware, Code is much much easier to maintain. If they write in complaining about the CPU usage, tell them it would be a $50 donation, & send the Code & half the donation to me for ASM slimming 😉
Honestly, start with an idea for a VST(i), chop it up in smaller ideas, then learn the SoundOnSound episodes & other net-lesions on how to do each idea segment. You can even do mini-releases with those idea segments if you wish.
I learned SM just by hacking others' OSMs. I read 3-4 of those SoS PDFs, but I knew quite a bit of synths from reading 20 years of mags.
matti ·
infuzion wrote: I would agree with oddson's disagreement
+1
Even tho ASM is great and SSE is pretty straight forward, it still is a lot more work than writing things with "code". In other words; You get more done in less time! Which is ofcourse good for the learning process.
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker