Please ensure Javascript is enabled for purposes of website accessibility Jump to content

jdonah

Members
  • Posts

    6
  • Joined

  • Last visited

Profile Information

  • Registered Products
    4

jdonah's Achievements

Newbie

Newbie (1/14)

  • First Post Rare
  • Conversation Starter Rare
  • Week One Done
  • One Month Later
  • One Year In

Recent Badges

1

Reputation

  1. Any way to disable full touch-capacitance yet? Also, I am not able to reassign Tap/Tune to other switch locations successfully.
  2. Firmware: 2.7.0 through 2.8.2 (HX Stomp) Global Settings: default all, Footswitches->stomp select->press Bug: When Press is selected as the option for “Stomp Select” under Preferences->Global Settings->Footswitch it appears to do nothing in that touch capacitance is still active. It can be quite frustrating to accidentally trigger the Tap Tempo feature with my hand on FS5 while manually adjusting the HX Stomp. It would be ideal if touch capacitance could be fully disabled through this setting or a separate setting.
  3. Firmware: 2.7.0 through 2.8.2 (HX Stomp) Global Settings: default all, Footswitches->stomp select->press Bug: When Press is selected as the option for “Stomp Select” under Preferences->Global Settings->Footswitch it appears to do nothing in that touch capacitance is still active. It can be quite frustrating to accidentally trigger the Tap Tempo feature with my hand on FS5 while manually adjusting the HX Stomp. It would be ideal if touch capacitance could be fully disabled through this setting or a separate setting.
  4. Hmmm.. Would it be an unreasonable request to make it an off/on setting in the next firmware update?
  5. I would like to turn off the Touch Capacitance feature of the foot switches since I seem to always hit FS5 with my hand when I manually tweak the pedal. If I go to Preferences->Global Settings->Footswitches->Stomp Select and toggle between Touch/Press/Both it doesn't seem to do anything and my foot switches are still sensitive to touches. I looked in the firmware bugs section and there doesn't seem to be a direct mention of this issue. For the record I have tried all firmware versions from 2.7.0 up to the current 2.8.2 and the issue is still present. Am I alone in this occurrence??
×
×
  • Create New...