Cherry Audio Forums

A side note on CPU usage - generating partials using Chebyshev polynomials is somewhat cheaper than generating independent sine waves for each partial (plus I cheat a bit on the sine wave, using a good-enough approximation function) which enables Chebysynth to pump out 1280 simultaneous sine waves (...

Chebysynth is a polyphonic synth rather than a single harmonic oscillator, and might not fit the bill; however there is also Chebz , which took inspiration directly from Squinky Labs's excellent Chebyshev module for VCV, and which can also be demoed for free: chebz.png I don't have experience with t...

Chebysynth may also be of interest here - a polyphonic MIDI synth with envelope-controlled modulation of 9 partials:

My basic attitude is that doubles passed between threads in VM are mostly like network packets representing individual bullets in an online multiplayer FPS: it doesn’t really matter if occasionally one gets dropped or arrives out of order. Besides the concern about transporter malfunctions causing t...

I didn't want to handle anything in the timer thread as it updates at too low a rate For audio processing, I agree. But do we need to be pushing updates into the UI any faster than once every 50ms? The way I'm picturing this is that, within a given module, there are at least three schedules running...

Is internalSetValue() ever called from ProcessSample()? This is the sort of case where I'd want to send a non-blocking signal that there was a new value from ProcessSample() and respond to that signal in a less time-critical thread. Since value is marked as volatile it can be set atomically, so one ...

Yes, if you are accessing an unsynchronised collection both in ProcessSample() and in Notify(), you may well run into thread-safety issues. It's not necessarily a good idea to deal with these by synchronising the collection, since that involves placing locks around read/write access that might stall...

SetValue() on VoltageAudioJack is marked as native (GetValue() is not...)

One other thing I tend to do in ProcessSample() is grab all the values I'm going to use (samples from input jacks, smoothed knob values etc) at the start of processing and build up a "frame" that represents a snapshot of state for the duration of that sample - the sources for all the value...

It does make for a more complicated programming model, but the general rule is to treat all the UI components as a separate source of truth from the internal state of your processing engine: take advice from them about what's going on out there in user-land, and let them know when you want something...