Finally got a chance to make and push HetrickCV 2.2.1 (build available on the repo in the next minute or two). As mentioned above, this adds a new XOR/Direct switch to control the feedback behavior. It took two months for me to find free time for this, so thanks for your patience! I’ll submit this to the library. In the meantime, let me know if you find anything weird with the pre-release build.
EDIT: 2.2.0 and 2.2.1 feature a new polyphonic Probability module. This patch is extra fun:
Nice!
That Probability module looks to be nearly identical in function to a Bernoulli Gate - or am I missing something?
It’s pretty similar, but I added a few modes. B Prob is the standard Bernoulli functionality where the knob sets the probability for the B output to fire. Alternate mode is also present (although slightly hidden) on Audible/Mutable Branches where probability determines whether the current output changes. Independent mode is a new mode where the Probability knob determines the probability of both outputs (so both outputs can actually fire simultaneously).
Likewise, the right control lets you choose whether the outputs are toggled, gated, or triggered.
It’s a bit large for the functionality, but it’s nice and readable instead of using the LEDs like Branches.
You still have tiny LEDs, but I guess you mean that the pushbutton is large enough? I do confess I hate trying to click on tiny LEDs (I’m talking about you, Bogaudio!)
Sorry, I forgot that Branches doesn’t have LEDs for mode: https://pichenettes.github.io/mutable-instruments-documentation/modules/branches/manual/
In Branches, the way to tell that you are in Latch mode is that the output LED never turns off (and this might be tough to see if you’re using rapid or wide gates). You can’t tell that you’re in Toggle mode unless you test the behavior of the outputs. The idea behind the Probability module was to not only add the Independent mode, but to make the active mode visible at all times.
Nice! oh, btw, the panel on rungler looks like there are some small mistakes? Like the black background of the “Out” is almost running into the word “direct”, even though there is plenty of space. Likewise the LEDs next to 1, 2, 3 have very thin black borders to their left - again for no reason. And the bottom part kind of crows your “brand logo”. There’s plenty of space to move all the the bottom stuff up, esc if the vircial spacing is reduced a little.
But I’m no graphic designer, so feel free to ignore 
Can you please explain this in further detail? I want to do something similar in hardware using a CV mixer, but I’m unsure about the ratios (by that I mean the “weight” of each bit). For instance, if I patch an 8V gate into, let’s say, bit 6 of an 8-bit DAC, what should come out? Many thanks in advance!
A DAC has a resolution of 2^n-1 steps, where n is the amount of bits. So for 8 bits this is 255.
The weighting or ratio between the bits follows the same principle, where each bit is 2:1 higher:
1bit = 1/255 2bit = 2/255 3bit = 4/255 4bit = 8/255 5bit = 16/255 6bit = 32/255 7bit = 64/255 8bit = 128/255
So when all bits are used, you will get the maximum amount of 255.
So, in your example:
if 255/255 is 8V, then the 6th bit will be: 8V*32/255 = 1.003921(etc) V
Edit: In the Benjolin, or the Rungler, only the 3 last bits are used, forming a 3bit DAC. The ratio of this is: 1/7 2/7 4/7
Thank you so much!!!
The Benjolin V4 Pony Matrix Demo is just astounding to me. And for me, I kinda see it as a masterwork and am in awe of it. Can’t thank you enough for this instrument. And the presets are so great so it’s great as music as well!
Wow, thanks!
I frequently find myself returning to some flavor of the Benjolin patch - I am always entertained.
I may try to replicate the V4 preset sounds with the latest Benjolin patch that uses the Venom Benjolin Oscillator. That would be an interesting experiment.
That would be fantastic!
Here it is - I adapted my most recent Benjolin version that uses the Venom Benjolin Oscillator to use the matrix mixer and programmed all the same V4 Demo settings into the Transit module. I did not bother implementing the automatic snapshot advance. You can manually select any of the snapshots. Of course it is not a perfect replica, but it is pretty darn close.
This is great! I’m so glad to have this version. Thank you!
I do have a quick question.
With this matrix version, it seems like my controller mapping is not compatible with the presets. Makes me wonder if there is a way to have my controller latch to the presets parameter position? As is, the dial settings get out of sync with the presets. My mappings seem to take over the dial positions.
There would have to be two way communication between VCV and your controller. I don’t know how that is done.
You’d need to check the controller’s manual, but it’s most likely just sending the cc back. These controllers have both in and out midi ports.
You could try and use Midi Cat by Stoermelder. It is similar to MidiMap by VCV but has some extra functionalities built in. There is a good manual on his github
Is there any MIDI CC mapper module that supports relative encoder values?
Many MIDI devices offer such a relative mode, like the Intech GRID EN16 encoder module, also the AKAI MPK Mini Plus keyboard. It only makes sense for endless encoders without visual feedback like an LED ring. Relative encoders send 7 bit numbers in two’s complement, representing postive or negative numbers as incremental values.
With encoders in relative mode there is no requirement for feedback to the controller, the module could simply increment or decrement the current parameter value starting from it’s current value.
I dabbled with a modification of the MIDI MAP module to recognize and support relative values, but didn’t get it to work reliably. Possibly some form of user input to select relative vs. absolute CC values would be required.
Thank you! Thats what I am using, but I’ll check the manual to see if I can figure it out.
