silverhead

From the manual (as of firmware v3.0): “For path Input and Output blocks - These blocks display with a green fill to indicate a signal is present and a red fill if the signal is too hot. If clipping is indicated you should reduce the signal level before and/or at the red indicated Input/Output block.”

There’s also probably a technical limitation based on the ASIO protocol that Helix uses. That protocol requires that a single audio device be used at any time.

No, Helix has no permanent loop storage.

Of course I can’t hear exactly the sound you describe, but I can say that it’s not unusual to have strange sound artifacts when switching snapshots. One of the key benefits of snapshots is that there is no audio gap when switching. The downside of that is that a drastic change in the sound of the snapshots is instantaneous and audible. Seems to me that an instantaneous change from an acoustic guitar to a driven electric guitar might be drastic enough to result in an audible POP. Many users here have described other artifacts like warbling or phasing if different snapshots have different time settings on certain FX between snapshots. If the POP is being caused by this situation there is really little you can do about it; Helix and Variax are accurately modeling pretty much the same sound that would happen in the analog world if it were possible to make such dramatic instantaneous changes. One thing you could do to test this is to set up two different presets rather than using snapshots. Have each preset match exactly the two snapshots. Then experiment with changing between the presets. My guess is that the POP will disappear, but of course you will hear a gap in the audio as the presets are switched in and out of the Helix working memory. The POP is what you hear when the switch is instantaneous due to the memory not being swapped.

I’m not a Line 6 rep. My Firehawk FX device has never had Bluetooth connection issues, but my use of it is admittedly simple.

Here’s what the manual says: “Existing MIDI, bypass, snapshot, and controller assignments are not saved with the User Model Defaults.” That implies everything else is saved, including cab/mic choices with Amp+Cab models. Manuals are wonderful things! Packed full of useful information.

Check the Global Settings for the Mic Input Gain setting. I find the default setting to be very low, and it is reset to default during a firmware update.

You’re welcome. Enjoy your Helix!

This is the most interesting part to me. The moral of the story seems to be that if you are buying anything used, from anyone anywhere, you are putting yourself at risk of being in possession of stolen property, leading to the above scenario. Caveat Emptor.

Good idea! Waste no more time on this. I do think it’s a good feature. The original owner will know that their stolen gear has turned up somewhere. How useful that info is depends on whether and how the original owner tries to pursue it - through Line 6, law enforcement, or their household insurance company. After all, the insurance company is the only one with a financial motivation to pursue assuming the original owner has made a claim and received some payment.

Follow the installation instructions: Begin by downloading and installing the HX Edit installation package. If you are using Line 6 Updater directly you are not following the instructions. If update issues persist please come back here with further details.

Personally I would rather this sort of thing be resolved through home insurance than using scarce and expensive law enforcement resources. I’d bet (and hope) that following up on a situation like this would be wa-a-a-y down the list of law enforcement priorities.

The earlier bug was restricted to moving between Bank 32 and Bank 1 and it has been fixed. If you are experiencing this during movement from random banks it is a new issue, and afaik only applies to you. Sounds like hardware. Open a support ticket.

I wonder what Line 6 does now when a new owner cannot register their equipment because the serial number is already registered? We get lots of questions about that here, and we usually reassure the new owner that Line 6 will help them with registration. Does Line 6 support simply reassign the serial number to the new owner, no questions asked, or do they perform some verification check with the previous owner to see if it was stolen? I don’t know but it might provide some insight into their follow up intentions with the ‘stolen gear’ feature.

It’s a good feature, but the devil is in the details. What will be done with this information? Yes, inform the owner from whom the device was stolen, but then what? What good is that info to that owner? Will Line 6 identify and/or pursue the new registrant/owner if a CS or support call comes in? Will they attempt to engage local law enforcement? The new owner is likely unaware that they are in possession of stolen equipment. Are they somehow culpable for innocently buying something online or at a local used equipment shop? Line 6 will likely do none of the above for legal reasons. In the end, all the original owner knows is that their stolen gear has resurfaced somewhere. They aren’t likely to get it back. Are they any better off knowing this?

Have you tried using Snapshots? That allows you to simultaneously turn on/off multiple FX blocks within a preset, and adjust their parameters, with a single press of a footswitch, and with no audio gap.

No, that’s not possible.

See the Controller Assign section of the manual for details on how to switch the Vol pedal control from EXP2 to EXP1.

Yes, you could do what you describe. This would essentially be duplicating what you can already do in Preset mode, albeit referencing only 8 presets simultaneously instead of 10. What you would lose, though, is the ability to use the footswitches for their primary purpose, namely turning individual FX models on and off within a preset. So you would end up with two ways to do one thing (select different presets) and no way to do what, to me, is a very important thing, namely turn FX on/off with a footswitch. Seems to me you have a solution looking for a problem. I think the current design of Preset/Stomp modes is a better approach.

Helix Native uses ‘compatibility modes’ for preset transfers. If you set Helix Native to the HX FX compatibity mode then it will restrict your preset structures and models so that they are compatible with the HX FX device. Otherwise the presets will not be compatible, leading to the behaviour you describe.

No, the new owner will not get the discount. It applies once per Helix device.

As voxman55 said, there’s a global setting that controls the behaviour of the volume pedal setting when you recall presets. Check the manual for details.

Yep - a bit of work to do. This is almost always the case when switching modeler platforms. Presets from different product families are rarely compatible. My advice would be to start with the amp model in your HD500X that you think most closely matches the FH FX preset amp model. Ignore your FH FX detailed amp settings and experiment with the HD amp settings until you get what you like. Then proceed with the first FX block in the FH FX preset signal chain. Choose the closest HD FX block, ignore the FH FX settings and experiment with your own HD FX settings. Rinse and repeat for all remaining FX blocks in the preset. Rinse and repeat for all FH FX presets you wish to recreate.

That's true unless you want to connect your Helix to a computer. If so you need the Line 6 drivers. And HX Edit is also additional software if you want to use it - it's not necessary. As for your current driver issue, there are 2 Line 6 drivers involved. One is for DAW support (that's the one you mention). The other is for general usb audio support. Find it and download/install it. if you are still experiencing issues open a support ticket. btw... installing HX Edit first, per the installation procedures, installs both drivers.

Are you sure you are using the Line 6 driver, not a generic Microsoft driver? Did you follow the firmware update procedures as published in the firmware release notes? If not, I would expect two things to happen: 1) The firmware update will not work, and 2) You will have driver issues.