phil_m

This is what Eric Klein (the Line 6/YGG Chief Product Architect) said about it - https://www.thegearpage.net/board/index.php?threads/line6-helix.1586637/page-3242#post-29615341 It's all translation costs. If we only needed to do English, I'd already have written a 500-page behemoth for everyone to peruse on the toilet. Instead, trade law legally obligates us to provide content-identical manuals for any hardware we manufacture in TWENTY-SEVEN languages. The money we spend every year on manual translations could pay for additional engineers, and we'd much prefer the latter. For whatever reason, software doesn't have the same stipulations, so the manuals for HX Edit and Helix Native get updated every single rev. TL;DR: I'm not happy about it either.

Well, the HD series was first introduced in 2010, and it received the last firmware updates in 2015, but it’s not like they all died after that. Line 6 Monkey will still work on the latest versions of Windows. It’s Apple’s decision to drop 32-but support that has been problematic.

Oh, yes, I forgot about that… They do update the manual for POD Go Edit with every firmware update, so that will include all the relevant new features. They don’t update the hardware manual because of international regulations regarding translation and having translated manuals available for dozens of languages.

Monkey is a 32-bit application, and Big Sur has no 32-bit support, so there’s no way to make it work.

You need to have the looper as the last block in your signal chain if you don’t want any of the other blocks in the preset to affect the recorded loop.

There shouldn’t be any dropout between snapshots, but I’d need to understand more on how you have each head connected to actually guess as to what’s going on.

Well, I don’t think MIDI CCs would be a viable solution, as there are way more potential parameters than there are available CC messages. CCs would work for a simple MIDI controller feedback where you’re only controlling certain things, but it wouldn’t be a way to reverse engineer an editor.

That would require MIDI Sysex, and Line 6 didn’t go down that road with any of the HX/Helix stuff.

If you use the LT’s USB audio, you can use USB7 for the unprocessed dry signal. It’s much easier than doing with an ABY box.

I’m not saying that Native won’t work in High Sierra. I just know what sometimes the download page automatically sets the OS field, and sometimes stuff doesn’t show up in searches because of that. Sounds like that’s not the case, though.

High Sierra is probably the issue. The newer version probably don’t list High Sierra as a supported OS. You can manually change the operating system field in the search to a newer operating system to find the newest version, though.

Make sure you’re signed into your account in POD Go Edit. Click on “My Account” in the lower left hand corner of the screen to do that.

You don’t need to have the Stomp registered to download any of the relevant software. It really only matters with respect to the Helix Native discount or warranty coverage.

Within the same snapshot? You can assign the Topology parameter to a controller just like any other parameter. So you could toggle back and forth between two settings with a footswitch if you want.

I doubt there will be a 1.3 manual. There was a 1.2 manual because it coincided with the release of the POD Go Wireless. But typically, Line 6 only releases new manuals for major number releases. Any relevant information on the use of the new features with the 1.30 update are described in the release notes.

If they’re greyed out, that just means there’s not enough DSP left in that particular preset to load them in that slot.

Did you buy the HX Effects new, and/or do you have the box? There should be a serial number sticker on the end of the box as well. Other than that, I’m not sure what else to tell you. Open a support ticket and see what CS recommends, I guess.

Make sure you don’t have phantom power on the channel you have the Helix plugged into.

No, there is no compatibility between the HD500 and the POD Go.

Just power the unit down and try updating again. If you’re still having issues, try sending the update with Line 6 Updater instead of POD Go Edit.

You’d want to select USB 3 or 4 as the input from the POD Go, not USB 1 or 2. That’s the dry DI signal from the guitar input. Then it doesn’t matter what’s in the POD Go preset. If you don’t want to hear the sound from the preset, just mute it by keeping the volume pedal down.

Line 6 Monkey doesn’t support the Helix or HX devices - that’s correct. All you need is HX Edit. And there are no ads-ons or model packs for the Helix. There’s Helix Native but that license is tied to your Line 6 account, not to the Helix/HX hardware. All you need to do to register your HX Effects is go to the Line 6 site and register it.

The factory preset names should be showing up. If they aren’t, someone probably updated it and didn’t do the factory reset after updating. To do the factory reset, hold down footswitches C & D while powering up. Of course, export any preset you may have created that you want to keep before doing this.

You need to make sure you have the POD Go’s FX Loop block turned on for the 4CM to work.

You would need another pedal that converts MIDI clock to a tap tempo signal to do that. Disaster Area Designs has several pedals that will do it.