Feature suggestion: invisible cable for CLK, RESET and other overused connections to unclutter the view

There are some cables like those connecting CLK or RESET to many modules that add unreasonable clutter to a rack.

I would like to propose a special “cable” which is invisible and can be connected from a certain output to many inputs without immediate visibility. This visibility can be switched on or off, but default would be transparent. This would help to unclutter racks where the main clock is connected to many modules.

The idea would be just like a Ground symbol in electronic schematics. I hope this idea is readable - English is my third language :smiley:

(You may know it, but) there’s a utility in the Submarine pack, which adds to the cables’ color palette - or lets you restrict it to only one color, say gray, to make those CLK RESET connections.

The issue with Rack doing something like this is individual cableColors are not classed as separated cables they are all the same and take the opacity from a master control in the view menu. I wonder if @carbon14 would be able to fulfil this request, if a cable is a certain colour reduce the alpha of this one cable?!

For Rack bug reports and feature requests see:


1 Like

@Coirt, thanks for the heads up. It would certainly be possible, but it might be tricky to implement in a robust way. I’ll have a think


Thanks. I know the submarine tool. You could also go the oldschool way and just fidle with the settings-v1.json for the same effect.

My idea is more or less to unclutter massive clockgenerated racks where tens if not hundred of connections are to the main clock and the main reset output form the clock generator.

Imagine Pins (four or five colors would be sufficient) and every “blue pin” would connect to every other “blue pin” without showing the cable. There would be a send PIN - just one of every color! And any number or receiver pins.

Maybe a sketch would be more helpful to understand my idea

EDIT: I could also imagine those pins for chord generated randomized sequences where the notes of the chord are sent to many oscillators which are triggered by different gate sequencers, turing machines etc. etc.


Use GitHub for this request, It may not be responded to here!


Essential the Little Tools Teleport module in pin form. :+1:

Request was rejected by Andrew – “This would overcomplicate the UI”.


@rickglasser ThankYou Rick I know Little Utils, but Teleport makes my racks even more complicated for me - remembering which position on the one side connects to which on the other…

And it is not just about the clutter - I am not an compulsion driven person. It is just sometimes about not be able to see the important cables beyond all those yellow signal cables i do not need to see ever… Or, which drives me mad, not being able to use knobs and switches, because some cable is in front of them so I can not see the position and have to zoom in.

OK enough about this rant… it isn’t happening …it would make the UI overcomplicated

The OP didn’t inspire me as it sounded like a proposal to standardize something nobody wants standardized, but seeing the UI concept with little signal-agnostic pegs, it makes a lot more sense.

Makes also sense this wouldn’t be considered for the core, but… is there anything preventing us from implementing it ourselves? The API gives us a lot of tools to interact beyond the boundaries of a single module.

1 Like