H90 Multiple Expression Pedal Mappings

Jason M Smith wrote:

… I am noticing instances in other user programs when the Hot Knob P is used to mimic an expression pedal that other parameters are assigned to it such as Mod Rate, Depth, and Q-Sensitivity are also mapped to HK P and thus the expression pedal.

What is the general line of thinking behind this?…

I can only speak to my own general philosophy behind this kind of programming approach:

• Versatility (A):  Some end users might use an EXP pedal (floor-based); others strictly in a desktop scenario, or MIDI with no EXP.  I try to keep that in mind while building a Program.

• Versatility (B): Some parameters mapped to a HotKnob, it also being mapped to an EXP, with another subset directly mapped to EXP.  That opens up options to reconfigure Programs differently, by hand or foot.

• Specific to Manual Mod:  When available, I always map it to EXP (sometimes inverted).  The user may tweak the Shape to a Manual (mode), or a HotKnob may control adjusting the Shape.  EXP control will always be on-deck for Manual via EXP.

• Hardware configurations:  It’s possible for users to hook up two EXP pedals, (1) 3x switch, (2) sets of 3x switches, MIDI, or no external control at all.  I try to cover any of those situations for some useful results.

I haven’t seen where anyone else using two EXP pedals.  Personally, I’d be lost without them.  Either each EXP has a distinctly different effect over the Program, or EXP2 as a master (“fixed wah”) control over what EXP1 is doing.  My Programs reflect that approach.

• Ease of Modification:  Every parameter mapping gets saved within a Program, whether it’s actively used or not.  So I map every control to something.  It may have MIDI CC control unused, for example.  But it’s a lot easier to re-map a parameter to say, EXP or AUX, than it is to configure it initially.

• Mega-Mapping:  Yes, there are times when mapping an EXP to the Program HotKnob may also control the A and/or B HotKnobs by extension.  That opens up several avenues for adjustments, specific to one or the other Preset, the combined Program, or external hands-free control.

There’s more, but I’m already running long & lost some readers.  Let me know if you want any of the points fleshed out in further detail, or specific examples of use.

Jason, you really like your wahs, in granular detail.  And here I was, giving you generalities.  I’ll try breaking this all down & replying with some specifics.  Let me get in front of my system first to try out some ideas

I came up with (quite) a few test examples, but with wildly different methods of getting there, and differing results.

So to clarify:

• Your prime objective would be the dynamic & organic under foot, plus the variation in sharp attack / Q?
• Nice-to-have would be the smoother swirl found after the rebuild?
• Regarding the HotSwitch, are you looking to toggle those organic components in or out, or prefer those to be ‘always on’ as part of the Manual Sweep?

I think all of this can be emulated, in one way or another.  You can toggle the ‘state’ of variations in the manual pedal sweep, but the range of those will either be static values, or set independently.  For example, set the ranges of Q-Intensity, Depth, Depth Mod & Manual Mod inside of the treadle sweep itself, or switch in Depth Mod onto a ‘regular’ wah sound to introduce those secondary dynamics.

I don’t intend to confuse the issue over these specifics, but I’m not there hearing what you are looking to simulate.  The answers will narrow down the focus, without heading off in the wrong directions.  From there, it should be an easier task to adjust to more subtle or extreme results.