silverhead

I find it handy to backup the factory setlists immediately after updating the firmware. That way you will have a backup copy of the factory presets on your computer, not just on the device.

You use different presets to do this. On the POD HD500X you can't assign those things to footswitch control within a preset. What you can do is specify the Variax settings (model, tone/vol knob positions, tuning) as part of the preset definition. Using different presets you can arrange to have those settings change when you select each preset. I believe these settings are on the Mixer page of HD500X Edit.

I don't know if the POD HD500X/ProX will receive further updates but they are still being manufactured. At the price point they remain a great value even without further updates. And I think you're right that Helix may in fact have spurred HD sales. Many HD users here have said that they felt no need to spend a great deal more $$ to buy Helix; the HD meets their needs. That may have persuaded some tire-kickers to save some money and buy the HD rather than Helix. Nothing wrong with that, and I bet they're happy.

Unfortunately the current IR management procedures in Helix are not sophisticated. Line 6 has said they are working on this and we can expect improvements, but no date has been forecast. Meantime that's the way it is. Many people, including myself, use a manual numbering system. I add a 3-digit prefix, representing the slot number 001-128, to each IR name after importing the IR. I then Export it to a specific IR folder with the new name. After updating I go to that IR folder, order the files alphabetically (the numbers force the proper ordering of IRs), select them all and drag/drop them in a single operation into the IR area of the Helix editor, beginning at slot #1. It's a pain but it works.

Ha Ha!! Don't forget the global reset after the rebuild. ðŸ˜

I hadn't noticed that the earlier release notes are deleted from the announcement thread as new updates are released. Your suggestion for easier searching is a good one. Meantime, all release notes continue to be available in the Downloads area. The history of releases in that area of the website continue to show the earlier release notes.

I can understand waiting to install updates for possible performance reasons (bugs). But there's no general reason for the installation itself to fail if you follow the instructions other than purely technical issues with your computer environment. Other's experiences won't help in this regard. To rccampeon: you might as well get the update issue resolved now. Your problem won't suddenly disappear. Start at the beginning again. Download and install the Helix editor (not firmware) package v 2.20, which includes the editor, driver and Line 6 Updater program. Follow the instructions carefully. Let us know exactly where/how it fails and we'll help.

Now you run the Line 6 Updater program (make sure you are using v1.11 of the Updater program) to install the v2.20 firmware. This should all be in the release notes, is it not?

After selecting Helix in the middle field on the Downloads page, did you find the Get Download button at the bottom of the release notes panel? Use that.

At the bottom of the release notes is a button that says Get Download. That's what you may be missing.

Try a different browser, or try deleting all Line 6 cookies. Then try to register again.

Ahh.... that's more understandable. Sounded like this volume stepping was the sole reason and that you would wait for it to be fixed. That'll be more than a few days!

That's too bad. Here's the release note about this: "Subtle stepping may be heard when adjusting the main VOLUME knob while audio is present" So ask yourself: how many times/situations do I actually use the master Volume knob while sound is passing through the device? Is that really not a very minor and avoidable annoyance? Is it really worth denying yourself all the benefits of the new firmware?

I think there's a judgement call that needs to be made concerning what to include in an operations manual, especially when it comes to the detailed parameters of amps/FX and their use. I think any operations manual for a modeling device needs to focus on the unique aspects of the specific modeling device (e.g. Routing, inputs, outputs, preset construction, etc...) and not get into the specifics of the devices being modelled other than to identify them. To elaborate, each type of FX being modelled has its own set of parameters whose meanings are not Line 6 specific. They are generally understood within the context of the FX type. Any reverb device has parameters for things like decay time, predelay, etc. Delay FX have time, feedback, sometimes mod, and other parameters. Chorus nad other mod FX use concepts like rate, depth, sometimes waveform, etc. These are industry standard concepts and, while their usage may differ slightly among different devices I don't think it is Line 6's job to document all of this. So I think Line 6 documents can seem to be lacking when it comes to the use of their modelled FX, but trying to include all these details would be both intimidating and redundant. Users need to consult the manufacturer's documentation of the devices being modelled to get this. And one of our generous users has produced a vary handy website to help with this. See helixhelp.com And there will always be disagreement about where to draw that line..........

Not sure about the global settings and bundles. The reason I don't use bundles as a transition between firmware updates is that after updating and reinstalling the backed up bundle you overwrite any new factory presets in the new firmware. Prior to updating I back up all setlists including the factory setlists. That way I can restore any old factory presets that may have been replaced in the new firmware if I particularly liked them.

Did you perform the global reset after the update as described in the installation procedures?

Did you also update the editor to v2.20?

Try turning off Helix and disconnecting the VDI cable. Turn Helix back on and reconnect the VDI cable. This will reset VDI communications and may enable proper communication with Workbench HD through Helix. I have found it best to disconnect the VDI during a firmware update.

You're right - the release notes do say that. It's an error. The latest Workbench HD is version 2.13. Helix is compatible with this version as a Workbench HD interface device.

Display issues are sometimes the first indication of a failing power supply. Try using a new wall wart. If you don't use an official Line 6 PSU MAKE SURE the specifications are the same. http://store.line6.com/accessories/power/dc-3g-power-supply.html

Taking a personal attack personally? How could I not? Anything I could rebut? How about the many assumptions in your last post that are similar to those you castigated me for? You created an entire fictional user-in-store experience that involved many more assumptions than my support forum assumptions. Embarrassed? Not at all. Goodbye.

All of that is just an assumption on your part. Where are your facts?😎😀 (for readers who may be confused by my comment, see the discussion beginning in post #18 in this thread).

Not sure I understand what you're getting at. Like the POD HD, Helix also has an editor. Within the editor of course you can see the list of installed Helix setlists and presets, factory and custom, just like the Pod Edit pictures you are showing here. I thought you were talking about an independent listing in something like PDF format, available outside the editor.

There is no list of factory presets maintained by Line 6. If there were it would be outdated routinely. Each new firmware update usually changes the presets. The next update is expected later this week. As far as I can recall there is no factory preset called Son of Plexi in Helix. That was a POD HD preset.

There are 3 inputs for expression pedals on both Helix Rack and Helix Control. The fourth is for an EXP toe switch. The two devices share the same virtual inputs. So you can only use 1 EXP-1 pedal, connecting it to either device - not both. You can use a total of three, not six, EXP pedals.