HonestOpinion

Although either type of channel can be used I connect my Helix to the microphone channels with XLR cables although 1/4" can work if the run is not too long. Too long and you are likely to get unwanted interference. If you do connect via XLR to the mic channels set the LT's global settings 'Ins/Outs' --> 'XLR Outputs' = "Mic" and remember to turn the phantom power for those channels OFF.

I also ended up using an RJM Gizmo to switch my Mark V because of ground noise through my old modeler. I eventually moved back to using the Boogie exclusively with an analog pedalboard and frankly rarely to never use it these days. I would be curious if anyone has gotten it working successfully with the CV out on the Helix and which Mark V footswitch functions they got working.

Nice troubleshooting, in hindsight uninstalling should have been the first thing suggested but it did not occur to me that this was a second go-round. No need to delete, this probably will help someone sooner or later.

Hmm, so this seems to be either a problem with the Mac download link or it could just be the installer documentation for the Mac version was not updated properly. There doesn't appear to be any version discrepancies in the Windows download. If you installed Native already you could go to your DAW, bring up the Native plugin and check in the 'About' section under the small question mark in the lower left hand corner of the Native plugin to see what version is actually installed. If you haven't installed it completely I can see where you wouldn't want to risk ending up with the wrong version and having to contact Line6 to get the whole trial thing straightened out. I have no idea if trial versions allow you to install an update after the initial trial is installed. Unfortunately I don't know/remember how the whole trial thing works and I don't own a Mac to test this on. If this is actually exactly the same file as the licensed version but just requires a trial signin then my only suggestion would be to go directly to the location of the licensed Native version - https://line6.com/software/index.html. Select "Helix Native" from the 'All Software' pulldown and your OS from the 'All OS' pulldown and download and try to install that 3.10 version. At worst it will not offer a trial signin and not allow itself to be used and you can just uninstall it and open up a support ticket with Line6 or wait for someone to chime in here who can shed more light on the issue.

Are you on Windows or Mac? I downloaded the trial Windows version to test it(I already own Native), available by pressing the "Free Trial" button at the bottom of the page at https://line6.com/helix/helixnative.html. When I run the install I do not get the screen you see. Is it possible you scrolled too far down in the Downloads section it takes you too and grabbed the wrong file from another version? You want to go to the first download button you see while scrolling down from the top of the page. It will be at the bottom of the verrrry long 3.10 Helix Native section; not the bottom of the page. Easy to miss. Just for good measure you may want to go back and download the file again. At least for Windows the file you download will be named "HelixNativev3.10Installer.exe".

I did that until my thumb started turning red.

In addition to providing more details on the question rd2rk asked, " What exactly do you mean by "snapshot stops working"?", could you please let us know which HX device you own and what the editor and firmware versions are as well as what OS you are on. This could easily be a problem with you not having those properly matched but it is impossible to know without more detail. In HX Edit you can go to 'Help' --> 'About HX Edit' and check both the editor and firmware version.

Any chance you are setting a volume block with the built-in expression pedal on the Helix and getting a different volume on the HX Stomp(no expression pedal)?

One suggestion, don't assign EXP1 for volume, instead use EXP2. By default Helix assigns the Volume block to EXP2 and a Wah block to EXP1. You may think they should have done this the other way around, you won't be the first, but it is not worth the energy of constantly reassigning them or the resultant confusion that often ensues when you start making more complex assignments or add another expression pedal. Just start with the defaults(EXP2=Volume, EXP1=Wah) as your baseline. If you want to control some other block's parameter(s) instead of the Wah, use EXP1 or EXP3 if you have an external expression pedal connected. If the defaults drive you nuts you can design a template to use with the assignments you prefer but IMHO it isn't worth fighting the Helix's default behavior. Note: If Line6 ever adds an option to allow controller and switch assignments to be stored along with Favorites or User Defaults I suppose one of the benefits would be making it much easier to use expression pedal and toeswitch assignments that don't use the current Helix defaults.

Just curious, why are you splitting your guitar's output via a splitter cable to the HX Stomp? What happens when you use a standard mono guitar cable without the splitter? It could be this or something else related to how you are connected as DunedinDragon alluded to. I would start by removing one thing at a time while HX Edit is connected to troubleshoot until the "improved" sound goes away. Also, unlikely but you can try eliminating electrical power as a possibility. Try splitting your devices across a different circuit than the Stomp if possible.

