even before wrapping cables, some of it is going to come down to module layout: proximity of one module or module type to another may greatly simplify cable length and reduce the intertwining complexity of cross-patching. if you notice that certain modules tend to keep getting patched together, then you might consider a bit of case shuffling to bring them in permanent proximity.
additionally, you might pursue a logical signal flow. example: external input (left of case) through sequencers, sound sources, fx/processing, and then output (right of case) to mixer. this is what my isms case does by default, and itās what iāve ended up sticking with; it makes sense. granted, this is only a single 120hp row, not the multi-row or multi-case setup that leads to greater cable density.
iāve noticed that iāll typically patch all my ansible outputs into my er-301, so thatās at least 8 cables that can be bundled, and i have a second ansible next to those that iāve used for a bunch more outputs to the 301. so all three are always grouped together when theyāre in the case. and even if those āstaticā patches donāt get cable-tied, by putting them in immediate proximity to each other, i establish a sort of mental āset and forgetā zone, where i can skim over it to other modules and patchpoints that will actually need changing or playing.
but besides keeping module flow as tight and orderly as possible, equally important to me is cable color. i came up with a color system before i even bought my first module, so that iād have instant visual identification. sky blue for control signals, white for audio signals, including any inputs/outputs to external gear. things can now be wrapped together if desired, as iāve dedicated āblocksā of the modular for certain shared purposes. it looks something like this, even without ties in the home studio.
