Midi issue and diagnosis

[RSVMark]

Hi all. Wondering if anyone can help on this diagnosis. Sorry for the long post but it’s a full description to avoid wasting people’s time.

 

i have a GigRig G3s controlling 3 midi pedals: channel 1 is an H9, channel 2 is a Jackson audio golden boy, and channel 3 is my new HX one. They are daisy chained G3>HX1>H9>Gb purely due to cables and pedal board layout.

 

i have changed the global settings of the HX1 to be channel 3 and midi thru obvs. 
 

All midi commands (pc and cc) work as intended to the H9 and GB meaning the cabling works,  and the HX1 is sending midi commands onwards via midi thru.

 

I have set a patch up to toggle the HX1 on/off using a cc command on channel 3 which also works fine.

 

Here is the thing- I can’t figure out why the pc commands don’t work on the HX1 because they do on the other pedals. This is where I am at.

 

I have hx user presets saved at 000 and 001 in the HX1 and when I load the G3 preset (call it number 1) which contains the midi pc command 00, it fails to load 000. In fact, nothing happens on the HX1 but the other pedals respond. (The G3 can send up to 20 midi messages per G3 preset so effectively you just program in as many as you need). On the adjacent G3 preset (call that G3 number 2), I check and the toggle on off works. I go back to the G3 preset number 1, again, th epic message does work. Next I go into the midi menu in G3 preset 1 and I change the pc from 000 to 001. And then when I exit the menu, it executes the pc message and the HXone switches to 001. I then play about a bit more (change the HX one sound and go to totally different G3 preset) and when I go back to G3 preset 1 which now contains  HX1 preset 001, it is unresponsive. I then repeat the exercise, amend the midi message back to pc 00 and on exit from the midi menu, it triggers the HX One again which accepts the pc change back to preset 000

 

So it appears I have narrowed it down to either:

1. Fault on the G3 which appears to be sending the midi message on exit of the menu only but I rule that out as the other pedals work as intended with pc messages

2. Fault on the HX one which fails to recognise the pc change

3. User error and set up issue

 

the HX one is brand new and updated to 3.81

 

Belp very much appreciated!

 

 

[silverhead]

In the Settings View make sure the MIDI PC Rx parameter is set to “On” 

[RSVMark]

On 1/4/2025 at 2:04 PM, silverhead said:

In the Settings View make sure the MIDI PC Rx parameter is set to “On” 

It is already

[garryedgar]

Not sure if this will help any but I have an airstep midi controller and tested the PC midi command and it did correctly recall the presets.

 

My HX One is on Midi channel 2 as per the attached image, sending 0 called preset 000. I changed 0 to 4 and preset 004 was successfully called.

 

This was only one message being sent to HX One and it worked. 

 

I tried to add a CC message after the PC message to activate the preset after selection but that did not work. It called the preset which was in saved in bypassed state but the CC message to turn it on did not work after the PC message was sent.

 

Sending only the CC message to turn on the preset worked. 

 

I tried combining the HX One PC command with a command to activate another pedal preset on a different midi channel and both functioned correctly. 

 

Any chance you are sending more that one midi command to the HX One at the same time which is blocking the PC message?

 

 

 

[Bluepuma3]

How did u work around that issue? I have the same issue . 

[garryedgar]

On 1/8/2025 at 6:45 PM, rodri129 said:

How did u work around that issue? I have the same issue . 

 

Unfortunately I haven't been able to so I just have Prev/Next commands to navigate between presets and a separate switch to toogle on/off.

 

I read on another post that a wait command of a 50 milliseconds between the PC message and CC message may solve the issue. I can't do that with the airstep so don't know if that works. 

 

 

[garryedgar]

I thought about this again, and tested a Press command to send the PC message and a Release command to send the CC on/off toggle and it works. So I suspect the 50 ms wait between two messages would work in a similar way.

 

Not the way I'd want to do it but it would work in for certain use cases.

[RSVMark]

Still not fixed the issue. And it’s incredibly frustrating because there doesn’t seem to be any consistency in the error. Long post warning:

 

My GigRig G3s is controlling 3 midi pedals: channel 1 is an H9, channel 2 is a Jackson audio golden boy, and channel 3 is my new HX one. They are daisy chained G3>HX1>H9>Gb purely due to cables and pedal board layout.

i have changed the global settings of the HX1 to be channel 3 and midi thru obvs.

All midi commands (pc and cc) work as intended to the H9 and GB meaning the cabling works, and the HX1 is sending midi commands onwards via midi thru.

I have set a G3 preset up to toggle the HX1 on/off using a cc command on channel 3 which also works fine. This is on preset 10 and only sends 1 midi message, nothing else.

