Support |
hi Bernhard, Interesting concept. ...and even FCB1010 owners can try it, as the same idea works with the EDP presets, which can be called up with Midi Prog Change. (the FCB can send PC followed by CC in one press) The reasons I don't follow this approach are 1) The EDP is left in the changed "mode" after the button press, so you now have something extra to remember. 2) It uses up a lot of buttons, so it means that you end up with more than one banks of controls on the foot controller. In both cases here, the "cognitive burden" is brought back up again :-( Generally I think the big strength of the EDP is it's user interface, the way it's possible to get so much functionality out of just a few buttons. Usually those buttons all do something useful, whatever state the edp is in. If the price for that is 2 button presses rather than 1 (often the case) to get where you want then I accept that cost, partly because it's fun for the feet, and partly because the alternative is either less flexibility, or having to use more than one bank on the midi controller (which is even more button presses, and pretty dangerous in a live situation.) I notice that the current trend, with LP-1 and Mobius (for instance) is to create the scenario where you can do a whole bunch of stuff with one "button". Could this be seen as Looper as instrument vs. Looper as effect ? In which case the "edp" approach is the "getting your hands dirty actually doing it yourself even if you have to practise the moves" way compared to the LP-1/Mobius way of "once it's set up, I just press a button and this wonderful thing happens". andy butler > The idea would be: By using a MIDI footcontroller, get rid of the EDP's > concept of modes (which are perfectly suited for the situation with the > EFC-7!) and instead offer different versions of the same function by > sending a preprogrammed sequence of commands to the EDP. > > Using the SwitchQuant example from above, you could program two NextLoop > buttons on your MIDI footcontroller: > Button A for "immediate switching" would first send the required SysEx- >or > Note-commands to change the EDP SwitchQuant mode to OFF and then send >the > Note-command for NextLoop. > Button B for "confirmed switching" would first send the required SysEx- >or > Note-commands to change the EDP SwitchQuant mode to CnF and then send the > Note-command for NextLoop. > > So instead of adhering to the EDP's mode concept where a function behaves > according to a previously configured EDP mode (which you must keep in the > back of your head while playing: a cognitive burden), you offer two > different functions (which work always the same, ignoring the current EDP > mode). > > This would be interesting also for the insert and substitute-commands... > > Bernhard > > > > > > > > > > >