I learned electronics first but that's because I'm an old guy and audio DSP wasn't in common use in those days. You don't need to know electronics to understand DSP but in my case I tend to "visualize" the electronics in DSP code.
One of the nice things about DSP is it often behaves as almost "perfect" electronics. For example, a "ganged" potentiometer can easily be made with any number of channels with perfect tracking. "Gain" is exactly what you set it to be and is not affected by tube/transistor beta, temperature, component tolerances, etc. We actually have to work to make DSP non-linear to create things like tube and transformer distortion, etc.
At the risk of sounding too "simpleton", it is entirely possible to develop useful DSP plugins without much math at all. Most of the basic building blocks (EQ, delay, FFTs, etc.) are all well-established code in public domain. Put the blocks together to form some desired function.
Once you get the general hang of DSP then you can dive deeper into the math and other details; create your own EQ algorithms, etc. In the meantime, just get started!
One of the nice things about DSP is it often behaves as almost "perfect" electronics. For example, a "ganged" potentiometer can easily be made with any number of channels with perfect tracking. "Gain" is exactly what you set it to be and is not affected by tube/transistor beta, temperature, component tolerances, etc. We actually have to work to make DSP non-linear to create things like tube and transformer distortion, etc.
At the risk of sounding too "simpleton", it is entirely possible to develop useful DSP plugins without much math at all. Most of the basic building blocks (EQ, delay, FFTs, etc.) are all well-established code in public domain. Put the blocks together to form some desired function.
Once you get the general hang of DSP then you can dive deeper into the math and other details; create your own EQ algorithms, etc. In the meantime, just get started!
Statistics: Posted by Fender19 — Sat May 04, 2024 5:52 am