Ahh, another more likely possibility is the old compiler sees the variable assignment, but doesn’t detect it is conditional execution, so runs the risk of failing to detect potential use of uninitialized variable. Not an issue with my code, but I can see why the compiler developers might tighten things up.
yeah, I think you are right. I can tell you that as a human it is difficult to see that it’s always initialized in the cases you care about. But I agree it looks correct, but of course a sensible person would just initialize the variable where it’s declared and make the warning go away 
1 Like
I just realized my Recurse and Recurse Stereo modules are actually implemented via iteration, and not recursion. Regardless what the implementation, the end result should be the same.
Question for the community - Should I change the name to Iterate? Or keep it as Recurse?
Besides being closer to the truth, I’m thinking iterate might be more meaningful to the average user.
My thoughts: there is a module called “Pamela’s New Workout”. I have yet to see it improve my cardio numbers or BMI, and I’m starting to suspect there is no actual little person named Pamela inside it. So precedent has been set; call it what you want!
7 Likes
I do enjoy reading the disclaimer in their literature!
what’s about “recursed iteration”
tbh I’m with Don, just call it what you want.
1 Like
Thanks both of you. It shall remain Recurse!
Besides, I was being silly. If Return is patched, then indeed it truly is implemented via recursion.
Only if Return is not patched (Return normalled to Send), then it is implemented via iteration.
1 Like
Well now I have done it! I submitted Venom Modules for release to the library. Hopefully I followed the process properly and it is approved and released to the library soon.
Binaries for the release candidate are available at Release Release 2.0.0 · DaveBenham/VenomModules · GitHub
15 Likes
I was asked to change my slug/plugin name to Venom (drop Modules from the slug and name)
I also had to remove the hidden CVMIX. I’ve deleted all the old beta releases because they had the CVMIX within.
If you want the new binaries before release to the library, they are available at Release 2.0.0 · DaveBenham/VenomModules · GitHub
If you installed the old beta with the VenomModules slug, then you should delete the
<Rack user folder>/Plugins/VenomModules folder.
4 Likes
Win 11 - Loading Vermona preset in the new binary rhythm explorer crashes Rack and Rack VST/CLAP.
1 Like
Same here win10 rack free v2.2.3.
1 Like
@Rodney, @tomwake - Thanks for the prompt report guys. I neglected to update the preset after changing the name of the plugin. I will fix and get a new release ASAP. Hopefully I can get the fix in the library pipeline before the bugged 2.0.0 is released.
1 Like
Bug all fixed, and version updated to 2.0.1. Hopefully this is the version that makes it into the library!
Binaries are available at Release 2.0.1 · DaveBenham/VenomModules · GitHub
9 Likes
You should announce your lovely collection has graced the official library, excited to test drive them!
2 Likes
Yes - I had been meaning to have some vids to introduce module features and uses to go along with an announcement - But I kept on getting lost in possibilities and never got anywhere 
I’ll create a simple announcement later today.
8 Likes
Thanks! Danger Mode activated!
1 Like
Ooooh! Videos with use cases is mad sexy!!
1 Like
Hey Dave, sorry to necro this thread but I have one small request for the Benjolin model. Would it be possible to add a voltage offset parameter to the XOR so we have a way to control the “pulse width” of the output? I’m loving the properly oversampled Benjolin module and there isn’t another XOR module that has as little aliasing as the built-in one.
Maybe I am misreading, but just to be sure:
The XOR output on the Benjolin is not a “pure” XOR. It is an XOR of the internal shift register and osc 1 which is compared to the pulse signal of osc 2. In other words, it is the output of the comparator: not the XOR function. You can though offset the XOR and change it by adjusting the Pattern knob on the module.
Also: I believe @DaveVenom has a logic module now with oversampling
1 Like
Yes, @koen.kaptijn has that pretty much correct. Rob Hordijk called the output XOR, but it is not a useful XOR operation that you can take control of. It is simply the first bit in the shift register, which is the result of the data input (1 if Tri1 is > pattern value, else 0) XORed with the value that is shifted out of the shift register. It is slightly different if Chaos is enabled, but that does not matter. Also, the XOR output is only updated when the Rungler is triggered by the clock (Pulse 2 by default)
BTW - the pattern value used in the comparison is effectively the offset that you are looking for. But the Benjolin is intentionally chaotic, so you are unlikely to perceive any controllable pulse width. And it is not continuously updated, as stated before.
And my Logic module has the oversampling option for all of the logic gates. You should try that. As with all my modules, you should definitely read the manual to take advantage of all the capabilities. You are likely to miss important features if you don’t read the manual.
3 Likes