Hey guys, I’m writing a user manual for some software I’m publishing. It’s a software synthesizer design toolkit, for making your own software synthesizer in your programming language of choice. Of course, in order to make your own synthesizer, you must know how one works.

My goal in writing this user manual is not only to document my code, but also to teach how synthesizers actually work, so that anyone can make their own. That’s where this post comes in. I need inspiration on what exactly it is people don’t already know about them, and what all the hot topics are.

I’m happy to actually explain these things in the comments below!

  • wootz@lemmy.world
    link
    fedilink
    English
    arrow-up
    8
    ·
    1 year ago

    Are you sticking to only softsynths / digital, or also going into analog?

    I ask because I have previously struggled with explaining why plugins and dsp stuff works the way it does (why is “saving my settings” called a patch?) without going into a long winded history lesson.

    Either way, super cool!

    I think I know a fair bit about both the history of synths and how they work, so if you need someone try bounce ideas off of don’t hesitate to write.

    • lofenyyOP
      link
      fedilink
      English
      arrow-up
      4
      ·
      1 year ago

      Thank you so much for the offer! I’ll mostly stick to soft synths, but I don’t mind going into the history a little bit to explain terminology and whatnot. There’s a surprising amount of overlap between analog subtractive synths and software subtractive synths anyways.