silverhead

Not sure I'm understanding your terminology so I'll make an assumption: when you say Song 1 Preset1 - basic Rock setting and Song 3 Preset 1 - Basic rock preset you are using the same preset/settings with no tonal differences between Song 1 and Song 3. If that's correct .... Yes you can manually move through your songs by selecting the appropriate preset using no copies of presets. However in the example you provide above you won't always be 'advancing' through your presets and it will sometimes take more than one tap on the up/down buttons. In your example you would arrange your presets to be in the same bank, say Bank 1, and since you are only using 3 presets so far you would assign them to footswitches/presets A through C. You would begin Song 1 using Preset 1A. You would move to Song 2 and hit the Up button to advance to preset 1B (having used the Global Footswitch settings to have the Up/Down buttons move through presets rather than through Banks or Snapshots). For Song 3 you would use the Down button to go back to Preset 1A. Then for Song 4 you would hit the Up button twice to select Preset 1C, then Song 5 would be the Down button to go 'back' to preset 1B. More Up/Down button pushes will be required as your setlist expands to include say 15 songs using say 8 or more different presets in 2 or more Banks. In that case you can experiment with the Global Footswitch settings to use the Up/Down buttons to move between Banks rather than Presets and use the A-D buttons to select a specific Preset within the given Bank. If you want to arrange your setlist so that you consistently use only the Up button to change presets between songs you will need to make copies of presets and arrange them in the appropriate order. As you say, this makes future edits more complicated.

Accessories should include gig bag, battery/charger, usb interface device/cables (different from a VDI cable which is not included), and a set of Allen keys that fit various screws/adjustments. The plink issue will not be noticeable unplugged; it involves the piezos and modeling which requires power. It's a very rare issue I think but in some cases very disturbing. Chances are high that you won't see it. I would also visually inspect the VDI connector for damage. The pins are visible and should be straight; look for bent pins. This is normally fixable but it's better not to have to. The quality of the modeling (new vs. old) is highly subjective. Some people have never updated to v2 modeling because they prefer the older models. Others rave about the new vs the old. in my opinion they're all good - just different.

The POD HD has no ability to use IRs directly so I assume you mean routing the output of the POD into a separate HX FX device. That can certainly be done but you would have to configure your POD and HX FX presets appropriately. Specifically your POD preset should not use any cab/mic models.

I would reinstall the firmware and see if you can reproduce this. Sounds like a firmware corruption to me. But if it's reproducible please report it.

You use the Line 6 Updater program to update Helix firmware. Make sure you download the latest Updater program. Actually you don't need to download the Helix firmware file (the hxf file you mention) at all. The Updater program will download and install it for you. But since you've already downloaded it you can save a few seconds of your life by using the Install from File option in Updater.

Depends on your setup. If the mic you are talking about is connected to the Mic input on Helix and you are planning to dedicate one of the Helix paths for this purpose then yes, you can arrange the preset so that a footswitch or the onboard pedal can control the mic channel volume, essentially muting it by dynamically setting the volume to a zero level. You would have to do this on each Helix preset - there's no global setting for this. Do you want to talk just to the band (without the audience hearing you)? If so that's a different issue and I'm not sure Helix has a solution for that because I've never experimented with that requirement. Perhaps others have a solution for that using Helix.

I had no problem using the url directly. I'm running Win10 with Firefox. I initially had a problem using the link in your original post. I got a 404 then but it seems that has since been corrected.

There is no conversion required. Every preset contains 8 snapshots at all times. You can either use the snapshots or ignore them, which actually means that you are only using Snapshot #1. Every block in the preset signal chain exists in all snapshots, and if you haven't yet customized the snapshots the blocks are all in the same on/off state in all 8 snapshots. in order to begin customizing snapshots for different block on/off states simply select Snapshot#2 and manually turn each block On/Off as desired. Save the preset before selecting another snapshot (Use the Global Snapshot editing parameter to control whether you want to Recall or Discard Snapshot changes within a preset while editing). Continue with Snapshot #3 and customize it, then #4 and so on.

