Bug? Wah not bypassed on unit boot

The External controllers in the MIDI setup area of the glibal settings can be set to listen to the pedal jacks, not just MIDI CCs. They have an initial value you can set. It might work for your wah.
i went into detail regarding the initial value and when it does work and when it doesn't work on the FM9.

the issue isn't setting up pedals to work with external controllers. the issue is that when turning on the device, a block with Auto-Engage is On when you want it to be off. there's no problem connecting pedals where the Learn function would assist.

in the long post, i outlined the specific settings needed (or not needed) to make that happen with the various options of Auto-Engage Off Value, Auto-Engage Type, and Initial Value.
 
FM9
Auto-Engage Off value is 5% (Heel Down)
you MUST set
SPD type for Auto-Engage AND
set INIT value for that External Controller to 100%
(this is the weird one because FM9 does not respect INIT value, yet 100% INIT setting does the trick??)

Auto-Engage Off value is 95% (Toe Down)
can use SPD or POS type
INIT value doesn't matter (it's always at 100% on boot)
(because the FM9 sets the Pedal to 100% on boot and doesn't respect Init value, POS type for Auto-Engage works for 95% Off, but not for 5% off)
@chris Thanks for the detailed write-up. I'm pretty sure this was my issue as all seems to be resolved. I revised my wah blocks back to "Speed" and re-saved. Unplugging the expression pedal now bypasses the wah block as expected.
 
Glad it is resolved! Please remove the "Bug?" label from the title.

Sorry for the late reply to all this; it was a hectic end of the semester. Thank you so much to Chris for that exhaustive analysis!

I believe this is still a bug. It's inconsistent behavior across the FM3 and FM9 and it's also inconsistent behavior on loading a patch on boot versus loading subsequent patches. If I save a patch with a block bypassed, then when the patch loads, it should be bypassed. If loading a patch after boot can do this correctly, then loading the first patch on boot should be able to do this as well and do it in a way that has consistent, matching behavior..
 
Any updates on this? I noticed if I disconnect my cable the patch turns the wah on. I would hope it leaves it off. Imaging a drunk fan ripping out your cable mid song at a small bar gig. It has happened to me before.. Or just a general cable failure. I have noticed that you have to change presets on boot just to get the wah block to turn off. The work around Chris posted is not working that great for me.
 
Back
Top Bottom