HX FX auto Stomp Mode - why doesn´t it work when MIDI remote controlled?

[clausiii]

Hi folks!

 

I use the HX FX always remotely controlled with a MIDI foot controller (Nektar Pacer), which works great! However, there’s one problem. Regardless of whether I’m in stomp mode or manually editing something in another mode, I need to stay in stomp mode or automatically switch back to stomp mode. Once I press a snapshot or preset, it should switch into stomp mode. This is generally a feature (see quote from the manual, problem description after that).

 

Quote

HX FX auto Stomp Mode

When set to “Moment[ary],” the HX Effects device returns to Stomp mode as soon as a Preset (or Snapshot) switch is pressed. When set to
“Latch[ing],” the HX Effects device stays in Preset (or Snapshot) mode and the user must press MODE to switch back to Stomp mode.

 

my problem is that I can´t use the "Momentary" feature when using the MIDI foot controller. When I change snapshots with it the mode does not change, it stays where it was and does not switch into stomp mode.

 

what I am trying to accomplish is that after switching a snapshot I want to have the possibility to switch stomps individually also from the MIDI foot controller. But as long as the "Momentary" does not work with MIDI commands this workflow is not possible.

 

It would be great if these behaviors of "HX FX auto Stomp Mode" would also work when remote controlled. I think there is no reason against it, isn´t it?

 

Thanks

Claus

[Bonnie219Bailey]

Hello!

You've identified a key limitation with your HX FX when using an external MIDI foot controller: the "HX FX auto Stomp Mode" (Momentary setting), which should return the unit to Stomp mode after a Snapshot/Preset change, only works with the HX FX's physical footswitches, not via MIDI commands. This prevents your desired workflow of switching snapshots via MIDI and immediately controlling individual liteblue usps gov stomps from your controller. You believe this auto-switch behavior should extend to MIDI control for a more seamless and intuitive experience, and it sounds like a valuable firmware enhancement for Line 6 to consider. 

[rd2rk]

As Bonnie said.

 

I don't have the HXFX, I have the HXS which, for most intents and purposes, works the same way.

I'm using an Ampero Control MIDI controller.

 

I'm not sure what you mean by "MOMENTARY" in this context, maybe it's an HXFX thing, but the manual defines it the same way as for my HXS.

If the following is not what you're after, maybe explain what you mean by MOMENTARY.

 

Instead of using the default MIDI message for the FS, assign the Block Bypass to another MIDI CC#.

 

EX: 

You want to toggle the OD Block.

 

OD Block assigned to FS1 = CC#49 (default) - if I send this after a SS change (say, my default is SS1 and I change to SS3) it does whatever FS1 does in the current MODE, but does not switch MODEs. IOW - it only works if the MODE is STOMP. I think that is the problem you are describing?

 

ALT:

OD Block MIDI Bypass = Toggling CC#111 (any CC# not reserved in the MIDI Standard or HXFX MIDI specs). 

 

This works regardless and independent of the current MODE, and without switching MODES.

 

 

 

[clausiii]

Hi rd2rk!

 

momentary means that as soon as I press on a preset or snapshot HXFX returns to stomp mode view immediately but I need to press it directly on the HXFX. loading a preset or snapshot via MIDI does not change pages/views and do not go into stomp mode.

my HXFX is in a rack so it is not possible to use it as a foot controller.

 

my purpose for this is that I want to change my snapshots as usual and after that I want to be 100% sure to be in stomp mode. In most presets/snapshots the six buttons are MIDI CC programmed to enable/disable some (real) stomp boxes patched on a MIDI looper from Voodoo Labs.

[rd2rk]

Apart from being able to use the DEFAULT FS CC# instead of an ASSIGNED CC#, why is it important to remain in STOMP MODE?

 

If you ASSIGN a custom MIDI CC (NOT the default FS CC) to the block's MIDI BYPASS function then it doesn't matter what MODE you're in, it always just works as expected.

Even if you're using the FS to change parameters in other blocks/fx, those changes can also be assigned to the same MIDI CC# as the BYPASS.

This is true of ALL MIDI assignable functions - preset, snapshot, bypass, parameter change - whatever.

When using ASSIGNED MIDI it is not necessary to be in a specific MODE, and the ASSIGNED MIDI message does NOT change the MODE.

 

IOW - you are DIRECTLY controlling the actual FUNCTIONS that you want to control, not using the physical FS on the HXFX to do so.

Therefore, the current MODE is irrelevant.

 

 

 

[clausiii]

it´s not about the blocks it´s about external effects and stomp boxes I am MIDI controlling.

when I am in snapshot mode I will change snapshots, when I am in stomp mode, I am able to control the six buttons however they are programmed.

mostly I use the six buttons to turn on/off the Voodoo Lab HEX Looper. there are six stomp boxes connected and I save the on/off status mostly with snapshots. sometimes I need to manually add an effect (block or stomp). this only works in stomp mode.

[rd2rk]

As is often the case, the devil is in the details, and the six external fx/stompboxes weren't part of the original spec. 

At least, that was not clear.

So, I'd need to know WHAT they are and HOW they're placed in the signal chain.

If they can be controlled via MIDI, which it SEEMS like what you are implying, then everything I said above still applies.

I'd like to help you sort this out, but PLEASE try to be VERY clear on the details.

[clausiii]

Allright.

My main goal is to play certain songs with the four available snapshots of a preset.

With the snapshots I save the blocks on/off status and the six stomp buttons status.

the stomp buttons send (in my case) CC MIDI data to toggle on/off the six send/returns of the Voodoo Labs HEX Looper.

 

