I’m working on a custom unit to convert a gate signal to toggle triggers (trigger when gate goes high, then trigger when it goes low). The way that first comes to mind is to mix the input with a slightly delayed, inverted version of itself and then rectify the result.
To do this, I’d need to have the input to the custom unit available “multed” as an input to a mixer’s mix input chain. I know how to do this in a top-level chain, where I am just connecting the same input jack to multiple units, but is there a way to get “input to this unit” as a local so I can save this as a custom unit? Hope this makes sense…
To be clear, I get that I could put the signal into a custom unit control chain, but I would like to be able to use this unit inline as a filter on other chains where the main input is what’s being affected.
Edit: for clarity the tap tempo is just there to mock up a gate. Go into lin1 control, delete the TT, and you could use an external gate signal here instead.
It’s for a pedal-controlled looper. I have a MIDI pedal board running into a piece of software to “multiplex” 4 gates from pedals onto a single CV, and have them decoded in the ER-301. Now I’m working on converting the gates to toggle-triggers to control the state of the looper unit.
I know there’s a “native” pedal-style looper coming somewhere along the line but I think the existing looper is plenty to get it done.
Found this thread while searching for a way to access a custom unit’s input locally. Let this bump serve as my support for this feature’s development! I feel like it could make custom units much cleaner (ie “surface-level apparent control”).
Haven’t dug into middle layer development yet; is there a way to accomplish this (or anything similar) using LUA?
Yes, in my experience so far, routing is more free in the middle layer. You get direct access to the unit’s input, and can connect things together without being constrained by the UI layer left–>right topology, as well as route outlets to multiple object inlets.
If “unit’s input” and “unit’s parent” are available in the LUA layer, a perfect reusable bridge unit would simply output the signal from something like “unit’s parent’s input” (not sure exactly how many parent-traversals, maybe it would be grandparent). That unit could be placed inline at the front of the chain for a custom unit’s parameter, which would neatly fake having “parent input” as the chain source until “parent input” is available as a native chain source.