I have hx user presets saved at 000 and 001 in the HX1 and when I load the G3 preset number 1 which has 2 midi messages- one on ch1 to the h9, then one on channel 3 to the Hx 1. Both are pc messages and the one destined for the hx1 which contains the midi pc command 00, it fails to load 000. In fact, nothing happens on the HX1 but the h9 pedal respond because there are other pc messages intended for them. On the adjacent G3 preset (call that G3 number 2), I check and the toggle on off works. I go back to the G3 preset number 1, again, the pc message does work. Next I go into the midi menu in G3 preset 1 and I change the pc from 000 to 001. And then when I exit the menu, it executes the pc message and the HXone switches to 001. I then play about a bit more (change the HX one sound and go to totally different G3 preset) and when I go back to G3 preset 1 which now contains HX1 preset 001, it is unresponsive. I then repeat the exercise, amend the midi message back to pc 00 and on exit from the midi menu, it triggers the HX One again which accepts the pc change back to preset 000.

 

i have tried switching the order of the pc messages so the one to the h9 is after the one to the hx1, and that doesn’t work. The g3 has 20 midi commands per preset so I move the Hx pc change to command 3 (trying to simulate a gap by leaving command 2 ‘empty’ and there’s so change. 
 

I tried to add cc messages too: send a pc message to change patch, but then a cc to turn on….. nope. 
 

All hx1 presets are saved in the on state. So if the Hx 1 pedal is off, I am assuming the pc message changes the preset to the one desired and turns in on…….

 

i have a call with GigRig support tomorrow to check my G3 is working correctly but at the moment, all pointers are on the hx1 being at fault I am afraid…..

 

 

[RSVMark]

On another forum, a user reported similar issues, this time with a boss es8. Similar issue but the other way around- pc messages working but not cc. At this point it looks like hx1 has midi bugs remaining. Gonna go searching on this 50ms thing

[robertyboberty]

That other user is me

 

I've assigned the expression pedal input of my ES-8 to a CC on the HX One. My patch is set to call a preset on the HX One via PC and then control one of the parameters via CC

 

The HX One does not respond to CC data under some conditions

 

The only way I can get it to work is by changing the HX One to a different preset before I call my patch

 

If the HX One changes to a new preset via PC when I call the ES-8 patch the expression pedal works

 

If the HX One is already on the preset in the PC, the expression pedal won't work

 

There may be more going on but I this is the only way I could get it to work reliably

 

I have an H9 and a DM-101 on the same board that do not experience this issue

 

I'm using MIDI channel 8 for what it's worth

[garryedgar]

I have the same issue, tested it today.

 

My midi command sends a PC message to HX One to select a preset, waits 50 ms then sends a CC message to switch on effect. This works however sending the same command again, toggles the on/off state but freezes out the midi expression commands until I navigate to another preset.

 

I managed to work round it in my set up by sending the PC, Wait, CC command on first toggle position and then only sending the CC command on the second toggle position. Doing this navigated to the preset, switched it on and allowed me to switch it off with the same footswitch and retain the midi expression function throughout without the freeze issue occurring.

 

As you said it appears sending a PC message while already on that preset causes the expression freeze issue.  

[robertyboberty]

Just seen this issue discussed here (and better described)

 

https://www.thegearpage.net/board/index.php?threads/line-6-hx-one.2507027/post-39991722

[RSVMark]

Here is my response:

Hi,

This seems to be the way the commands are sent by the controller are you sending multiple MIDI commands at the same time ?
what happens if you delay the commands slightly, or if you only send some PCs on after another ?
you can also compare this by sending commands from another controller or a DAW
please check with the latest firmware and reset the HX One

To which is responded that I couldn’t because I only have one midi controller. So in effect, no real advice from them other than a check on firmware and a factory reset. I then received this response.

Hi,
it seems to be related to the way your controller sends the data
The messages must be slightly delayed, if you send CC and PC exactly at the same time, this can cause issues and it might not work as expected
If you only send one single PC alone and it works, it would be a indication for this

Again I have responded by pointing out that both other pedals work fine with multiple midi messages and that multiple messages with cc messages work but multiple messages with pc don’t. 

 

I await their response.

 

A helpful person has also provided this- The zatch_attach guy on TGP says Line 6 confirmed it as a bug to him. The CC messages don't work when a redundant PC message is received at the same time. If a new PC message is received at the same time CC will work. This proves that the HX One is at fault. Adding a slight delay between messages is a workaround, or calling an arbitrary PC beforehand

Hoping they realise the issue is subtly different in that I am struggling with pc messages but seems very similar.