I would highly recommend you take backups and download, install, and upgrade to HX Edit 3.10. Then follow the update alert in HX Edit to update to the 3.11 firmware from HX Edit before you do any further troubleshooting. Update your HX Edit version and the firmware, do the global/factory reset, restore of your backup, and wait for your presets to rebuild after the first restart. In other words, follow the update release instructions carefully. Now check the 'Help' --> 'About HX Edit' dialog box in HX Edit and ensure it is displaying HX Edit 3.10 and 3.11 for the firmware. Now you can begin troubleshooting again. Until you have executed these updates I think that currently you cannot rule out some sort of version mismatch. It is generally a waste of time to troubleshoot an old version of the software/firmware without a compelling reason to have stayed on it.

I actually agree with cruisinon2's post. Although the "optimal" or the recommended setup may at times appear to be contradictory to what is ideal for you it is really about finding the compromise that works best for your equipment/setup and how you tend to use it. The guidance Line6 provides on setting the volume level tends to be most beneficial to users who had their master volumes cranked down to for example 1/4(9 o'clock) and can't figure out why the sound isn't what they were looking for. Once you get past say about 12 o'clock the impact to the tone diminishes and can be much less noticeable, perhaps not at all depending. Although Line6 may state that the optimal sound is at unity with the master volume knob set at max, I also leave some play to adjust my monitor, usually around 3/4 of the way up for exactly the reason cruisinon2 described - I don't want to have to reach behind my monitor on stage to adjust it. Others who want to have an even wider range available for adjusting their monitor may leave the volume at around 12'oclock without noticing any significant impact to their sound. To some extent this may depend on how their presets were designed. My primary concern on stage is to make sure the FOH has predictable and optimal levels at the board so I send that signal out at max. Although I also want the best sound I can get out of my monitor(s) on stage, having some added measure of control over the volume and easy access from my Helix is also important to me so that is where I compromise by using the volume control. Same thing might apply to a bedroom or studio player. If it is more convenient to use the volume control don't hesitate to find a sweet spot on the master volume that allows you to adjust it without butchering your sound, e.g. keep it as high as you can while still providing adequate adjustability of your volume.

It's already in there. This is exactly what snapshots does and a whole lot more. You can also use one row of footswitches for snapshots and another for stomp assignments for very powerful control combinations. If that doesn't get you there you can use the Command Center to assign your footswitches in custom configurations. Read up on snapshots and the Command Center in the manual or watch any of the multitude of videos. The place to submit new ideas for features or improvements is here https://line6.ideascale.com/ . That is how you get them in front of Line6 staff and with or without enough votes they may just get implemented.

What version of HX Edit and the firmware are you on? The first thing you might try is getting a backup and then doing a global reset. - https://helixhelp.com/tips-and-guides/universal/reset-options. Try doing a restore from backup after that if it is still having issues. If that does not work I would do the following: Uninstall and reinstall HX Edit 3.10 It should prompt you to upgrade the firmware if you are not at version 3.11 of the firmware. Go ahead and upgrade. Follow the firmware update release note instructions. Do a global reset, and then restore from backup. If for some reason you can't run the firmware update from HX Edit then exit it and use the Line6 Updater instead. Again, do the global reset, and then restore from backup. Hopefully this should get you up and running without the lockups. Paying $700 for a Helix is an absolute steal, leaves you with zero chance of ever having buyer's remorse, and it should be very much worth your while to put some time into stabilizing your device. As rd2rk said you should be under warranty if all else fails anyway.

I have an old 1x12 cab with a Celestion Gold that sounds great! Essentially the Celestion Gold was an alnico speaker designed to replicate the sound of the Celestion Alnico Blue speakers but with a higher wattage rating so it could be used with more powerful heads/amps without blowing. The Alnico Blue was only rated for 15 watts so very easy to turn one into toast. That is part of the beauty of cab modeling, you can mix a 100watt or more amp with a model of a delicate and expensive speaker with no worries. The Alnico Blue was made most famous by the Vox combo amps and cabs so any of the cab models that work well with a Vox should have some similarities such as the 2x12 Silver Bell or 2x12 Blue Bell. There are 1x12 versions there as well but I don't know if there are any 10" models or 4x12 models. Some of the other cab models intended for Fender amps will probably also work well as they tend to have a bit of that "chime" and "bell-like" tone that the Alnico Blue(and Gold) is so famous for. Maybe give the 1x10 Princess or "4x10 Tweed P10R " a try or even the 4x12 WhoWatt100. I would just roll through the models until you find something that is close to capturing the sound you are looking for and then start adjusting its parameters, particularly mic type and distance. Another approach is just to get IRs made with exactly the speakers/mics you prefer in your favorite cab configurations.

