silverhead

Well, that explains it. If you were using the v2.20 editor that you downloaded after receiving the device, and pre-v2.20 firmware that was previously installed in the device you would certainly have problems loading the Auto-swell FX that was introduced in firmware v2.20. The editor would display it but the FX model does not exist in the firmware. Let us know if you have similar issues once you are running v2.21 of both firmware and editor. Be sure you follow the installation instructions carefully, beginning with the editor (not firmware) package. To get the editor package installation file go to the Downloads area and select Helix in the middle (software) field, not the leftmost (Products) field. Read the instructions and, when instructed, use the Get Download button at the bottom of the instructions panel to download the editor v 2.20 installation file. Install all components (editor, driver, Updater program).

I essentially do this now using a custom preset in the TEMPLATES setlist. I create a lot of FX blocks with my favorite settings and simply store them in this preset. The preset is not meant to ever be used for playing - it's just a repository. I then save this preset for safekeeping and archive purposes. Then, at any time, I copy/paste this block with my preferred settings into any desired preset under construction.

I agree. But some people may not do it. I just want to understand whether or not any reported problems can be related to that, so that I can guide/inform others accurately. I'm just suggesting we, as a well informed community, keep an eye on any reports.

Did you then install the editor after downloading? There's a new version of the editor out yesterday (v2.21). Try downloading and installing it again, including the updated driver and Line 6 Updater program.

Yes, the driver and the Updater program are both bundled with the editor package installation file but when you run the installer you can choose (via check mark) which of the components you wish to install. My interpretation of the release notes for v2.21 is that you only have to install the editor itself. There seems to be no update to the Updater program so no need to install it. My question is: what about the driver? Does it NEED to be installed or not? No harm in installing it, just wondering if some people will get in trouble by not installing it.

Hmmm... curious. I wonder if the driver update is actually important for this editor update? The editor release notes say that all you need to update is the editor itself, so I presume that means the driver update is not required. The timing is suspicious though. I guess we'll see if there are any problem reports that could be related.

v2.62 is the latest and current firmware release.

Search Customtone under the username CBTL. He has uploaded some really good Gilmour presets, including Shine On....

Make sure you turn off any existing Cab block in the factory presets when you introduce an IR block. Many presets use integrated Amp+Cab blocks so in those presets you will need to replace it with just the corrresponding Amp block. Note it's settings first before deleting/replacing it.

Sure - no loss of quality.

Not that I'm aware of.

Select POD HD (or the exact POD HDxxxx model you have) in the Products field drop-down menu, and select Flash Memory in the Software field (or leave it at All Software to also get the edit program and the driver).

Note that Firehawk FX firmware v1.30 was released yesterday. Make sure to restart this thread in a few months, though!!

The labeling on the device outputs is informative. On the HD500X each of the 1/4 Outputs (L and R) will sum the signal to mono if only one is used. That's indicated by the L/MONO and R/MONO labeling. If both are used they become a stereo pair. The XLR outputs, however, do not sum to mono as indicated by the absence of the MONO in their labeling. If you use only one output you will get the corresponding half of the stereo signal.

Yes - you can name snapshots. See Helix manual Rev D pg 37. You can also do it in the editor by right-clicking (or left-click and hold?) on the snapshot name.

OK - thanks for explaining in more detail with the operational context. I get your point.

Yes. Go to the Downloads section of this website and choose the pod xt live from the Products list.

I'm not sure I understand the difference. Assigning the Up/Down footswitches allows you to 'use the same footswitch every time and move through the proper snapshot progression', assuming of course that you have previously arranged the proper progression. What am I missing? Note that you can change the Up/Down assignment almost instantly between Banks, Presets, and Snapshots by holding down both switches momentarily. So no need to mess with Global Settings if you want to change between songs.

Have you tried assigning the Up/Down footswitches to control Snapshots rather than banks or presets and setting the display to 8 Snapshots? I think this will do what you want - proceed forward through the snapshots using the Up footswitch, and backward using the Down footswitch. The active snapshot and its scribble strip name will always be indicated and displayed. You can make these assignments in Global Settings -> Footswitches.

Be aware that 'trying out' Helix is not like trying out your average pedal when you walk into a guitar store. The salesman is likely to have little to no knowledge of how Helix works. He will probably sit you down with a guitar plugged into Helix and the 1/4" output connected to a regular guitar amp input. Then you'll wander through some presets (designed for an FRFR output) and you'll conclude that Helix sounds like $hite. Ask that the Helix output be connected to an active (powered) studio monitor or PA speaker.

Hmmm......... sounds like you may have used an outdated version of the Line 6 Updater program to update the firmware to v2.2. If you have further operational issues I would do a complete reinstallation of the editor package (including Line 6 Updater and driver) and firmware, this time updating to firmware v 2.21.

The FX Loop block corresponds to the physical loop outputs on the device itself, for external pedals. You position the FX Loop block where you want the external pedals to be placed in the signal chain. It has no relation to the mod and delay blocks, other than their relative positioning. Your external pedals will be patched into the signal chain wherever the FX Loop block sits.

Yes, the FOH sound guy will make these cuts as desired for any specific venue/situation. Also, the 'spectrum of what should be there' is the full spectrum of the human ear's perception. It's not the 'spectrum' of what the cab produces. Whether the sound your ear hears is mic'd or not (i.e. the 'cab in the room') your ear (and the mic) perceives the full frequency range. Your cab will sound different to your ears in different rooms due to the room's acoustic dynamics. These sound differences are real, and 'should be there'. There's no absolute sound of the cab - it's relative to human/mic perception. An analogy would be human vision and colour. I'm sure you've noticed how the colour of any object changes relative to the lighting in the room. Bright sunlight, cloudy daylight, electric lamp light - all of those affect the colour that your eye/brain perceives. Every time you see a shadow you are perceiving this. A shadow is essentially a perceived colour change due to the change in lighting (direct vs. indirect). The object might have a very specific 'colour' as defined in scientific terms by the wavelength frequencies it reflects - but that's not what your eye perceives in all circumstances. The sound of a cab in a room, as perceived by a mic or your ear, behaves similarly. While the cab may have its scientific specification in terms of frequencies, that's not all that the mic/ear perceives.

Two reasons I can think of off the top of my head..... 1) As already expressed by tedulrich, no matter where Line 6 decided to arbitrarily make the lo and hi cuts, different users on both ends of the spectrum would wish they decided differently. 2) Perhaps more importantly, remember that Helix models the mic'd sound of the amp. That means that frequencies beyond the range produced by the cab are captured. Room reflections, added boominess from the cab sitting on the floor vs. raised on a stand, etc..... All of these tonal frequencies are captured by the mic. So these frequencies are not problems or inaccuracies in the modeling. Line 6 accurately provides the full range of captured frequencies and lets the user decide where to cut based on their personal preferences. There's nothing 'incorrect' about what's captured by the mic.

I prefer recording direct using Helix via usb as the audio interface. It eliminates a D/A and A/D conversion in the signal flow. Helix is also an extremely powerful and flexible interface with 8 in/out channels, supporting direct dry signal recording and easy hardware reamping.