Can Someone Confirm this Behavior RE: Switching Modes
Posted: Wed Dec 09, 2009 3:08 pm
I think I've got a much better understanding of what's going on. I've boiled it down to this:
- When switching from SGL to QD Mode, the "required" method for pressing Button 1 and Button 3 is to _first_ hit Button 3 and _then_ hit Button 1. Amos specifically mentions this in his newest demo video. This prevents an accidental decrement of the patch. Hitting Button 3 first only changes the Channel being selected in SGL Mode and that seems pretty harmless - especially since you're changing to QD mode where you'll have direct control over the individual Channels.
- Here's where things are confusing/disappointing for me. When switching from QD Mode to SGL Mode, the user is susceptible to toggling Channel 1 or Channel 3 when he hits Button 1 and Button 3. The pedal lets the first Button press activate and then understands that when the second Button is pressed, then the change from QD Mode to SGL Mode was requested. Unfortunately, which ever Button got hit first - just milliseconds apparently - that Channel gets toggled and _stays_ toggled (in Latch Mode - Momentary is much less severe).
- I can train myself to hit Button 3 _before_ Button 1 in order to safely switch between SGL Mode and QD Mode. But it seems if I use the same practice to switch between QD to SGL mode, then I have to sacrifice the use of Button/Channel 3. In other words you have to choose: Do you want to switch between QD to SGL mode in a song, or do you want to sacrifice Button/Channel 3, or do you want Channel 1 or Channel 3 activated randomly when switching from QD to SGL.
That's my understanding of what's going on and I'm at least getting repeatable behavior with that understanding. Is that expected and understood behavior?
I am curious is you guys have messed around with building in some hysteresis on these mode switches. It seems like if Button 1 is pressed, the pedal might wait 20ms or so to see if Button 3 was going to be pressed. If in that 20ms Button 3 doesn't get pressed, the Preset is decremented (and the Program Change is sent). If Button 3 gets pressed, no Preset change is made (no Program Change gets sent) and the unit switches from SGL to QD mode. Same thing on the way back, If Button 3, for example, gets pressed, a 10-20ms wait is put in place to see if Button 1 gets pressed - i.e. the user is trying to switch modes and not activate Channel 3.
I bet there's some awkward inflection point where the time window required to protect the user from order dependent Button presses collides with the user's awareness that a delay is being put into the Button press.
Brandon Lewis
- When switching from SGL to QD Mode, the "required" method for pressing Button 1 and Button 3 is to _first_ hit Button 3 and _then_ hit Button 1. Amos specifically mentions this in his newest demo video. This prevents an accidental decrement of the patch. Hitting Button 3 first only changes the Channel being selected in SGL Mode and that seems pretty harmless - especially since you're changing to QD mode where you'll have direct control over the individual Channels.
- Here's where things are confusing/disappointing for me. When switching from QD Mode to SGL Mode, the user is susceptible to toggling Channel 1 or Channel 3 when he hits Button 1 and Button 3. The pedal lets the first Button press activate and then understands that when the second Button is pressed, then the change from QD Mode to SGL Mode was requested. Unfortunately, which ever Button got hit first - just milliseconds apparently - that Channel gets toggled and _stays_ toggled (in Latch Mode - Momentary is much less severe).
- I can train myself to hit Button 3 _before_ Button 1 in order to safely switch between SGL Mode and QD Mode. But it seems if I use the same practice to switch between QD to SGL mode, then I have to sacrifice the use of Button/Channel 3. In other words you have to choose: Do you want to switch between QD to SGL mode in a song, or do you want to sacrifice Button/Channel 3, or do you want Channel 1 or Channel 3 activated randomly when switching from QD to SGL.
That's my understanding of what's going on and I'm at least getting repeatable behavior with that understanding. Is that expected and understood behavior?
I am curious is you guys have messed around with building in some hysteresis on these mode switches. It seems like if Button 1 is pressed, the pedal might wait 20ms or so to see if Button 3 was going to be pressed. If in that 20ms Button 3 doesn't get pressed, the Preset is decremented (and the Program Change is sent). If Button 3 gets pressed, no Preset change is made (no Program Change gets sent) and the unit switches from SGL to QD mode. Same thing on the way back, If Button 3, for example, gets pressed, a 10-20ms wait is put in place to see if Button 1 gets pressed - i.e. the user is trying to switch modes and not activate Channel 3.
I bet there's some awkward inflection point where the time window required to protect the user from order dependent Button presses collides with the user's awareness that a delay is being put into the Button press.
Brandon Lewis