Jump to content

Touch Capacitance for Edit Mode?


MusicLaw
 Share

Recommended Posts

As a new Helix owner I am enjoying Stomp Mode's capacitance touch sensitive buttons feature.

 

I saw the February 2016 thread about the touch feature's capability to recognize multiple touches:

http://line6.com/support/topic/18467-can-the-capacitance-sensitive-switches-detect-a-double-tap/

 

It would seem that the touch feature would be useful in other modes as well, particularly as many YouTube videos show users using their hands and fingers with their Helix's positioned on their desks, adjacent to consoles, etc., all in lieu of the Editor.

 

Is there any reason why the genius of the capacitive touch sensitive buttons has not also been enabled for the Foot Edit Mode? This would be a magnificent method to select the controllable parameter (in lieu of requiring a click of the fsw btn). Moreover, multi touches of the Value-, Value+, and touches of Back, <Page, Page> would be useful too! This would not be necessarily when using your feet!

 

The touch feature could also be useful for Bank Mode, Preset Mode, and Snapshot Mode.

 

A Global fsw Parameter setting allowing users to define which Modes they wish to touch enabled would provide ultimate user flexibility.

 

I created an IdeaScale post. Vote It Up if you agree. http://line6.ideascale.com/a/dtd/Touch-Capacitance-footswitch-for-Edit-Mode-and-more/861308-23508?submitted=1

Link to comment
Share on other sites

Although I do almost all of my interaction with the Helix through the Helix interface rather than the editor, and I do use the capacitive touch  feature, I'm not sure I'd be a fan of taking it much further knowing that each additional feature further reduces computing resources that could better be reserved for operational features such as amps and effects.

Link to comment
Share on other sites

Although I do almost all of my interaction with the Helix through the Helix interface rather than the editor, and I do use the capacitive touch  feature, I'm not sure I'd be a fan of taking it much further knowing that each additional feature further reduces computing resources that could better be reserved for operational features such as amps and effects.

 

It's not necessarily true that adding additional features reduces computing resources, sometimes it's just a matter of turning on functionality that is already in the code, but needed further hooks into other features and/or debug testing that was not yet in the plan.

 

I think, however, that the design philosophy is such that pedal edit mode is meant for use in live gigs, and I'm not sure how many people would want to rely on always being barefoot during their gigs.

 

But, there's always global options, (haha, poke, poke, DI ;) ), and ideascale.  Write up and post your idea and how you think you'd use it, and maybe it'll stick.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...