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

Helix HX MIDI Input Behavior


BlueViolince
 Share

Recommended Posts

I am reprogramming an Arduino switcher(that currently works fine) for my HX Stomp(FW 3.71), and I'm running into some weird behavior. 

 

I'm trying to set up switches to work with the block bypass switch modes(momentary or latching), and it isn't doing what I expected. When momentary type is selected in bypass assign, the switch will not get any response. When latching mode is selected, I can get the block to latch on and off, but I can also get momentary engage by holding the switch down on the switcher. 

 

My question is this: Does the HX Stomp only work with single incoming CC and PC events, as opposed to continuous fired messages? It looks like for proper hold behavior, I need to send one CC message to engage, and then send a second identical CC message when the switch is released.

 

When I program the switcher to send a continuous CC message, the selected block just blinks on and off, like there's a MIDI loop error. I'm trying to get the switcher to behave like the onboard switches, e.g., program external FS4 and 5 to momentary mode for momentary engagement, or latching mode. I can work with what it's doing now, because with the switch behavior programmed to latching mode on the HX side, I can get the switch to latch or hold momentary. It's just a little less predictable how it will respond than the onboard switches. It also doesn't respond on switch press, but either on switch release, or the timer. Meaning, for the latching behavior, I need to press and release within 125 ms, and for momentary hold, it waits 125 ms before engaging the block. 

Link to comment
Share on other sites

I think that it's the opposite. Momentary switches send CC, but latching switches will probably cause errors. The arduino sees a press/release event, and sends one message. In order to send a press/hold message, or a long press message, it needs to wait to make sure that it wasn't a short press. While it's waiting the quarter second, or half second to confirm that it wasn't a short tap, it won't send the press/hold or long press message. This causes a short delay before an effect block will activate in momentary mode. For this reason, the momentary hold cannot engage immediately like it does with the factory switches. 

 

The benefit is that I can use latched fx switches, or get momentary effect engagement when I want, without changing block settings. This isn't possible with the onboard switches, as far as I know. This will be handy if I decide to add looping controls, reducing the number of switches I need by setting dual functions for each switch. Press/release, press/hold, double or triple tap can all be assigned to separate functions off of one switch. 

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...