Technology

For somebody who has no idea about them at all:

When I was a kid in the 80s, a "synthesizer" was an electronic keyboard. Now, a "synthesizer" is a mess of knobs and buttons that looks more like a drum machine than a piano.

So, uh... my Q: "what's a synthesizer?"

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.

Cool project! Will it explain some of the related concepts like envelopes and ADSR? It might be nice to talk a bit about calibration/microtuning so it can match external gear. Also maybe some recipes for making sure a readers synth they build has a few basics to work from.

Honestly, latency/performance stuff. As in: how do VST synths ensure that they'll synthesize in time to keep up with the audio buffer, depending on user hardware. I'm asking because I've seen/heard countless VST synths fail at this and sound like a clicky mess, and I feel like if I understood how it's handled in code it would make more sense to me.

I'm a long-time software developer who at one point spent a lot of time on a software synth as a hobby project (never finished it as I realized it had fundamental design flaws). I'm also interested in making music (but still suck at it), follow various producers on YouTube and dabble with Ableton. Here are some things that puzzle me:

Latency seems inevitable, regardless of how fast your CPU or code is. Many algorithms simply require a certain window of input data before they can produce something. For example, an FFT with a window size of 2048 requires 2048 samples (~50 milliseconds) before it can react. Chain multiple such filters together and it adds up. In my hobby project I wanted to make a "reverse reverb" module (buffer data, reverse it, apply reverb, then reverse audio again to get an effect as if the sound is "arriving") and I could never wrap my head around how to do it. It could potentially add a latency of tens of seconds. How can we deal with this in the audio pipeline? It seems like for prerecorded or generated audio, it should be possible to consume data ahead of time to make the output come out at the right time. But all of the modules need to be synchronized so e.g. a drum comes out at the right time along all paths.

Typically analog synths have lower latency, but I don't understand why. Aren't they theoretically subject to the same limitations as a digital synth? Even an analog filter would need some kind of buffer to determine frequency. It's like Heisenberg's uncertainty principle but for sound. So how does that work, and how can we replicate the low latency of analog synths in software synths?

I lack an intuition about sound synthesis and it all seems very magical, so I wish somebody would help me untangle the relationship between what I hear and what the algorithm does. I mean it's easy to look up algorithms for producing audio, but I don't know how to apply those algorithms to incrementally work my way toward the sound I'm looking for in my head. As a developer I have an analytical mindset, and most producers I follow seem to go more on feeling (which is difficult to me). I have a hunch that a lot of what they talk about is just placebo, but I don't know how I would test that assertion. For example, there are people who compare the different sounds of Ableton's Operator and Serum, as if they are different beasts. But both are FM synths; it's the same maths behind them. So why would they have different sound? With all the FM synths that are out there, what are the things that actually separate them to produce different "feeling"?

In fact, speaking of FM synths, they are one of the biggest mysteries for me. I know what they do mathematically, but I need help understanding why someone chose to build a synth in this particular way and how they tame it to get the sound they want. It just seems like a really chaotic way to work for me, only slightly better than a random number generator.

Perhaps it would be interesting as a case study to try to replicate some of these commercial software synths by stitching together basic algorithms covered in the manual.

Hey that's great! Will it cover all types of sound synthesis (FM, substractive etc) or focus on a specific one?

What filter poles are and how they relate to cutoff frequency response.

This is something that confuses people and always needs good explanations.

Great work, good man!

This looks very interesting and I look forward to reading it.

Will this make me the next Aphex Twin?

"What should I attempt before deciding I need to roll my own?"

What language? I'm decent at C++. Plz no Python. I'm too old to learn that now.

Techniques to avoid aliasing. Difficult topic to do well though.

Any guide to make the GUI actually resemble a synthesizer. Having knobs and sliders don't seem to be enough, in my case.

Great project btw!