And I have the first cut of the final module for the upcoming release! The Mouse Pad design may change size, and/or layout, and/or options. But it is fully functional for now. Patches made with this version may not work properly with the final release.
I didn’t have time to make a video, but below is a patch that uses all 4 new modules for v2.10.
Here are the binaries:
I would love feedback on the design and functions of the Mouse Pad, and ideas for improvements. I have some ideas for changes, but I would like to hear from others first. I am really hoping to release in October, so time is pressing.
I am leaving for a flute retreat Thursday morning, and return Sunday. I am pretty sure there is no internet, so I won’t be able to respond until I return.
Hold down the Alt key (Option on Mac), and move the mouse to play the lead voice. X axis controls pitch. Y axis controls volume. Release Alt to go quiet again. I don’t have documentation yet. Feel free to experiment with the various options, and tell me what you think!
The new VCO Units provide the voices.
The Quad VC Polarizer functions as a VCA and mixer.
The NORS_IQ is not new. I use it to quantize to a non-octave repeating scale, as well as provide the polyphonic notes for the slow arpeggiator sequence created by the Poly Fade.
The NORS_IQ is not new for this release. It quantizes a non-octave repeating scale, and provides the polyphonic notes for the slow arpeggiated background voice created by the Poly Fade.
@DaveVenom heads up, I’ve been getting crashes with the teleporting patchbay (which is otherwise super neat btw!) lately. Seemingly it only happens when removing a bay module from the session, and I think it might only happen if they’re connected, I haven’t yet seen it with a bay module that hasn’t been assigned a friend. Here’s the relevant part of the crash log:
I have not had the crash from the vst, but I did once have a bay output refuse to send audio even while the menu looked like it was connected ok. Will let you know if I find a repro on the latter.
That is a known issue, and the fix is already in my latest dev build. Don Cross (@cosinekitty) was a huge help in diagnosing the problem. I don’t think I would have come up with a fix without him!
I hope to submit to the library by the end of this month. In the mean time, you can get the fix at
That build has all the new modules, enhancements, and bug fixes that I plan on releasing.
There is also a complete change log for the planned release 2.10.0
I am feeling ready to submit. My only hesitation regards whether I should add a slew limiter option (static low pass filter) to the Mouse Pad output. I prefer to use controls rather than context menu options, but there isn’t room for another button, and I don’t want to make the module bigger. I don’t think it is needed because it can be added via additional modules. But it might be a nice convenience.
hello. I would be perfectly fine without it, but submitting to the library would probably expose the module to more users, and you might get more real-world feedback, and adjust from there. The idea to generate cv out of mouse \ touchpad movement is genius, and probably there’s fairly hi-res data there, so it can be quite musical.
Thanks. After your comment, plus playing around a bit with a LPF after Mouse Pad feeding the V/Oct input of a VCO, I have decided to move forward without a slew limiter. I can always add one at a later date if there is demand.
I’ll give a couple days for any additional feedback and/or bug reports, but there doesn’t seem to be much coming.
thank you @DaveVenom !
all seems ok. I tried a LPF and seems to work ok to smooth movements.
but you should post, when you have time, your own example.
its always good to see/hear miracles directly from The Maker;)
big love for all your modules but especially for Benjolin and mr. Mouse.
first thing that I’ve tried was to map x to osc pitch and y to filter cutoff, with shift triggering a vca, and it’s a lot of fun) Shift is a bigger key so it’s easier to tap with two fingers, I’m like typing a morse code or something)
When I try and load some current racks, like Poly Fade Test 2 for instance, I get an error that modules are missing, like PolyFade and VCOUnit, but they are installed on my machine according to VCV Rack 2 updater. Any suggestions on what to check for this? Sorry for the interruption!
Did you close down VCV Rack and then reopen after you downloaded the plugin via the updater? The updater simply downloads the necessary binaries, but they only get installed during the startup process when you launch VCV Rack.
