I’m Gregg and I’m a long-time electronic musician, a designer, and a developer, and I’m happy to announce a collection of modules I’ve been developing for VCV.
The first group is called acModules and are mostly made to fill gaps that I have had when making music in VCV and I couldn’t find existing solutions. Or, sometimes, I just make the modules because they’re fun, and it’s fun, and I like fun.
The “ac” in acModules is for my personal hobby brand artificialcolors, which I’ve used for all manner of random things over the decades, therefore you’ll find the modules under the artificialcolors brand in the VCV library.
There are currently five modules in the collection, with a sixth in the pipeline, and I’m sure I’ll add more as time goes on.
This is a software clone of my hardware sequencer which I have made versions for MIDI, modular, and my custom synth, the Wygonium GB01 (which is a reinterpretation of the Trautonium synth from the 1930s, complete with touch+pressure sensitive ribbon controller). More info on this project can be found here: Wygonium Synth Info | Wygonium Info
I hope others find the modules useful or interesting, and I’m always open to feedback and suggestions.
I like the concept of your modules. But, I’m curious why the ChordRoy module root note input is not in v/oct format. As I was trying out Pick6 with other modules (such as my Meander module), I found that I could not send the Meander chord root to ChordRoy without a translation module such as Basically.
V/oct root note is actually coming in an update! It will be an option in the context menu, and probably submitted to the library next week. Though it probably wasn’t the best choice, the current/first version met my workflow needs at the time, and so I went with it.
I guess I should clarify that V/oct is coming for this one particular input; all other note-related input/output features already adhere to the voltage standards.
Well that’s not good! If you’d be kind enough to log an issue on the module’s github ( https://github.com/gwygonik/ORBsqVi/issues ), with all the usual info (platform, etc), I’ll dive into it and see what we can do!
Thanks. I added to the GitHub issue to ask that you include the log file there (and I gave instructions where you should be able to find it).
I do test on Mac, Linux, and Windows, but I know that just because “it works on my machine” doesn’t mean it works everywhere Happy to dive into problems with the right info.
2.0.4 is in the library now for both acModules and Wygonium modules.
acModules
Found that a couple of the modules were crashing (sometimes intermittently) on multiple platforms when there was no audio interface selected. This has been fixed/worked around.
Chord4Roy now has an option for V/Oct root note selection from CV input, and a “PianoMan” mode which outputs piano-style chords instead of guitar-style ones. Sometimes I want this.
Pick6p now has options to copy/clear the custom patterns
New Module: Merc8or - project (get it?!) one CV range to another range, visually, and without the need for math. I made this because sometimes I want -5V to 5V to go from .24V to 1.53V and you try doing that quickly with attenuators
New Module: Pul5es - send a trigger out after a set number of input triggers. Or send a trigger out except for after a set number of input triggers. I use this to sequence muting and unmuting mixer channels in odd timings (not a simple clock division), but you could do almost anything with it (as long as that involves sending triggers at specific intervals).
New videos coming soon, and one more new module in the works, but will be another week or so.
Wygonium ORBsq Vi
Added options to control whether or not each of the three step types drift or remain static.
Also a new option to reset drift cycle on reset trigger input
Fixed same intermittent issue as acModules when no audio interface selected
Yes, I have read the manual before. There is a section you are not quoting that is about pitch and volts per octave. Admittedly it’s a not completely un-ambiguous, but every VCO I’ve ever seen uses a bipolar CV, where 0V is C4. You are course free to make whatever you want, but that’s what 99% of the users will expect.
I don’t think there is a VCV ever made (I could be wrong!) that wraps at 10V and 0V. Again, it may be a great innovation, and your are free to make such a thing. Enjoy!
Ah. There might be some confusion there as this module isn’t a VCO. The CV input just picks a root note (instead of using the knob) and send out guitar chord-tuned note CV. And since it’s guitar-oriented, there isn’t the full range of octaves as on a piano, thus the decision to treat 1 V/oct from 0-10V as picking the root note only, with no concern for transposition or anything. The wrapping would just be for convenience, should someone want to send in negative voltages.
Thanks for considering this. I know from my Meander module that it can be complicated trying to mix CV knob control and v/oct knob control (parameter value). Unfortunately, for me, not supporting negative v/oct limits how I can use Chord4Roy. For some testing I just set my Meander chord octave up a couple of octaves so I would not send any negative chord notes v/oct. Thanks again.
Thanks for the info on how you use it and where your pain points are.
It’s always tricky with modular because of the “well just put another module between your modules that does what you want” nature of things; one all-singing all-dancing module is rare (at least in hardware). And, I mean, part of the reason I made Merc8or is because sometimes I want my own modules to output something different and all the other attenuverters weren’t to my liking.
Thanks to this sub-thread, I’ve already incorporated the wrapping of negative voltages into another module I’m working on that uses V/Oct for parameter selection, and I’ll move this over to Chord4Roy shortly.
It will be an option in the context menu, and probably submitted to the library next week. Though it probably wasn’t the best choice, the current/first version met my workflow needs at the time, and so I went with it.
If you’d be kind enough to log an issue on the module’s github ( 
