v2.6.0
- Octaves VCO
- Initial release
- Misc
- Better default values for ADSR and Burst
Poly PonyVCO and Burst were both a big yay!
Now the Octaves as well. Nice!
And extra compliments for the to-the-point module naming.
Octaves has a wicked amount of aliasing. Is that intentional? Looking on a scope it looks like the waveforms have the telltale spikes indicating antialiasing has been applied. I can also see the band limiting on an analyzer. But it doesn’t seem to be controlling the aliasing. Or maybe that is what “A harsh and funky take of an additive Oscillator.” means? Does the hardware sound similar when isolating the highest frequency output?
Hi Dave, it’s certainly not intentional! There is oversampling in place but on reflection I think the default setting (x2) is not sufficient. I had experimented with ADAA for the implementation (effectively each square sums with a hard clipper between each sum), but didn’t get satisfactory results.
The hardware is analog (triangle core into comparator) so will not alias but it does sound incredible harsh (especially when base frequency is high). But there is (tonal) harsh and (atonal) aliasing and clearly the first is what is desired. I’ll certainly revisit the default settings, but also look at if the antialiasing can be improved otherwise. At x8 oversampling the CPU is 6% on my machine which feels high, so maybe x4 is a compromise.
Green naive, pink x4 oversampling. (currently default is x2 oversampling, not shown)
If you or others are interested, could we continue in the dev thread? Befaco modules development blog - #234 by hemmer
Well done sir!
Just a heads up: Noise plethora’s bank select seems a bit wonky since the update. When I press the bank select knob to switch banks, the bank I’m switching to automatically changes to the program of the bank I’m switching from.
Yup, can confirm that when clicking on the knob the newly selected bank then changes to the current knob position.
In the previous behavior it would only change setting as you turn the knob (although it would jump to that new position).
I think the behavior should be however the hardware works (I don’t own it so I can’t say).
Confirmed, just an overzealous backport of some fixes for 4ms metamodule version! Will push a fix to the library tonight. Edit: pushed
v2.8.1
v2.8.2
In the library now!