I know this is pretty farfetched… but bare with me
Just thinking aloud again with some ideas.
I know we have labels coming for the quicksaves but i think we could really benefit from being able to label all the InX, A/B/C/D/G Inputs. Especially when reloading a quick save that may be recalled a week or a month later. Without super detailed notes, the intricacies of patch could be lost. This wouldn’t have to affect all the i/o at an operational level, but could almost be a scratch pad area for notes bundled with the quick save.
So here’s my super nutty idea that I’ve stolen from Air Studios in London, as it was literally the coolest thing I’ve ever seen at a big studio…
So you’re recalling an orchestral mix with substantially complicated patching, it would be a nightmare as there’s HUNDREDS of patch points on the rear wall of the studio. Except, somehow (and i have no who built them) came up with this solution:
When you reload a mix on the automation computer, LEDS would skim across the patchbays (a led per patch point). It would stop at the source), you’d plugin a wire, it would know and then LED’s would skim to the next patch point to tell you were to patch the destination. This process would repeat for as many patches were required to setup the room. Absolutely wild!
So my thought in ER-301 land, if the jacks can sense a connection (which i think it does? or is that the 101/102?), what if:
When you loaded a quick save, there was an optional extended ‘guided’ re-patch. So it would load the patch and then guide you through any required input connections.
-"A1 is required for A1 user label. User then Patches the cable. 301 knows and continues…
-"G1 is required for G1 user label. User then Patches the cable. 301 knows and continues…
Could be cool!