The VCV VCO and VCV VCF modules are over 8 years old now, so I decided to rewrite their DSP engines. They’ve received massive quality enhancements without significant changes to their behavior, for backwards compatibility. See the full details in their changelog.
Feel free to build them from source and try them before they are released, and let me know what you think.
What about the wavetable vco or the lfo modules? Or are those not in need of an update internally?
Awesome! Nicely done.
Nice!
Does the VCO still sync on the falling edge of a unipolar trigger? For a bipolar trigger it fires on the rising edge. It would be nice if it triggered on the rising edge of both unipolar and bipolar triggers.
For the Venom VCOs I default to a Schmitt Trigger going high at 2V and resetting at 0.2V, which works well with both unipolar and bipolar triggers. I have an option for the Schmitt trigger to go high at 0V and reset at -2V, which only works well with bipolar triggers, but sometimes is desired for proper phase alignment.
I’ve significantly revised the VCF model/solver. Commits · VCVRack/Fundamental · GitHub
If anyone would like to test the sound, stability, performance, backward compatibility, similarity to the old transistor ladder model, etc here are builds.
https://files.vcvrack.com/packages/Fundamental-2.6.5.rc1-mac-x64.vcvplugin
https://files.vcvrack.com/packages/Fundamental-2.6.5.rc1-mac-arm64.vcvplugin
https://files.vcvrack.com/packages/Fundamental-2.6.5.rc1-win-x64.vcvplugin
https://files.vcvrack.com/packages/Fundamental-2.6.5.rc1-lin-x64.vcvplugin
I tested the VCO and found a significant change in the sync behavior.
unipolar (0-10V) signal no longer syncs the VCO. It only syncs on the leading edge of a bipolar signal.
Old behavior the VCO synced on the trailing edge of a unipolar signal, and leading edge of a bipolar signal.
I wish the VCO used a Schmitt trigger that went high at 2V and low at 0.2V so both unipolar and bipolar signals synced on the leading edge.
But either way, I think there should be an option to restore old sync behavior.
I’ve done a quick & dirty adaption to my pole mixing filter, this looks like it’s working. A previous iteration I was trying with newer VCF code had issues with pole mixing, I think that’s resolved here. The changes also seem to have a positive effect on resonance: I can do a bandpass limited resonance feedback and that appears to work:
// Resonance feedback into the input, one sample delayed.
//T u0 = xOversampled[n] - frame.resonance * previousY[3];
T u0 = xOversampled[n]
+ frame.resonance * previousY[3]
- frame.resonance * previousY[2] * 2
+ frame.resonance * previousY[1];
Guessing that may be due to the oversampling? Anyway, initial impression is this looks very promising!
But Andrew is talking about changes he made to the VCF, not the VCO…
Yes, he did only ask about the VCF. But I looked at the posted commit history and noticed changes to the vCO as well. I’ve had issues with VCO sync in the past, and wondered if that improved. I tested and saw changes, but IMO the new sync behavior is worse. I thought it was better to raise the issue now than to wait for release.
Hi, I’m glad to see changes on core modules.
I realized recently that VCV VCO is not pure, so I use Bogaudio VCO now.
I noticed that was planned on the changelog : “Make sine output pure (-103 dB THD) instead of quadratically-shaped with harmonics.” for 2.5.5, but I use 2.5.6, and it’s still not pure.
It would be great to have a place to put suggestions on the forum, because I’ve used VCV Rack for a while, and I do have some.
We should have a shortcut for cut and connect. So you delete a module, but the cables connect and become one, that would save a lot of time. It’s available on Blender, when we build shader nodes.
Overall, it would be great to have more parameters, more custom shortcuts, it feels a bit empty on customization of the UI and workflow.
It would be cool to right-click and select “selections” to have a preview of the groups of modules we made with “save selection as…”. A more intuitive usage of blueprints basically.
An option for cutting frequencies below 20 and above 10K would be nice to protect ears. I’ve hurted myself a lot of times connecting cables the wrong way, before learning to setup a global EQ.
Anyway, thanks for that amazing software, I’ve been hooked for weeks.
Welcome to the forum and to VCV Rack! For feature requests and bug reports, please contact us at VCV Support. We generally prefer that you submit separate support tickets for each bug report or feature request because it allows us to respond to each one more easily and to track them individually.