Support
Looper's Delight
|
Support |
|
|
With mobius you wouldn't need to model the looper in the controller. You just write a script for each button that asks "if mobius is in this state, then do this. If not then do something else". You'd just need to script the behaviours you want depending on the current conditions. This is not possible with the lp1 and I'm not sure even the most sophisticated floor controller can model a looper within it. Sent from my iPod On 20 Mar 2011, at 23:52, Mark Hamburg <mark@grubmah.com> wrote: > On Mar 20, 2011, at 4:51 PM, Mark Hamburg wrote: > >> On Mar 20, 2011, at 12:31 PM, andy butler wrote: >> >>> Simeon Harris wrote: >>>> I'm not sure this is possible with the lp1. >>> >>> It's not, and I'm sure Mark knows that. >> >> I'm aware that there are a few things that just aren't possible and >that many of the other things I want could be done if the controller were >sophisticated enough to model the state of the LP1 (and really annoying >in cases where the model and the LP1 got into a disagreement) but that >requires a really sophisticated controller. I also know that it fits >pretty much exactly with the playback and general loop manipulation >capabilities of the LP1, so it's a matter of how it gets controlled >rather than what it does -- not to say that's easy. > > But I was really pleased when I figured out how to map most of the >functionality I care about to a reasonable number of switches. But then >I'm stuck with the gulf between those switches and the actual looping >machinery. > > Mark >