matsonf

Thanks cruisinon2 - agreed, and that was something I verified using good headphones to make sure it wasn't in fact the guitar.

Thanks HonestOpinion - I did question at first whether I was hearing my guitar directly. Once I put on headphones, I was still hearing it come through the signal. Positioning of the effect had the biggest improvement.

Thanks zappazapper - that is true. Fortunately, basic re-ordering of effects seems to have resolved the biggest part of the problem.

Thanks DunedinDragon - as you suggested, placement in the signal chain turned out to be the main culprit. After making changes, the experience is definitely better.

Thanks amsdenj - the latter suggestion turned out to be the key factor. I switched things around quite a bit to put the poly capo up front on Path A with all other effects moved down to Path B. I then put a split on Path A to route everything into Path B. That took care of the dissonance.

Anytime I use Poly Capo, I'm hearing dissonance in the tone, where the original pitch in addition to the Poly Capo pitch comes through, e.g., +1 (to raise pitch by a half step). Secondly, and possibly related, the tone gets more corrupt sounding the farther from 0, whether plus or minus. Is anyone else experiencing this? Version 3.01 was to fix potential audio corruption, but maybe those were different issues.

I had a similar error. I was initially attempting to update the floor Helix using HX Edit (from v2.30 to v3.00), when the HX Edit software crashed mid-process and the Helix got stuck in the boot error. I was unable to get the laptop to recognize the connected Helix after that point until I: (1) powered off the Helix, (2) with the USB connected to both the laptop and Helix, booted the Helix using FS 6+12, (3) started Line 6 Updater software instead of HX Edit and logged in to my account. From there, I was able to select my device and restart the firmware update, which completed successfully. I came across this thread shortly after the process, and it's effectively a limited version of what others have posted and matches pretty well with what Tech Support suggested (steps 3, 4 and 6), not that I'm advocating shortcuts. This is just what worked for me.