I am working on my first VCV Rack plugin module- Meander. This is an attempt to duplicate a Windows app that I developed over the years and that I use in my music performances. For examples from over the years, see https://soundcloud.com/cyberpunken . This VCV module is once again primarily for my own use, but depending on how it works out, I will release to open source eventually, and assuming interest.
Attached is a screen clip of my module in Rack, in its very crude development phase, trying to get the panel layout frozen before I start adapting Meander source code to Rack. As you can see, Meander is an 80HP module at present with approximately 80 params, including buttons. My question here is what might I expect in terms of CPU load with this many parameters and quite extensive source code? Also, how often (in milliseconds) is process() called per module, and is there a limit on how long the code can run before experiencing problems? Most of the code is setup related, such as defining scales and keys and circle of 5ths harmonic progression steps and patterns. But, there is a significant ammount of code associated per process() call to determine the harmony,. melody, arp, and bass notes to play.
Lastly, in Meander for Windows (and for Max/MSP), I create an event queue which I populate “off beat” so that I have the notes figured out before they are needed. Then on the beats I process the event queue and play any notes that are due, based on system time. Has anyone created an event queue in a Rack module?