jdomine

Hello. I can confirm there is some sort of issue with the Glitch Delay in 3.70. Comparing it side by side to 3.60, it is very obvious. On 3.70 after changing the Time parameter to Note divisions it seems to essentially stop working completely. I have attached audio examples of what I'm hearing. Do they line up with what you're experiencing? I have logged a bug for this. It will be addressed in a future firmware update. Thank you for the report. Glitch 3.70.mp3 Glitch 3.60.mp3

I am able to reproduce this and have logged a bug for it. Please note that this also occurs when exporting/importing a preset or when restoring from a backup. Thank you for the report.

Hello Jack, If you could post the preset here I would be happy to check this out and see if I can also reproduce it.

Hello. I am able to reproduce this. It seems to be an issue tied to HX Edit. If I duplicate a preset by saving it to a new location using the hardware itself, the change to Heel Down does not happen. It only occurs when copying and pasting a preset with HX Edit. I will log a bug for this. Thank you for reporting it.

Good find. I have logged a bug for this and the 4-Voice Chorus. Thanks for reporting it!

I am able to reproduce this and have logged a bug for it. It seems to go all the way back to 3.00.0 if not further. It does not seem to happen if you use EXP1 for the ext amp control and EXP2 for expression. For now I would recommend using this configuration as a workaround.

If you could email the problematic preset to me at jdomine@line6.com or attach it here I'd like to test this out.

Thanks guys. I can reproduce this using the attached presets and have logged it as a bug. Appreciate your report!

This is indeed a bug. I have logged it for review by the team. Thank you for the report!

This sounds like your DAW is sending MDI CC 68 to the Helix to activate the tuner. Try changing the midi channel in the global settings on the Helix. You can also use a midi message monitor to see if you daw is sending CC 68.

If you unplug the USB cable after it has become unresponsive does that snap it back into functioning?

Is your keyboard sending out MIDI clock or any other MIDI data constantly when powered on? Simply having something plugged in via MIDI din should not matter but I could see flooding the MIDI stream with clock and other things could theoretically cause an issue.

I am able to reproduce this easily. I noticed that if I deleted the looper block at the end of path 2B the problem goes away. Do you use that looper at all? If not I recommend deleting it from the preset until the bug is fixed. The bug seems to be that if you load a preset with a looper on a B path after coming from another preset with a looper on a B path audio stops passing.