Version 2.1.0 is now in the library. This was a bit of a monster update to get over the line, but very happy with the end result. The main update is Noise Plethora, but there are some bugfixes in there too.
In other “life” news, Very soon I’m about to become a father for the first time so will probably be a little bit less responsive for the next wee while (i’ll still be around now and then). I’m looking forward to soothing the baby to sleep with some freaky noise algorithms such as satanWorkout.
Changelog:
Noise Plethora
Initial release
Chopping Kinky
Upgraded to use improved DC blocker
Spring Reverb
Added bypass
Kickall
Allow trigger input and button to work independently
EvenVCO
Fix to remove pop when number of polyphony engines changes
Muxlicer
Chaining using reset now works correctly
Stereo Strip, in collaboration between DivKid and Befaco, has been added to VCV Rack. Some details/notes:
it is polyphonic so you can do neat stuff like have 16 voices all with different panning/levels
VCV is more standardised about voltage so e.g. (almost?) all VCAs close at 0 V and open fully at 10 V (the volume knob decal dots have been removed to avoid confusion)
the line level / eurorack level conversion doesn’t make sense in VCV, but I’ve kept the black switches as +6dB input boost and -6dB output cut.
there are a couple of things in the right click context menu
change panning law between equal power and linear, and linear clipped
option to disable soft clipping
option to toggle DC filter
the mute switch is clickless (slight vactrol like decay), and also supports the momentary behaviour
the soft clipping behaviour is there but might exhibit slight differences from the hardware
PonyVCO, a Thru-Zero Wavefolding VCO/LFO, has been added to VCV Rack. Some details/notes:
optional modifications relative to the hardware version include DC correction for pulsewave, pulsewidth clamping, and AC coupling for TZFM input (see context menu)
octave and waveform switches are “playable” (can be dragged)
Also in this release:
EvenVCO - Optionally remove DC from pulse wave output
StereoStrip - Address high CPU usage when using EQ sliders
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)
This was a bit of a monster update to get over the line, but very happy with the end result. The main update is Noise Plethora, but there are some bugfixes in there too.
