phil_m

Discharging the battery completely shouldn’t kill the unit. Before you buy a replacement, I’d suggest opening a support ticket.

If you want to copy patches and IRs from one Helix to another, the easiest way is probably using the Restore from Backup feature in HX Edit and selecting the setlists you want to transfer. You can also load all the IRs from one Helix to another using the Restore from Backup.

You need to download and install HX Edit 3.0.

Some of the delays have maximum delay times that are lower than others. The Memory Man (Elephant Man) model, for instance, has a max delay tome of 500ms. If you tap in a time that would result in the delay time being longer than that with the note value you have selected, the Helix will automatically shorten the delay time to the next longest value that’s still in time with what you tapped but is still within the max delay time limit. Ben Adrian, the lead sound designer for the Helix, explains it here: https://www.thegearpage.net/board/index.php?threads/line6-helix.1586637/page-1701#post-23642314 There’s only a few delays that behave this way. Most have much longer max delay times.

Which Apollo? If it has S/PDIF or AES/EBU inputs you could use those to connect the Helix and not have any additional D/A-A/D conversion, but otherwise, no. You'd have to use the Helix as an interface to record without additional conversion.

Have you don’t a factory reset since updating?

In HX Edit, go to File>Restore from Backup.

That noise is related to the Tempo Pitch parameter under Global Settings>Preferences. Set it to Transparent if you don’t want to hear it.

Well, it’s not really digital clipping. It’s more like an overload. The only block that you can really induce digital clipping in is the Vintage Digital Delay, and that’s only if you have the Bit Depth parameter set lower than 16 bits. For everything else, the signal path is always at 32-but floating point, so it’s virtually impossible to induce real clipping at that point. One thing I’d make sure is that your preset level isn’t too hot. It is possible to clip the output converters, so it’s possible that you could be close and then a block pushes it over the edge. With the Bubble Vibrato, I’d suggest lowering the input going into the block. You can always lower the Channel Volume parameter in the amp block, for instance. Then compensate somewhere else down the line if you need more level.

I'm not sure what hoops Line 6 is exactly making you jump through anymore. Everything is done with HX Edit now, but Line 6 Updater should still be working for you. The Fractal update process isn't really all that different as they have a separate update utility called Fractal Bot, which is analogous to Line 6 Updater. Usually update problems come down to specific USB cables or USB ports being problematic. I'm not sure why Updater isn't running for you. It should be. Try uninstalling stuff and reinstalling, I guess. When you say you checked to see if 3.0 was compatible, did you actually download and install HX Edit 3.0? Many people assume HX Edit updates itself automatically. It does not. You need to download and install the latest version.

Yes, if you have a single transmitter and have both receivers set to the same channel, they'll both receive the signal.

Variax isn't being discontinued, and Line 6 isn't abandoning the concept. The main reason (well, the only reason, really) the POD Go doesn't have a VDI port is that adding that port would have added another $50 to the price, and they were concerned about increasing the overall cost with a port that the vast majority of buyers won't use. I'm sure they would like it if every POD owner bought a Variax, but the fact is that only a relatively small percentage of them do. And those that do tend to be more "power users" to begin with, so they would be more likely to go with something like the Helix LT or Floor anyway.

You need to download and install HX Edit 3.0. This is a symptom of having the older version of HX Edit with the newer version of firmware.

My smiley face was very gentle...

I expect there will be a Big Sur compatible driver soon.