MIDIāCV module (and surely other MIDI-based VCV stock modules): ālast knownā MIDI controller device, restored when the MIDI controller is connected (in case you disconnect, then you reconnect it later).
This may be related to your idea, but I was wishing to be able to create custom keywords or identifiers that I can remember.
So often Iāll remember what a specific module does and (usually) what it looks like, but for the life of me I cannot remember the name of the plugin it belongs to.
Even being able to restrict a search to āFavouritesā is not quite enough, since there are so many.
Also, it is difficult to recognize the dark appearance of a module, when I almost always prefer the light version. The module browser doesnāt stick to the āUI Themeā preference.
The module browser uses the current settings, then caches the image previews. Modules generally follow āPrefer dark panelsā and not the Rack UI theme.
The website previews are always generated with āPrefer dark panelsā off and the Light UI theme.
This is just something thatās been bugging me forever, and not life-or-death, but: change the text in the Update notification box to read āRack will now automatically restartā, instead of āPlease restart Rackā⦠the very first time I updated the Library, I assumed it needed me to manually restart, and it freaked me out a little when it just did it, w/o any input from me.. brand-new users might appreciate not having that mismatch between the text and the behavior.
Yeah and if youāre too impatient and restart Rack manually before the first one has restarted, then you have 2 instances open and then nothing works , well on Windows at least, I donāt know if its the same on Mac.
Thereās code in the Rack main startup code thatās meant to prevent two instances running on Windows, so youāve managed to hit a race condition where that mechanism doesnāt work.
It might be a silly idea, given that in the world of modular synthesis, everything is managed through Patches, but Iāll throw it out there anyway:
Once a Patch is generated, it would be nice to be able to save some āPresetsā correlated to that Patch as if it were a standalone synthesizer (with arrow icons to switch between āPresetsā).
I know this can already be done with Patches themselves, but each time VCV Rack must reloads all the modules and their states, whereas with āPresetsā it would just change the modules state and thatās it.
Therefore, it would be much faster to cycle through āPresetsā instead of having to click āFile - Openā every time to load a new Patch that have the same modules but with different settings / states.
As is so often the case, Stoermelder has you covered here I think. Several modules in his collection will effectively let you set up āpresetsā for a whole set of modules.
It looks like you have to manually map every parameter of every module.. i meant something more immediate like click on āSave Presetā and give some āPreset Nameā
There is one (though presently I forget its name) which loads module presets. Youād still need to visit each module in the patch, at least each one whose settings you want to change. But better than mapping every param independently.
There is also transit, which can work on entire modules at a time, and smoothly change their params between āsnapshotsā. That might be an option as well.
Yep, your suggestions are other two additional workarounds. Thanks
Imho, such a solution integrated directly into VCV Rack would be perfect, like normal synth.
Ideally, it must compare after the Patch is loaded obviously, because Presets must be correlated only to a Patch (that became like a Synth), and each Patch/Synth has its own Presets (only the save/delete option will be available, because the loading can be automatic as the presets will be saved all within the patch file as an atomic entity).
An example of what i mean (with the arrows you could move from one saved preset to another):
Or maybe, if someone (an Angel ) are able to implement a module capable of doing this without the need to touch the other modules in any way.
I donāt want to bore you, itās just an idea that in my opinion, especially in the case of Plugins versions of VCV, can be really useful..