Absolutely - that is also a key feature of my Rhythm Explorer module. In a similar way it saves the pseudo random number generator seed so you can return to your happy discovery when you reopen the patch. I also provide the seed value as an output so it can be stored in something like the Impromptu CV-Pad. You can store a whole array of interesting seed values and call them up on demand.
Another nice feature that I also implemented in Rhythm Explorer. The Run button normally toggles the run state. But the Run CV input expects a gate, not a trigger. If the Run CV is patched and low, then the Run button momentarily turns the sequencer on. If the CV is high then the Run button momentarily turns the sequencer off. I agree, it is a nice performance tool.
Back to PUSH - I’m still surprised the Hold button responds while the Hold CV is high. I don’t have a problem with it, just surprised.
My main use case is converting bipolar to unipolar, or vice-versa, followed by scaling. As long as the offset is done first, then the offset amount remains constant, regardless what amplification/attenuation you use. But if you do the offset after ward, then the offset has to change as the scale factor changes.
I agree, it is a nice feature. (and even better with CV inputs!) I agree the wave folding is naïve, but I still think it is useful with anti-aliasing. I have been toying with the idea of creating a Venom module that does offsets, scaling, clipping/reflection, etc. for a while. I have mocked up the features with existing modules - predominantly Recurse and WinComp. The WinComp has oversampling available, and it can make a huge difference in the wave folding result.
Here is a quick demo showing how my mockup gives nearly identical results to RSCL when oversampling is not engaged, as well as the dramatic improvement when it is engaged. It is amazing what a difference x2 oversampling can give. WinComp goes to x32, but I didn’t bother going past x2.
Venom vs VCV Wave Folding.vcv (3.9 KB)
