Thanks for taking the time to test them 
and for your report
1 Like
I’ll test and report back when I get a little more free time (I’m a bit caught up at the moment).
1 Like
My bad, I didn’t put the correct docs in 
I trust and envy your ears, as I mentioned above
In this case, I will correct the docs.
Thanks for all the reports
1 Like
Iirc, I had another voice in b minor running which has a c# instead of natural c. The dissonance with Etesia pitch middle position was obvious. No perfect pitch or mutant superpower involved at all, haha… 
1 Like
I could, indeed, reproduce it and found some more interesting stuff around the issue:
-
Doesn’t need an LFO, anything patched to the Trigger input will cause it (I managed to get it using Marmora as well).
-
Can also happen when switching models with the trigger already patched and selecting one of those 6 OP models, even without loading a patch, if the selected model has not been passed when twisting the knob or modulating / setting the model using the black port.
-
I managed to make it produce cheeps, burps, growls…
Ok, cool; but why does it happen? Firmware issue: when the 6 OP models are selected without the trigger input patched the two internal voices are initialized with the selected patch as the module happily drones away; when the trigger is patched… not every voice is initialized at once; on paper (errr… screen ) looking at the code it should not be a problem… except it is. I suspect this can bite hardware as well.
Riiight… so, can it be fixed? I already did, please test using the latest Nightly and let me know if the problem is gone (or if anything odd was introduced :P).
2 Likes
Yes, my original problem is gone! 
However, because you said it can also happen if you switch from another model to one of the FM models, I tested this as well, and there the cheep-burp-growl is still there. For example, I set the model to “PhaseDist”, save and close the patch, reopen it and then switch the model with the knob to “6 OP-FM1” → Cheep!
1 Like
Thanks for letting me know So… that’s one problem solved. I’ll look into the remaining one soon, I’m bound to leave in a few minutes.
1 Like
I broadened the scope of the firmware fix and the cheep is gone when switching models after loading the patch from, say, “Dualwave” and using the menu to go straight to “6 OP-FM1”, and also, from “PhaseDist” using the knob, a new Nightly has been generated and is ready for testing, please let me know if the problem is gone
1 Like
Ha, fantastic, you made it! All cheep-burp-growl issues are gone! Thank you so much for your work on the module! 
One entirely different question: I tested the new Out-Aux crossfader and sub-oscillators a bit. I tried before, but for some reason only with the FM models, and the sub-oscillators are, I guess, less useful for them because the FM models don’t appear to support the low pass gate, so the sub-oscillators are just constantly droning, no matter if a trigger is plugged or not. But now I tested with other models that support the LPG, and those new features get much more interesting now!
Is the following correct:
- The Out output is not affected at all, neither by the cross fader nor the sub-oscillators
- The cross fader mixes the Out signal gradually into the Aux signal when turning the knob or applying CV, and at 100% the Aux signal is equal to the Out signal, especially the sub-oscillators are fully removed/silenced from the Aux signal
It would make the Aux signal the more interesting and versatile output of the two.
1 Like
I’m glad that problem is solved
Regarding the Aux crossfader:
Both your statements are 100% correct
1 Like
I made some changes to the way Anuli handles audio input and, also, how the module manages resampling: they make the module more CPU friendly when more than one channel is used; again, I would really appreciate if you kind people would let me know if the output is off or the input does not behave as you expect
The module with the changes applied is already present in the latest 9d4413c Nightly.
no oddity regarding audio in changes, that I can detect.
1 Like
Thanks a lot
I am still in a Mutants release cycle; but a slimmer, dual version of the Aion counter was requested and it was easy and quick enough to do… so it is now roaming the Monster nightlies.
“Aion Kairos”
Same options as Aion; just far slimmer; only two sections and no custom buttons (that was not requested; but those touch buttons are too big for the form factor and also… MetaModule is not really conducive to the way I handle them: it uses pngs instead of svgs).
Happy Halloween!
Create spooky (or friendly, or happy, or scary) sounds with the newly produced Funes Mark 2!
It is slimmer! It allows per polyphonic channel LPG control! It can load different custom data per polyphonic channel (just make sure to select the proper model using the Model knob beforehand…); want different Aux suboscillators for each channel? Can now be done! Want different chord banks? Send some voltages!
This completes the request by @MinorNoise and adds a few new features that weren’t requested; but made a whole lot of sense.
Looks-wise, the module uses the new aesthetic standard for certain LED groups, already used in some other modules, if you play with the Nightlies regularly you’ve already seen it; I find the new look a bit soberer and less loud.
The module will be available in the next release; but it is already making the rounds in the Nightlies!
I hope y’all enjoy!
14 Likes
Hi @Bloodbat, sorry for the very late feedback about Funes Mark 2. I tested a lot during the last days, and made a patch ( https://youtu.be/0jM4e_78vkE ) that uses many of its features.
The module is great and once I had connected everything it runs very stable under all kinds of modulations and when turning knobs.
However, I had a few rare crashes when I was patching. For example, in the patch of the video, if I detach the cable to the LPG decay input, Rack freezes for 3 seconds and then crashes. I tried to pin down the issue, and found that the problem disappears when I detach the cable to the trigger input first. It was also dependent of the presence of certain other modules in the patch even if they were completely disconnected, for example Sapphire Echo, but only if at least one Tap expander is added. Unfortunately, it was not reproducable consistently.
I have found one very simple case where I can reproduce a crash all the time:
Create a new empty patch in Rack. Add Funes Mark 2 and a VCV Merge module. Connect the poly output of Merge with the Trigger input of Funes. Change the number of polyphony channels of Merge (context menu) to a higher number. For me, it always crashes if I choose at least 7 channels.
Can you reproduce it?
I can only repeat the issue if I start with a fresh patch. If I, for example, do the same with a Funes Mark 1 (setting 7 polyphony channels), then remove the Funes, set the polyphony back to 1, add a Funes Mark 2, connect Trigger with Merge and set the polyphony to 7 again (or any higher number), no crash happens.
Maybe, the LPG decay cable disconnect issue is separate to this one, or they are somehow related?
In all cases, the Rack log file shows nothing about the crash, and the Windows event log only reports that Rack was crashing and the faulty module is …\plugins-win-x64\SanguineMutants\plugin.dll.
I’ve used a Nightly of Mutants from about 2 days ago.
I saw the video! Great piece 
I’ll look in the problems you report, thanks for letting me now
1 Like
@MinorNoise What is the system you’re running VCV Rack under?
1 Like
@MinorNoise I managed to reproduce it and, in my local tests, fix it (This could affect a number of my other modules as well, if the problem is what I found, so, thanks a whole bunch for reporting ).
I have triggered a new Nightly with the changes and it is ready for testing, please do let me know how it goes.
It’s all right discussing the bug and triage here; but if it is possible, let’s continue the discussion at
Better for my bookkeeping 
2 Likes
@Bloodbat Thanks for your feedback. I’ve moved all my replies to Github now. 
1 Like