garryedgar

My support ticket received the following update so hopefully the issue will be resolved in a future update! Hi, I can reproduce this and have escalated it for further testing Best regards Line 6 /Ampeg Support Europe

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.

Glad it's not just me!! I've logged a ticket with the line 6 team which has been acknowledged and I'll share any info I get back.

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.

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.

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?

Thanks, will do

HX One Firmware 3.81 and is set up in insert (4CM) configuration. I have observed the following behaviour for some time and only just now been able to replicate the issue consistently. Scenario 1: When moving from a PolyWham effect preset with the status ‘off’ to Feedbacker effect preset status ‘on’ or ‘off’ results in feedbacker effect not triggering. Toggling the HX One On/Off device footswitch while on the feedbacker preset in this scenario does not correct the feedbacker issue. Scenario 2: When moving from PolyWham effect preset status ‘on’ to Feedbacker effect status ‘on’ or ‘off’ results in results in feedbacker effect working as expected. Toggling the HX One On/Off device footswitch while on the feedbacker preset in this scenario also works as expected. This issue is occurring whether presets are navigated view Prev/Next midi command or by the in-built footswitch preset navigation. The same observations occur when moving from the PolyCapo effect to Feedbacker so it may be related to moving from pitcher shifting effects? This issue does not appear to occur if moving from another effect such as Dynamic Plate, Tube Comp 3 Note Generator to the Feedbacker effect. It also appears that if scrolling past another effect between PolyWham and Feedbacker resolves this issue e.g. if a had 3 presets in the sequential order PolyWham > Dynamic Plate > Feedbacker the issue is not observed when scrolling past between PolyWham to Feedbacker using the preset scroll function. It seems like the pitch shifting (PolyWham/PolyCapo) effect preset status is being passed on the feedbacker effect when navigating directly between the two irrespective of the saved Feedbacker preset status. Has anyone else had the same experience or can replicate this behaviour?