I also took some time to improve the manuals web site. Now every module has some documentation. If you find any mistake, let me know. Vult Modules
The last update contains a bunch of small fixes. There should be some performance improvements thanks to the latest Vult compiler. If you notice a breaking change let me know.
The new binaries should be available in a couple of days.
Can’t wait to add these to my rack! Which premium collection is getting the new module, just “vult modules” or compacts? Planning on buying both bundles this Black Friday but I’m just wondering ahead of time
Awesome sauce Leonardo, and they already hit the library. Was great to read your blogpost, very inspiring. Looking forward to playing with the new stuff.
I’m most impressed with the labeling on Quantum, lol! I find Overon really nice, especially for a layer on chords. Remember it’s fully poly already in VCV.
The ARP filter quickly became one of my favorites as well in hardware. I had to make a model of it. It took me some time. But I finally nailed a nice and efficient model.
Here are some pictures of my hardware version. It was a quick prototype and I built only one to make measurements.
Very cool to see hardware and software that look and work the same way. I know you have your own programming/simulation language for DSP. Do you use it to develop hardware modules also? Or is the language to emulate hardware in the first place?
I use the Vult language to do both hardware and software. All the DSP code of all the Vult, the DotCom and VCV Drums is written in Vult language. That makes easy for me to target it to different platforms, like Voltage Modular or hardware.Caudal, Freak, Anima and Feigen use microcontrollers running the same DSP code I wrote in Vult language.
But I also have other tools I use to make modules, both hardware and hardware. In the blog post I show my “panel designer” which is a tool that runs a LISP-like language I developed called Marabu. With that language I can describe the panels, including the graphics and the components for a PCB and generate the VCV Rack glue code for the DSP, the fabrication files for the PCBs and panel, and also VST code.
In the case of the ARP filter, first I made the panel in the Marabu language. That exported the PCB for the controls and I created manually the actual circuit board. Then I started the modeling process, which was analyzing the circuit and creating simulation models of the components I did not have, like the Norton op-amps. For the actual modeling and simulation I use Wolfram System Modeler, which is the tool that I professionally develop. Then I refine the simulation model until I get a good tradeoff between efficiency and accuracy. Here it is where many models get stuck. In the case of the ARP filter it took me a couple of years to come up with different attempts, until I got a good and efficient model. I have a blog post with where I show the process for the 808 kick drum in the Drum modules https://blog.wolfram.com/2020/07/23/digital-vintage-sound-modeling-analog-synthesizers-with-the-wolfram-language-and-system-modeler/
Once I have the model, implementing the DSP code is easy. I have one simulation engine that I call the VSS (Vult Super Solver) which is a solver that I have been developing for the last 6-7 years (since I started making VCV Rack modules). I will be using the new solver for other filter that I have re-modeled.
Hey Leonardo, at first many thanks for the new modules, the SEM is one of my alltime favourites. Sadly the main audio outputs at both Overon Versions produce only clicking sounds. The scope shows, that the clicks are exactly at the times of the external gates. Only when I use the saw/pulse outputs, there is the real audio signal and only if connected with the ext1/ext2 inputs of the internal mixer, the audio signal is also present at the main outputs. I checked the video from SATURATA MODULAR on youtube and there Overone behaves like it should. Am I doing something wrong?
Cheers!
Silly me, should have red the manual for the mixer, which says “At the center the oscillator is silent.” Now I get audio signals where they should be. But in my opinion this isn’t a crossfade but an attenuation because you don’t blend between both waveforms, you just change the amplitude. A real crossfade would have the one waveform 100% left and the other 100% right, and in the middle that would be 50% each and not both at zero.
It happened to me a couple of times. That’s why I made the initial patch with the oscillator 1 in full volume. I’ll fix the manual to remove the crossfade part.
Now I get audio signals where they should be. But in my opinion this isn’t a crossfade but an attenuation because you don’t blend between both waveforms, you just change the amplitude. A real crossfade would have the one waveform 100% left and the other 100% right, and in the middle that would be 50% each and not both at zero.