Flux switch and parameter editing disables when currently loaded preset is called again via MIDI

[Philipozz]

I use an Ampero controller to switch presets on both my amp and HX One via MIDI with a series of messages. My problem is that the ability to use the flux (both via the onboard switch and MIDI) disables when I press a button that calls the same preset that is already loaded. This also locks the preset from having parameters edited through the knobs. If I want to use flux or edit the preset, I have to pick another and then go back again.

I tried finding an explanation in the manual and I doubt this behavior is intentional from L6.

There are some less pretty ways that I can get around this, like making multiple presets of the same effect or to make a dummy preset that is called between calling the same preset again, but these all ruin the flux by changing the settings instantly.

 

My wishes/suggestions:

• That the HX One will ignore the PC command if the currently loaded preset is called again and nothing is changed.
• If something has changed: Reload the preset.
• The ability to actively change the flux setting to high or low instead of just toggling.

 

Another question:

How long does it take to load a preset? I tried making a series of commands to my amp and the HX One where the preset will be loaded and flux being toggled immediately afterwards. I didn't get it to work when doing it as a series of commands, but I could select the preset and then toggle flux.

[silverhead]

Are you running the latest firmware? I know it fixed a bug involving Flux but I don’t know if it will fix your issue. Worth a try if you’re out up to date.

[kwells1204]

I have this same issue.  Knobs are locked after loading the same preset twice.  

 

And if I try changing Presets via MIDI PC immediately followed by a CC4 message to toggle an effect OFF, the CC message is never processed.  MIDIOX confirms my MIDI controller is sending both messages.   

 

If I command both messages, and the preset doesn't need to change, the CC4 message gets through.

[kwells1204]

I am using the latest firmware 3.81.00.

 

 

[opositif]

Same problem for me. I'm changing presets of my nano cortex and hx one with my graviton M2 midi controler with the hx one effect OFF by default.

when I put effect on with the hx one the Flux works, but when I put effect on with the midi controler Flux is not working anymore...

My midi comands for exemple : on Nano Cortex : PC10 and on Hx One : PC10 and CC1 with 0 value to put effect on and off
And I'm with the last firmware 3.81

[kwells1204]

When will we expect a fix to this?

 

Also, I can't seem to enter a support ticket anymore on the website.  I can't get past the first step.  I click on the "Search" button and nothing happens. 

[Almir_Matoso]

Em 31/01/2025 às 17h19, silverhead disse:

Você está executando o firmware mais recente? Eu sei que corrigiu um bug envolvendo o Flux, mas não sei se resolverá seu problema. Vale a pena tentar se você estiver atualizado.

Bom dia! Boa tarde! Boa noite! Gostei muito das atualizações para o HX Stomp, mas agora acho que deveria haver uma atualização para captura, já que o Ampero Stomp 2 teve essa atualização. Nós, consumidores da Linha 6, estamos esperando por isso. Vamos esperar com antecedência.

[Pointlessaccount]

I have the same bug, I'm on the latest firmware 3.81.00

 

I opened a support ticket but no progress so far.

 

 

[Pointlessaccount]

I am replying again here in the hope that this reply will be approved, my previous reply made 10 days ago is still hidden and showing "Your content will need to be approved by a moderator"

 

I have the same bug, I'm on the latest firmware 3.81.00

 

I've opened a ticket with Line6 and the response is that "The senior guy here confirmed that this bug was fixed with 3.81."

 

Which doesn't seem right,  the claimed fix is never mentioned in any firmware bugfix list and everyone in this thread still has the issue on 3.81

 

 

[syntapunk]

I also have same issue of locking knob when i send the PC message twice.

[kwells1204]

I also sent in a support ticket.   

 

The response from Line6  was:  "It's a known issue and logged as bug, I don't have time frame when it will be fixed but it's on the radar."

[Pointlessaccount]

On 4/12/2025 at 5:24 AM, kwells1204 said:

I also sent in a support ticket.   

 

The response from Line6  was:  "It's a known issue and logged as bug, I don't have time frame when it will be fixed but it's on the radar."

 

Could you please let me know your ticket number?

 

The customer service rep. in my current ticket is saying the bug was fixed, it would be great to be able to point to your ticket where it has been accepted by line 6 as a known issue. 

I fell like the more tickets this bug is linked to the sooner it'll be fixed.

 

It's the most egregious midi bug I've come across in my years of midi use, I'm pretty disappointed line 6 has been so slow to fix this. 

[rossedwards]

Just adding +1 to the list.

 

I use a GigRig G3 to manage my MIDI switching and, since updating to 3.81.00 I'm seeing the same problem. My 'clean' patch on each G3 bank sends a PC message to HX One to select the relevant effect e.g. Chrome Custom wah. Works perfectly the first time I select the clean patch, but when I move to another preset (e.g. drive) and back again, the second (and subsequent) issuing of the same PC command causes the flux/exp feature to lock up - the only workaround is to select another patch on HX One before re-triggering the original PC message.