From my limited testing re: the on/off state of new blocks and snapshots I see the same behaviour despite the age of the preset (new or old) and the number of customized snapshots. What I observe is independent of the mirroring of latter snapshots and independent of the saving of the preset or snapshot. What I observe is this: when you add a block to any preset it is by default, and immediately, in the On state in all snapshots in that preset. In other words, you cannot add a block in the bypassed state. It doesn't matter how many snapshots you have already customized. Doesn't matter how the mirroring of later snapshots behaves. Doesn't matter when you save the snapshot/preset or whether the Snapshot editing parameter is set to Discard or Recall. In all cases a preset contains 8 snapshots at all times and a newly added block appears in the On state in all 8 snapshots. From that point things behave as if the block had previously existed in the preset, in the On state in all snapshots. If you want to change the state in different snapshots you must bypass it manually and separately in individual snapshots, one snapshot st a time, saving them immediately or later depending on the Snapshot editing parameter setting.

You're right. Sorry for the misinformation; FX blocks themselves are always 'assigned' to the snapshot controller. Their parameters need to be specifically assigned to the controller but the On/Off state of the block is part of every snapshot. This is true even of the first block added to an empty preset where no snapshots have yet been customized. The preset still has 8 identical snapshots, all of them with the one and only block ON. This remains true with the addition of every new block in the preset. EDIT: After a bit more reflection I'm not sure that Ideascale suggestion will get a lot of support. Seems it boils down to the default on/off state of any block when added to a preset. Should it be On or Off when you add it? Seems to me that in the vast majority of situations you're adding it because you want to use it, which means it should be On. Changing the default to Off (which with the current design would seem to be the way to achieve what you want) would be counter-productive about 99% of the time.

When you add the reverb block do not assign it to the snapshot controller. Turn it OFF and save the preset. Since it is not assigned to the snapshot controller it should now be OFF in all snapshots. Later, if you want it on in a particular snapshot, assign it to the snapshot controller and turn it ON only in the one snapshot. Save the preset.

Not ugly. Just inferior!! Hah! (Just kidding, all. I know there are lots of very satisfied HD owners who have no intention of moving to Helix. I'm not slagging y'all, just having some fun.)

Manual recreation as you have done is the only way to do this right now (and maybe ever). There is no converter. And there likely will never be one since, as you've already noticed, straight conversion does not yield the same tone. That 'tiny bit of tweaking' you mention pretty much defeats the purpose, I think, in terms of anyone considering this task to be worth the significant effort. Another observation about this that I have made many times (you're not the first to suggest this) is that HXN is capable of producing much higher quality tones than the POD HD. You're doing yourself a disservice if all you want to do with HXN is reproduce inferior tones. Rather than recreating HD presets and tweaking, try starting with a blank preset in HXN and build your own (superior) tones. It will take some practice and experience but I think you'll soon see why there's not much interest in a converter, at least not that I've seen.

Very cool tool. Highly useful when wanting to experiment with new IRs without impacting existing presets. Just use currently unused IR slots. Thanks.

The Multi setting includes the Variax input, which is either a Variax model or the mags - not both. Specifically, the Multi input does NOT include the Variax mags. The only way you get the Variax mags with the Multi input is if you have the Variax guitar set manually to mags ( i.e. turn the modeling off). The Variax Mags is a separate Helix Input setting. It always selects the mags as the input regardless of whether the Variax modelling on the guitar is on or off.

That tech is misinformed. All requests to L&M for Line 6 repairs should be accepted by L&M and referred to their owner, Yorkville, for repair. L&M is the repair intake/outlet location.

How are you controlling the selection of the input blocks to switch between your clean and distorted sounds? Check the parameters involved to make sure that when your clean sound is silenced there is no amount of dry signal allowed to pass through.

Do you have an iOS or Android cell phone? The app works on those devices too.

You just need to install 2.60

For future reference you should always begin a firmware update by downloading and installing the HX Edit installer package which includes the latest (and guaranteed compatible) versions of the driver and the Line 6 Updater program. Then run the latest Updater program to install the firmware. Installing the firmware in isolation, with potentially outdated driver and Updater, can lead to more complicated compatibility issues than just the new models not showing up.

Can't be done with the current architecture. If you're not happy with any update you can always reinstall the previous version, although any presets created with the new version may no longer be compatible.

When Helix Native is installed it replaces any earlier version with the installed version. Only one version is installed and available at any time.

You also need to update the HX Edit program to v2.60.

I agree. HX FX would be the better choice.

Sounds like a good Ideascale item......