Support
Looper's Delight
|
Support |
|
|
> I have
>> ran into the
>> problem you describe many times. What I do is to
>> make sure I always
>> have the feedback function assigned to that actual
>> expression pedal
>> in at least one patch with an "harmless" function -
>> like for example
>> Overdub. If I don't play anything I can press a
>> short Overdub only to
>> recall the patch that has feedback assigned to the
>> expression pedal.
On 5 okt 2006, at 08.33, L.A. Angulo wrote:
> so if i understand correctly you assign a value of 127
> on the overdub button for example and press it shortly
> to reset the controller?
No. I'm talking about the FCB "PADS" assignment of particular FCB
PATCHES.
When I press my foot at the overdub button the FCB is doing two
things: (1) Sending the MIDI Note for "Overdub" and (2) recalling the
pad assignments of that patch (since you call up a patch by pressing
a button),
In my EDP rig I have different functions assigned to expression pedal
2 in different patches. But since I know that when I press the undo
button I will also recall a patch that is using expression pedal 2
for EDP Feedback. So if I recently called up a patch where I the
expression is used pedal for something different (like for example
tweaking the tempo division of the MIDI Clock beat sync LFO of my
filterbank) and suddenly discover that "oh, shit - I forgot the EDP
Feedback at 88 % and now all my music is vanishing!!!! HILFE -
HILFE!" ...he, he... what I can do in that situation is to quickly
press undo two times (on/off) without playing anything, only to make
the expression pedal 2 start sending the EDP Feedback data instead of
the Filterbank data. Then I push down the toe to maximize feedback
and get back to whatever I was doing.
>
>> Another strategy I have developed to stay out of
>> such trouble, and
>> also to be able to loop faster and more fluently, is
>> to double up
>> most function over many controller buttons.
>> Especially the feedback
>> functions. I like to have both expression pedals and
>> twistable knobs
>> or faders assigned to the same parameter. Then I can
>> simply reach for
>> the most immediate way to achieve feedback or
>> whatever.
>
> this sounds cool,but it could create problems as
> well...donīt know if i am understanding it right could
> you give me a more specific example?
Ok. Three examples:
(1) Let's take that catastrophe scenario from above. I have a little
hand mixer beside the laptop (Faderfox) and some of the faders and
knobs are sending the same MIDI cc data that the FCB expression pedal
does send. So I can use either the pedal or a knob or a fader.
(2) A typical example would be if I'm working in a FCB BANK where I
have no patch button ("pad", as the FCB manual calls them) that
brings up the particular MIDI cc I want for the expression pedal.
Then I simply reach out a hand and twist a knob - because that knob
is always sending this particular CC data.
(3) In Mobius there are many times when I'm working on one track (the
selected track, equals one EDP in a multi EDP rig) and find that I
want to adjust feedback of a loop playing on a different track
(another EDP). Then it's handy to have hardware knobs directly
addressing feedback (and other functions) directly on different tracks.
In Mobius there are both Feedback and Secondary Feedback and I like
to set it up to use them both. The Secondary Feedback can have any
setting because it only kicks in when loops are in Overdub, Multiply,
Substitute etc mode. The normal Feedback is usually set to 100 % and
I use it for fade outs or for manually creating volume patterns in
loops.
All the best
per