Just at a brainstorming stage…
I tried adding a second looper. Immediately two things occurred to me.
-
It would be nice to have some sort of visual counter on the master clock so that one could tell at a glance which bar the clock is on at any time. The idea being that, by seeing where the main clock is at in the cycle, one could arm the second looper and get ready for the whole patch to begin again. Maybe just the same neat time meter you put on the looper itself, but on the master clock as well? Or Something that said Bar: 63/64?
-
The quick and dirty way to “arm” seems to be to, again, have a gate that can be inserted between one of the master clock bar division gates, on the one side, and the looper record button, on the other side of it.
Even fancier (but foreseeably useful for many applications here), would be to have this switchable gate have two types of buttons in one module.
Button A) When engaged, this gate remains open, as when disengaged, also remains so.
Button B) This would be the same as button A, except it has a separate gate input that can tell it to close. The idea here is to have separate gate Inputs for opening and closing. This would make it possible to have a synced record start when the clock starts but, once in playback mode, at anytime a guitarist could decide to “arm” the overdub as soon as the clock completes the bar cycle.
I understand that a lot of this is probably ultra simple and kicking around but, when you aren’t a builder, many of these small modules aren’t where you go to look for them in the libraries, or there are two or three other details that get in the way of them working straightforwardly. For example, a new user would probably get tripped up by not realizing how important the “gate to 10ms pulse” is to get things to talk to each other properly. Also, sorry if the above is confusing. It’s not easy to communicate without a standardized vernacular, which builders would be more familiar with in speaking to on another.