example:

1. my foot controller sends CC69 value 0 for snapshot 1 of HXFX
2. this enables/disables the blocks in HXFX and enables/disables the six stomp buttons of the HXFX
3. the six stomp buttons send CC toggles to the Voodoo Labs HEX looper (CC80-CC85, value 0-64 off, 65-127 on) to turn on/off the six effects loops

so far so good - this works flawlessly and perfect.

 

but now what happens when I want to enable/disable one of the six HEX effect loops without using snapshots?

 

I need to use the CC49-54 to enable/disable the HXFX buttons but as the manual says: "NOTE: These MIDI CC 49~54 messages control the respective switch’s function while in Stomp, Preset, or Snapshot footswitch mode"

 

That means that I need to be in Stomp mode to enable/disable the right thing, if I were in snapshot mode the CC49-54 would switch snapshots instead of the stomps or change presets in preset mode.

 

That´s why I want to be in stomp mode.

 

a sidenote: of course it's possible to send CC data directly from the foot controller to the HEX Looper but this would disturb my concept that everything after HXFX in the MIDI chain is controlled by HXFX...

 

[rd2rk]

On 7/19/2025 at 8:43 AM, clausiii said:

a sidenote: of course it's possible to send CC data directly from the foot controller to the HEX Looper but this would disturb my concept that everything after HXFX in the MIDI chain is controlled by HXFX...

 

Here we are at the heart of the problem.

After a cursory look at the HEX and NEKTAR manuals, this is how I'd do it:

 

Set the HEX to accept PC (and CC if desired - see below).

Set the HEX to MIDI Channel 2.

On the HEX, save as many Loop combinations as you want. Save them to consecutive PC#s (for simplicity).

 

On the HXFX, set Global Settings>MIDI>MIDI THRU = ON; MIDI PC Rx = MIDI; MIDI PC Tx = OFF; Snapshot CC Send = OFF.

The last 2 - MIDI PC Tx and Snapshot CC Send - shouldn't really matter if you've set the MIDI Channels as described, but, "Best Practice".

Leave the HXFX MIDI CHANNEL set to 1 (default BASE CHANNEL - check to be sure BASE is set that way).

Set up as many HXFX combinations/presets as you want.

In Control Center, in each preset, on SS1 (Snapshot 1), use the first Instant Command (IC1 - the first lightning bolt) to send the PC# for the default HEX Loop that you want to load with that preset when the HXFX preset loads. Be sure to set the Channel to 2. SAVE the Preset on SS1.

 

Apart from that, forget Snapshots as controls for the HEX, just use them for controlling the FX on the HXFX in SS MODE or individual FX Bypass/parameter control in STOMP MODE. IOW - use the HXFX switches for their primary functions. The MODE needs only change if you WANT it to change and has NO effect on what's coming from the Nektar. KISS theory.

 

NOTE - if you choose to use Snapshots like this, be sure that in each Snapshot IC1 is set to the desired HEX Loop. The ICs are sent each time you change Snapshots but won't RESEND the same message unless a DIFFERENT message is sent on that IC. The IC value on new Snapshots defaults to PC# 0 (zero) unless you manually set it in each Snapshot. So, in each SS either set IC1 to the SS1 PC# or to the PC# for the HEX loop that you want to use with that SS. 

 

Use the Nektar to select the HXFX Preset (on MIDI CHANNEL 1) which will then automatically load the default HEX Loop for that HXFX Preset.

Set the remaining available Nektar switches to send whatever alternate PC#/HEX Loop Combinations you want available in that Nektar/HXFX Preset (MIDI CHANNEL 2).

You COULD also have any or all of the Nektar switches call totally different HXFX Presets. Lots of possibilities.

This gives you access to 128 HXFX Presets/FX configurations and up to 10 HEX Loops from every HXFX Preset vs 4 using Snapshots.

You could also use CC#s 80-85, though I would see that as limiting vs using PC#s. Whatever floats yer boat!

 

Anyhow, this method, while it may SEEM complicated, is the most efficient and flexible use of your HW.

It allows you total control of HXFX Stomps and Snapshots on the HXFX and total control of HEX Loop Combinations with the Nektar.

You never have to touch the HXFX or worry about the MODE unless you want to for Stomp/SS control.

 

Of course, while VERY complex combinations of HXFX and HEX Loops are possible with this configuration, it can also be as simple as you want.

 

I've attached an example preset to demo the SS IC configuration. I created it on my HXS, but it SHOULD load on your HXFX.

If not, you can convert it with Native.

I tested what I described using my Ampero Control and it all works as it should in terms of what gets sent when.

 

Final Note: The Nektar Pacer allows for a lot of different ways to do what I've described. I'm not going to try to figure out a "best" way. The manual kinda sucks and, although there's a web-based editor available here:

 

Nektar Pacer Editor by StudioCode.dev

 

It can't be used without a Pacer actually connected, so I was unable to play around with it.

 

When setting up your Pacer (or any MIDI controller) you should have a MIDI Monitor to verify that the controller is ACTUALLY sending what you THINK it's sending.

If you don't already have one, here's a link to a simple one:

 

MIDIView - Free MIDI Monitor tool for Win & Mac

 

Of course, the Gold Standard is MIDIOX (Windows only):

 

MIDIOX

 

Questions?

 

 

 

clausiii.hlx

[Schmalle]

Not sure if this is already solved but you select Stomp Mode via MIDI by sending CC#71 = 0.

 

So the MIDI controller sending 

1. CC#69 = snapshot number-1
2. CC#71 = 0
3. CC#49-54 = 0

might be the solution.