Andreas0815

Reproducable even with firmware 3.60. Sometimes the CCs get processed immediately, but at times there is a freeze of 5-10 seconds and suddenly the CCs get processed in fast forward, like if the processing took so long. Could be hint for a software issue in the midi processor of HX, resulting in an overload if too many messages arrive in short time? In my setup there is Midi over Bluetooth in the signal chain, so I have to check the signal flow before the HX first and will postvthe results here. But I remember a similar problem in old firmware versions with midi CCs over midi cable from Zoia. Looks like there is no midi message filter to protect an overload to me. Thanks im advance! :) Looking forward to a statement from Line6 to this issue.

Hi Line-6 & community, I came across the following issue on my HX Stomp (firmware 3.50) regarding TAP Tempo Function: a) Using footswitch FS3 (works as expected): 1) Assign FS3 to Tap/Tuner. 2) Send Midi CC 51 (Emulates FS3) with value 127 to the HX stomp 3) Wait for 1-2 seconds Result: the device switches to the tuner display (as expected). b) Using footswitch FS5 (inconsitent behaviour): 1) Assign FS5 to Tap/Tuner. 2) Send Midi CC 53 (Emulates FS5) with value 127 to the HX stomp 3) Wait for 1-2 seconds Result: the device does *NOT* switch to tuner display, other than the previous example! As a workaround a separate cc 68 message (Tuner screen on/off) can be send to the device, but this requires a more complex setup or more dedicated external switches which is sad because it works perfectly using footswitch FS1-3 assigned to Tap/Tuner and using their corresponding CCs. Dear Line6, please let me kow your opinion about this issue/inconsistency. Kind regards in advance, Andreas PS: Loving the HX Stomp, it is just so versatile... and after this bugfix even more so! ;)