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.