Unfortunately yes 
Fixed now. Thank you for testing and reporting, much appreciated!
2 Likes
Yep, works now.
1 Like
Fixed now.
That actually broke by this fix, this is the reason why it worked before.
1 Like
Yes, it seems that in your latest build any combination of encoder control and mouse movements work fine for my Master/Aux module faders even if snapEnable is true.
Thank you!
1 Like
I’ve finally submitted an update to the VCV Library. The additional items since the preliminary changelog are marked in bold. If you have any question, please let me know.
v2.2.0
Modules 8FACE, 8FACEx2 and 8FACE mk2 are now considered stable again. A new Safe-mode has been added, which loads presets into modules according to the supported way. This provides maximum stability. However, it may lock up the audio processing and cause stutters, pops, or other audible artifacts. This behavior is not caused by CPU overload but by fundamental design constraints in VCV Rack. The old behavior can be restored using Unsafe fast-mode, which will load presets more quickly but may lead to crashes or other issues.
New modules
- Module MIDI-CAT FINE
- New expander for MIDI-CAT, allows fine-tuning of MIDI CC parameter-mappings
- Module PANIC ROOM
- Restricts your modular space within Rack, making it impossible to patch outside of a defined area
Changes and Fixes
- Modules 8FACE, 8FACEx2
- Added stability mode setting and Safe-mode, which is the new default setting
- Modules 8FACEx2
- Fixed broken function on some modules (only 8FACEx2)
- Module 8FACE mk2
- Added stability mode setting and Safe-mode, which is the new default setting
- Improved robustness for expander +8
- Module ARENA
- Fixed broken loading of presets and loading from saved patches
- Modules CV-MAP
- Added mapping functions Map module (left) and Map module (select)
- Added color setting for mapping indicators
- Modules CV-MAP, MACRO, µMAP, MIDI-CAT, MIRROR, ReMOVE Lite, X4
- Added context menu option to report parameter updates to plugin-host (only in plugin-version of Rack)
- Module DIRT
- Added new defects Pitch, Crush and Dropout
- Module GOTO
- Jump-points can be multiple modules/a selection instead of a single module
- Nodule MIDI-CAT
- Added input-modes Snapped and Snapped (short/long) for CC and Notes for use with snapped parameters (e.g. “Steps” on VCV SEQ3)
- Added handling for MIDI System Reset message for resetting input-mode Pickup (snap)
- Added color setting for mapping indicators
- Fixed mistaken copy-over of 14-bit CC flag from previous mapping slot on CCs >= 32
- Fixed missing parameter updates after manual adjustment in some situations
- Fixed broken MIDI learning for CC 31
- Fixed broken Locate and indicate mode
- Module MIDI-CAT MEM
- Added module restriction list
- Fixed broken MIDI feedback when loading stored mappings
- Module STRIP
- Remember and recall file-dialog folder locations for vcvss and vcvs files
- Module STROKE
- Fixed cables’ Toggle visibility command (cable plugs still visible)
- Module TRANSIT
- Improved robustness for expander +T (e.g. crashes when using module-presets) (#412)
19 Likes
It’s me again, sorry 
I have another exotic case, not sure if you want to do anything about it.
Spent a few hours chasing a crash in my (unreleased) plugin. What I had done was to remove a few parameters. That breaks patches of course, buy this is all in the lab and I can easily repair the incorrect values. But it crashes and the call stack show this:
The two mapped parameters for this module in MIDI CAT are close to the end of the parameter range and their id is now beyond the size of the params and paramQuantities arrays because of the deleted parameters. At first I suspected Rack, but whereever I looked for calls to isBounded() (didn’t check all places, but many) there was a range check for paramId against paramQuantities.size().
I suspect MIDI CAT does not do a range check. My problem is that I cannot find a way out of this dilemma without loosing my elaborate test patches with the module in question.
Admittedly probably not a very common case outside a develpment enviroment since removing parameters from a released plugin would break peoples patches. I will bring the removed parameters back, then I’ll be fine, but didn’t expect to have to keep them in an unreleased plugin where parameter lists change often.
Maybe you want to do a range check in parameter ids in a dev build or so….
Edit: didn’t think enough, I can easily save my patches by bringing the params back, ran Rack und unmap evrything linked to MIDI CAT (there are only 2 in the module, fast and slow Leslie speeds mapped to buttons) save the patch and then remove the params again. So my problem is solved, a range check might still be a good idea
Yes, you are right, there is no range check. Because of the assumption, once a valid paramId, always a valid paramId. I will add a check 
2 Likes
If you want automated params in your module, you should probably add CV inputs and then you will not need to resort to external param mapping modules.
When you change the set of params available, you’ve already broken your test patches that reference those params, so you’ll have to create new ones anyway. Even after you get a fixed MIDI-CAT, your test patch is still broken.
It might help to get familiar with editing the json for a patch. Then when you delete params (etc) you can delete those parts of the patch. it’s easy to still end up with something that doesn’t load or crashes rack.
One way to help manage this and not have to throw away too much when you change things is to use selections to partition your testing setup. Have a selection with just the basic setup to use the modules, and a selection for testing each scenario. When you break a scenario by removing/changing params or adding/removing inputs, then you only throw away the selections that test those parts.
Another approach to testing modules is what Squinky has written about, which is by testing the DSP code in a test harness outside of Rack.
Thank you, but I an not talking about automated test setups. My parameters are mapped to CC values froim MIDI controllers for manual changes, replacing this with CV inputs makes no sense.
I am aware that my test patches are broken if I remove parameters, but that is easily fixed by double-clicking the parameter controls once to set them back to default values, Much faster than recreating the test patch from scratch or even a test selection. There is only one instance of the module affected. Once a plugin has been released, changes in parameter order or value range are taboo of course. But anyhow, I found a way to preserve my patches (except for the parameter values on the one module with removed parameters), so it’s all good.
1 Like
Maybe something else is amiss, but I cannot seem to get Stroke to reliably execute the zoom out, I get the zoom in very well, but my shortcut to zoom out usually moves sideways without zoom level change. I love Stroke for these simple quality of life controls. I’m on win 11, VCV pro 2.6.6
1 Like
This is a bug, will be fixed in the next release.
5 Likes
10 Likes
Looks like ORCA… which would be very fun having inside Rack.
2 Likes
Wouldn’t it?
2 Likes
Announcing AHAB
…a port of the ORCA-C project into a VCV Rack module. I just merged it into my development branch and the module can be tested using the development build. Please take a look at the preliminary manual here.
If you have any questions or issues, feel free to let me know!
19 Likes
Good name choice!
2 Likes
Very cool Ben!
1 Like
Now we just need to learn orca… now I have a way to send it to my other instruments but I still have to actually learn how to use it… it pleases my eye and boosts my inspirations
2 Likes
some years ago it was like this:
1 Like
Preliminary changelog for the upcoming version 2.3.0:
New modules
- Module AHAB
- A live programming environment for ORCA, an esoteric programming language designed to quickly create procedural sequencers
Changes and Fixes
- Module GLUE
- Added option to add labels to cables (#247)
- Module MIDI-CAT
- Added hotkey Ctrl/Cmd+Shift+R for resetting input-mode Pickup (snap)
- Added hotkey Ctrl/Cmd+Shift+I for temporarily activating input-mode Direct while held
- Added hotkey Ctrl/Cmd+Shift+F for re-sending MIDI feedback
- Module MIDI-KEY
- Fixed occasional crash in browser preview
- Module SAIL
- Fixed occasional crash (#358)
- Module STROKE
- Fixed broken Zoom out command
- Fixed broken Toggle-commands on different UI Scale (#415)
- Module TRANSIT
- Added alternative parameter binding by selection box
- Added custom color LED setting per slot
- Added option to set the first usable snapshot (instead of starting at 1) (#265)
As always, feel free to let me know about any questions or issues.
18 Likes