I agree - It should be saved with the selection.
VCV support’s Paul Gatt has replied, and confirmed that “This is a known bug and we are hoping to fix it soon.”
Hrmm… it doesn’t even work now loading the preset… just lists the CC’s but no mapping to the MixMaster module. Looks like I just have to manually map each slider or knob for every new project I do.
My STRIP module supports this for a long time. Unfortunately it is not available in the VCV Library for Rack v2 yet.
5 Likes
Seeeeeeee, moderator patrol, I was a good community member, searched the forms first, change the sort to list by recent posts, before posting something new on a known reported/discussed issue.
Here I am! 5 months later . . . There is still a problem.
We can all agree that mapping midi controllers is a laborious task that can be fruitful after it is all tested and complete. Saving the work as “Save Selection…” seems prudent since, who in the heck wants to do that again
Sorry @JenniferG, its still not fixed
I spent a few hours today, and at my age minutes are precious, after all that work, it fails to recall the mappings using the integrated “Save Selection …” and “Import Selection …” in-app function. I am running Pro v2.06, Windows 10. This was in standalone mode. I am glad I saved the ‘testing ground patch’ with all this information so I can reload all the work
At first, I thought it might be “MIDI-CAT” from Ben’s @stoermelder plugins which are still not in the library and I manually installed. I thought, ya may wanna use VCV’s MIDI-Map just in case … surely it won’t be busted
@JenniferG or anyone else having this issue, just use Ben’s Strip module. Easy peasy - I can confirm, it does work. Also, you can bring over “strips” saved in v1.1.6 into 2.x as well . . . these can be used again, as long as those plugins in the saved strip are available in v2.x
1 Like
Did anything change since the last post? It would be great to be able to save mappings as well…
2 Likes
Some sort, yes:
I created a new module S++ (aka STRIP++) which adds options to paste or import Rack selections while preserving parameter mappings and GLUE’s labels. Just add the module to Rack and use hotkey Shift+Ctrl+V for pasting selections or Shift+Ctrl+B for importing selections.
Available in the latest preview build.
Release Development build · stoermelder/vcvrack-packone (github.com)
I even heard it supports some upcoming new modules…
11 Likes
Oh my - this is a dream come true! Thank you!
It will definitely be a help for upcoming new modules…
I tested S++, and it preserved mappings beautifully. I also tested with the “new module” (I have been helping the developers test), and it worked for that as well.
However, there is one problem - It always attempts to place the selection at the original coordinates, and if there are existing modules in those locations, then the imported modules get intermingled with the already existing modules - a real chaotic mess.
Can you update the code to find the closest free area that will fit the entire selection, without any comingling?
As a bonus, it would be great if there was an option to place the imported (or pasted) selection next to the S++ module, so you could control the placement. (or the closest free area near the S++)
Well, it is the same behavior as Rack has build in. But I absolutly agree, the placement should be more adaptive to the current screen area. I will see what I can do.
You legend 
1 Like
In my testing on Win 10, the native Rack import and paste both properly find the closest free space that fits the selection.
Interesting. You are using Rack 2.1.2? I’m on Windows, too, and selections are always placed at the original position…
Yes, I am using Rack 2.1.2 Pro (standalone - not VST)
The selection is pasted/imported in the original location if there is space. If it overlaps any existing modules, then Rack moves left or right, finding the closest space that does fit without overlap.
I have never seen it move up or down.
Epic!
3 Likes
I changed the behavior of S++ so the selection is inserted near the current mouse cursor position. I think this is much more usable than the default behavior.
Let me know what you think…
3 Likes
That is a brilliant solution to establish an initial trial origin point - I love it!
There is still a potential issue, especially if you do not know the size of the selection. If you import (or paste) too close to existing modules, then you can still get comingling. It would be great if you could implement the Rack strategy of moving left or right from the trial origin until you find enough space for the entire selection.
But even without any additional changes, the functionality is fantastic, and eminently useable. Thanks!
Yes, I did recognize the potential issue… two ad-hoc ideas when it happens:
- S++ supports undo, you can undo the insert and redo it on another place
- After inserting a selection all new modules are selected as well - makes moving them toghether pretty easy
I thought I could be nice to display some semi-transparent preview of the selection, before actually inserting the modules, using the previews from the module browser. But this will be a bit of work and I’m not sure if it is worth it…
1 Like
Sounds very cool though! Will Dirt be coming back into the collection. Got a fair bit of mileage out of that module recently.
1 Like
Really? It is still included in the development builds as it has never been officially released to the VCV Library yet.
Cool!