Sell me on stackable inputs!

I am having to re-train myself in my patching workflow. This is going to take a while.


I tried 2.51 and went back to 2.41 because of this cable change. Why not CTRL drag as it was before and CTRL+SHIFT as the new future? Lovely cable salad.


+1 for making Ctrl+Grab act like the old grab, and using Ctrl+Shift+Grab for the new one. I’m stumbling over it every single time.

I do like the extra features though, and having summable inputs feels like a neat and weird convenience.


Honestly, I thought I’d like cable stacking more, but it surprisingly gets in the way. Is there going to be an option to disable it?

I also feel like they switched A and B on the Nintendo controller and now I can’t play. They really should have left the key mappings alone, or added the new function to a new key IMO.


Stackable cable are great for gates. Want an extra snare hit but only in certain bars?

Also liking them as a poor man’s mixer for quick patches.

Modulation does often need tweaks before stacking inputs, but this is avoidable if the modules you use allow customisation of the output.

1 Like

Annoying, since remapped Ctrl still doesn’t work either: Rack 2.1.2 doesn't respond to extra Ctrl keys

I am totally puzzled by this new feature… I think that it has very little application since as mentioned by much others, when mixing we almost always need to scale and/or offset…

And at the same time I see a loooot of actual use for the option to take a stack of cables at one output and being able to move the whole at once to an other output, which AFAIK still isn’t implemented.

Still loving VCV and using it everyday but this isn’t making any sense to me…

Being sensible about CV ranges is modular 101…


Agreed. Not only because we’re all used to it, but I suspect I’m not alone in thinking that duplication is something a user is going to do much more often, and having the extra key press should be assigned for the lesser used function.

On top of that, The context menu incorrectly shows that CTRL-DRAG is still used for duplication, adding to the confusion.



Oh thank god, I use it a lot too. And yeah, he should have kept the old key-mapping and added a new. The old one is definately easier and more used.

Also, it’s just dawning on me that if you use stackable inputs the patch will probably only work on Rack >= 2.5.0. That’s going to confuse/piss off some users for a while, if sharing patches with others not upgraded yet. At least it should be documented somewhere when incompatibilities are introduced.


One thing that could be interesting with input stacking is if that meant having a weird nonlinear response (because of the output to output patching it actually is).

But this obviously is not gonna happen, so, back to no interest / confusing / bad to teach modular synthesis. :thinking:

1 Like

Especially since there’s no mention of it in the changelog as far as I can tell. Honestly not sure I wanna update due to this, and the move of the user files.


Indeed. I’m sticking with 2.4.1 until something compels me to upgrade.


OOh I like it. Stack up outputs to a common input and the outputs feed back into the parent module and cause it to fry, or the common input gets overloaded causing it to catch fire. VCV could then simulate some purple smoke and let it drift over the front panels.

Of course I’m joking, but when you think of VCV as an educational tool to teach modular synthesis, the input stacking is actually a bad practice in the hardware world. Many of the fancier expensive modules are now protected against input patching, but you can still toast your friend’s DIY project in 2 seconds.


Yeah, output protection is way more common now, but it always feels like a bit of a gamble. Last week-end I was at the Synthfest in France and saw a demonstration by one of the guys from Joranalogue, and he was patching really fast and got a output to output situation quite often, and nothing happened, obviously, I laughed and told him “oh and your modules have a good protection on the outputs too”, he laughed it off and confirmed that since they love feedback and feel a strong connection to Serge designs, they indeed think at this kind of connection as an extended technique, and the modules have been designed in conscience of this…

If there was an option so that input stacking meant average mixing, maybe that would be something that could have some interest, but definitely not as the default behavior… (think of the modulation bus on the ARP 2500)

And yes, it is a really bad habit to just do that without knowledge of the modules, and IMO it takes something from the “virtual eurorack” badge that VCV still wears on the front page…


It’s okay if VCV innovates on features that can’t really work in Eurorack, it’s for music after all in the end. But I totally get your point, and I’m such a purist as well, I had a bit of a hangup over putting my first context menu into a module since ‘real modules don’t have those’.

Now if some Eurorack designer would just figure out Poly cables, we’d be set! :slight_smile: Maybe they could build little CPUs into the cables. New Apple cables practically have this capability already, if you’ve ever seen a take apart video of one of their cables there’s honestly more in there than in a typical eurorack filter design.


I actually can think of 2 cases where summing inputs is very useful.

When I (in nearly every patch) use AS Delay Plus Stereo with an AS BPM module, I use an Synthkit Addition to get rhythmic subdivisions like 9 16th notes.

You don’t need the Addition module any more, you can just plug in more than one voltage.

Using it as an OR for gates can be even more useful. With the VCV Pulse Matrix, I use the Submarine OG 106 to combine two trigger rows, in order to add occasional random triggers.

See, all I had to do about it is to sleep on my own question :grinning:



I am with you on that. What irks me is not the deviation from hardware (I use and love polyphony in VCV for instance…) it is more than this particular deviation is not something I see the point of, and it complicates patching when you just want to ignore it by taking the default behavior of CMD+drag over the cable copying mechanism.

Anyway, I’ll get use to it, I am sure, but I’ll have to make clear when using VCV in class that this is weird and not something you want to do on hardware.


I’ll tell you one thing I will love about this (once I update after an important show next weekend…).

Not needing a silly summing mixer to patch start/stop/cont into the same thing to control transport when running the plugin in Reaper.

Of course, I would’ve rather just had a way to keep a gate high while transport plays. :slight_smile: It’s strange that DAW transport state isn’t in the rack API… but this change is very welcome and at least alleviates one nuisance.

And there are definitely some other situations where I just want to sum two things, this will help with those. :slight_smile:


Me too, but I chalk it up as one of those “First World Problems”.

Then again, there have been times I’ve wished for stackable inputs in addition to stackable outputs. It has origins in real-world stackable banana plugs such as I’ve used on an ARP 2600 and various electronics test gear.

The key command is correct. Click-drag on the menu item to create a new cable.