Well the 'Extract Files From Backup' command would at least be useful for this as you can open up the preset files it creates with any editor and at least see each block's settings. Just can't import them yet.

Personally I would probably use the backup that HX Edit made during the editor and firmware upgrade(most recent), but yes, i do the factory reset and then restore my globals and setlists after an upgrade per the release instructions. Supposedly you can get by with just restoring the globals but I tend to take Line6 at its word regarding the recommended procedure.

The latest version of Native is 3.10. Go to the Line 6 Downloads page and select "Helix Native" from the 2nd(All Software) pulldown menu and select your OS in the 3rd(All OS) pulldown menu. Do not select anything in the 1st(All Hardware) pulldown. Click 'Go' and you should see Native 3.10. https://line6.com/software/index.html The update of Native has not been integrated into the automatic upgrade process yet in HX Edit 3.10. You still need to download and install it manually.

Nice find. Too bad it costs $140 to ship to the US or I would order one of these.

Whether there needs to be a more comprehensive way to lock global settings and if so how to go about it is up for debate. Frankly in years of gigging with the Helix I never once found it to be an issue. Still, I can see why some users might find being able to totally lock down certain settings valuable, particularly in the studio. Don't know if there are enough who find this an issue though to give the idea any real momentum. One thing I agree on though with the OP and DunedinDragon is that the 'Footswitches' --> 'Stomp Select' setting should have an option added that includes turning off the touch/capacitance sensing on tap tempo and the tuner. There should be at least one option("Off" being the obvious choice) on this setting that guarantees absolutely nothing will be activated by touch although I suppose some users wouldn't mind having an additional option(s) that retained the current behavior where only the tap tempo and/or tuner remains touch sensitive.

As 'sombodyelse' mentioned there is the 'Extract Files From Backup' command under 'File' in HX Edit but the presets don't import properly after the extract. Maybe someone can help you out with fixing them for import, but barring that... If you have the individual setlist backed up it is as simple as exporting any of your current setlists, using that setlist location as a temporary placeholder, importing the setlist you want to retrieve the old presets from, and then exporting those presets. You can then import the setlist you backed up initially and restore the presets you recovered anywhere you wish. However, if you only have a full backup and not the individual setlist backup one thing you can do is use the 'File' --> 'Restore From Backup' command to restore a single setlist or all the setlists from an old backup. Restoring one setlist is a bit more complicated as you need to understand that it will overwrite whatever your current setlist is in exactly the same position(from 1 to 8). Here are the instructions for the more heavy-handed full backup and restore. You will be doing an initial full backup, restore of the backup that has the presets you want to recover, extracting the presets you want to recover, and then restoring the initial backup you made. Warning, this will be tedious as you will have to wait for all your presets to rebuild after the restore, and there is always the potential for screwing this up although it is more straightforward then it sounds. Start by creating a full backup with 'Create Backup', I would also export all my setlists individually to be on the safe side. Click the 'File' --> 'Restore From Backup' command in HX Edit, select the backup you want to recover the old presets from, and run the restore. Export the presets from the setlist(s) that should now be loaded from your old backup. Use 'File' --> 'Restore From Backup' to restore the backup you made initially. Import the presets you recovered to whatever location you wish. As I said, even if all you have is a full backup(not the old setlist) you can do this more surgically by just restoring one setlist from that backup but the instructions get more involved and more error-prone unless you are quite familiar with backups and restores. If you have that level of familiarity with backup/restore you probably know how to go about it. It is ironic to me to see this post come up within days of having submitted a Line6 support ticket to hopefully get the 'Extract Files From Backup' command fixed. It would be so much easier and more straightforward if that utility was working properly and would require none of these more sledgehammer restore procedures. I might be inclined to wait and see if they fix the Extract command in the near future before I undertook the above procedure unless you need those presets immediately. Maybe if you get lucky someone will jump on here with a script they wrote themselves to extract presets from an old backup.

That is one pro level doorstop, looks like it was made for a pedalboard. I was expecting to see one of those brown rubber jobs :-)

This is an impressive topic! Love seeing people sharing these DIY projects.

Agree with all of this. I suspect very few users have played with this command yet although I think it could be well used in the future. I plan to just wait and see if it gets fixed in the next firmware update.

LOL, War & Peace at this point. Best to stick to the most recent posts.