HonestOpinion

Great to know. I still love a good Marshall model!

Let us know how you got it back online when you get the issue resolved. Good luck!

If you are just speaking generically as in auto-wah, envelope filter, T-Wah etc. look under the 'Filter' effects category. There are several including a few in the Legacy category that don't appear under Mono or Stereo. Here's a handy resource for looking up effect(also amp/cab) models: https://helixhelp.com/models

This^^^. Is it possible you are using the Import command off the yellow task bar towards the very top of the librarian section of HX Edit titled "SETLISTS" ? To import presets you want to use the Import command from the section below it in white labeled "PRESETS". As always make sure your HX Edit version is the one that corresponds to your firmware version.

Could easily be a hardware issue with the button needing cleaning or just failing. The Home and "Page --> " buttons on my Helix have both started to periodically require two clicks although my Page button started to fail a year earlier. Their performance has degraded over time. Opening up the chassis and cleaning the contacts might help. For now I am just tolerating it.

Yep, I have a Spark and it is a great little practice amp. Just could not deal with the Amplifi's lousy Bluetooth connectivity. Would have preferred just to see the Amplifi continue to be developed and supported though. Postive Grid appears to essentially have just copied the Amplifi concept and improved on it although the multiple speakers in the Amplifi and the software were a great foundation for Line6 to build from. I guess they weren't selling enough to make it worth it.

Probably not the issue but make sure your power cable is firmly seated on both the device and outlet ends. Also ensure nothing else is plugged into the device while doing the global reset including the USB as datacommando recommended. If you can get past the "Updating UI MCU..." screen it might require rebooting the PC yet again and try swapping out the USB cable for another one(or two) and moving it around to other USB ports. Worth trying another PC if you have one available as well. Also, keep trying the global reset FS6 & FS12 as data recommended as well as some of the other reset options available at https://helixhelp.com/tips-and-guides/universal/reset-options. I know other users on the forum have had success through sheer perseverance by rolling through the various reset options. Ultimately you may have to open up a ticket with Line6.

Agree that the manual and the settings need to be corrected/reconciled. The workaround, even if some find it less than ideal, to this issue is similar, as you point out, to the approach to tunings I detailed above. Just force all the settings on the Variax by setting them explicitly on the Helix. At least you know what you are going to get when you switch to a preset or snapshot that way. I suspect Line6's approach to HX operation of the Variax is similar to the one they took with the Powercab+ and this informs the lack of urgency for making changes to the way they are controlled remotely. For example, in the case of the PC+ you cannot select the presets on the PC+ from the Helix even though this capability has been repeatedly requested. You must remote control every parameter individually from the Helix. Once you decide to control the Variax or PC+ from the Helix/LT Line6 seems to shall we say "encourage" you to control all parameters on these peripherals from your HX device. I appreciate their approach and I can see how it ultimately cuts down on confusion that might otherwise be caused by passing control back and forth from the Helix to the Variax/PC+. It does however require more effort and intention on the part of the user when designing Helix/LT presets for the Variax and PC+. The allowable interaction and operation between devices could be documented better and with more detail.

Did it just freeze on this screen, was this the only message you got? Maybe you mistyped but there is no "HX Edit 3.11" yet as of this moment for the LT. The latest HX Edit version is 3.10. It is the latest firmware that is at 3.11. You may want to try a manual update using the Line6 Updater if you can't get things working with the HX Edit automated update.. Uninstall everything. Download HX Edit 3.10 and install it with all checkboxes checked. If you can upgrade the firmware to 3.11 successfully at this point great. If not, proceed to #3. Download/install the Line6 Updater along with the 3.11 "Flash Memory" firmware file. Run global reset - https://helixhelp.com/tips-and-guides/universal/reset-options Manually run the firmware update - Run the Line6 Updater, point it at the 3.11 firmware file you downloaded. Use backup to restore global settings and setlists

I find the best way to address this is first to make sure that on the second page of parameters on the Input block you have 'Variax Settings' = "Per Preset". Then set 'Preset Variax Tuning' = "Custom" for every Variax preset. Make sure on the third page of parameters every preset/snapshot has your preferred tuning set. Even if you are using standard tuning. More of a PITA but it gives you explicit control over the tunings in all your Variax presets/snapshots via the Helix with much more predictable results. You also have the added benefit of assigning and changing tunings per snapshot in addition to per preset this way if you wish.

If you have not already, try uninstalling first and download and install the latest version of HX Edit(3.10) with all checkboxes checked. Sounds like you just tried the various drivers.

One thing to be aware of is if you have the global settings 'Footswitches' --> 'Stomp Select' = "Touch" and you touch a footwitch that is assigned to a CC value that will bring up the Command Center screen as you observed. Stomping on it with a shoe on(or wearing gloves :-) for example does not do that so unless you are playing barefoot it should not impact your live performance. If you find this inconvenient during editing you can always set 'Footswitches' --> 'Stomp Select' = "Off"; at least while you are editing your presets but that brings with it the downside of not being able to use the touch capacitance to switch the focus to a footswitch assigned block.

There is a 3.11 version of the firmware out now so that is what I tested on. Same question as rd2rk as to what "2 no. footswitches" is referring to? Can also confirm though that using global settings 'Footswitches' --> 'Up/Down' Switches' = "Snapshots" is working normally, can't replicate your bug. Update: Just noticed you set up two additional switches for snapshots in Command Center. I will try that next.

This is just great! We are already seeing the benefits of the improved upgrade process with what essentially amounts to a quickfix in very short order addressing some issues in 3.10. The fact that the new upgrade process causes far fewer users issues allows these kinds of quick responses to bugs or even to just push out new features more rapidly while minimizing the number of users who have problems with the upgrade. To me this is perhaps the greatest benefit of a smoother upgrade process and it is manifestly demonstrated with the release of 3.11 so shortly after 3.10. Just remember to follow the upgrade instructions and run the factory reset and restore afterwards! Thanks Line6! Cheers! If you go check 'File' --> 'About HX Edit' in HX Edit after your update is completed you should see HX Edit 3.10 and the firmware at 3.11.

Wow! That is one very impressive homemade electronics project!

There is a $10 difference right now, at least on Sweetwater, but your same logic still applies and that seems a small extra price to pay for the flexibility and future-proofing.

I could see it being handy to have an additional option to the 'Extract Files From Backup' command that could extract individually all the current presets located on your HX device rather than those located in a backup file on disk. It could use the current process(all your presets as individual files, sorted into directories named after their respective setlists) but also allow a destination directory for the extraction to be selected. The current process uses your selected backup file's directory as the root directory for the extraction so it doesn't require you to select a destination. Granted you can use this command as it is now to extract the current presets loaded on your device by creating a current/new backup first and then extracting from it. It just requires an extra step to use it with the setlists on your device so no tragedy if this proposed option never gets added. Using this two-step method does have the additional advantage of providing you with a current backup. Never a bad thing. Still, having the option to point at a backup or your currently loaded setlists would be convenient but as suggested above easily enough worked around and that functionality does already exist as well in HX Edit's librarian section. Just more kludgy using the old method. Ideascale(or not :-) ).

Stated with great humility. No true village idiot would have said that. Good luck on your quest!

Found a couple of bugs with the 'File' --> 'Extract Files From Backup' function in HX Edit. Was hoping some other users could confirm them and if so I will create a ticket. Hardware: Helix Floor Firmware/Editor: Firmware 3.10; HX Edit 3.10 OS: Windows 10 Bugs: 'Extract Files From Backup' I noticed two bugs in the 'File' --> 'Extract Files From Backup' function in HX Edit. At least on my Helix. Not sure if these bugs will show up on every HX device or even on every Helix as my setlists are almost six years old now and are full of presets that have been through almost every firmware upgrade. Anyway here are the bugs: One bug is that it does not seem to be working consistently if you just try to extract one setlist. When you do that you may just get an empty directory with a file named info.txt. Or, you may get a proper extraction but depending on which setlist you selected you may also get additional setlist extractions that you did not select. The extract seems to work properly however if you leave all the setlists selected for extract. The second bug is quite minor. For some reason some of the empty presets named (by default) 'New Preset' don't seem to follow the naming convention properly and just end up with the preset number. I suspect this could be related to if those new presets slots were previously used and then had a blank "New Preset" copied back to them, or perhaps the name of the preset before them breaks the naming convention. Just speculating though. Again, not a showstopper but a bug nonetheless.

There is a kind of cool feature in the 'File' menu in HX Edit named 'Extract Files From Backup'. This command will allow you to go back to a previous backup and extract the individual presets from any of your setlists. That means if you just need a specific preset(s) from an old backup/setlist but never extracted the presets individually you can still go back and get to it easily. Ever wanted to go back to a previous firmware's backup and see all the Factory presets? Now you can. You can also use it to make additional backups of all your presets individually before every firmware upgrade. Something I always do out of an abundance of caution. This allows you to rescue a setlist that isn't loading from your previous backup by using it to extract all your presets from a setlist in that backup and load them individually until you figure out what is breaking when you try to load that setlist. If you just leave all your setlists checked the 'Extract Files From Backup' command will create multiple separate directories(on your hard drive, not on your device) under your backup directory. Each directory named for each setlist with all of your presets extracted there individually. It also extracts your IRs and Favorites if you leave those checkboxes selected. Btw, it is noninvasive in that it does not overwrite any presets/IRs you have loaded on your HX device(at least not so far in my testing) so feel free to experiment with it. It even prompts you when the process completes with the link to open the directory where your presets have been extracted. Nice! I did notice at least two bugs in this utility but they are not showstoppers. Don't know whether everyone will observe the same bugs that I did as my setlists are now almost six years old and have been through every firmware upgrade. Maybe this utility is more bug-free on setlists full of presets created only with newer firmware versions? One bug is that it does not seem to be working consistently if you just try to extract only one setlist. When you do that you may just get an empty directory with a file named "info.txt". Or, you may get a proper extraction but depending on which setlist you selected you may get additional setlist extractions that you did not select. The workaround is to just leave all the checkboxes checked and extract all the setlists. This seems to work properly. The second bug is quite minor. For some reason some of the empty presets named (by default) 'New Preset' don't seem to follow the naming convention properly and just end up as files named with only the preset number. I suspect this could be related to if the slots for those blank presets were previously populated and then had a blank "New Preset" copied back to them, but I am not sure. Again, not a showstopper but a consistency bug nonetheless. I will list the bugs over in the bugs topic so hopefully others can confirm them but overall this is a very handy capability in HX Edit that I had not used previously, nor did I find it documented in the 'HX Edit Pilot's Guide' or any firmware's release notes. If it proves reliable(Update: currently it is not, see bug two posts down) and I am assuming it will 'Extract Files From Backup' provides a much easier method of backing all your presets up individually into their own directories. That is something I have always done before a firmware upgrade by creating a directory for each of my setlists(I eventually set up a blank directory template on my hard drive for this) and then going through each setlist individually, highlighting all my presets at once and clicking 'Export'. A real PITA. This however turns backing up all your presets as individual files, sorted into directories named after their respective setlists, into a hassle-free single click affair. It also executes and completes shockingly fast. I like it, a lot!

Do NOT cut the red wire, 60, 59, 58, ... :-)

Just to be sure, have you tried downloading, installing, and then running the latest version of the Line6 Updater manually while the screen shows the boot failure message? If you have and it is not working can you describe what is happening. Also, have you tried swapping USB ports, USB cable, and even trying the update on another computer if you have one available? Btw, if you have an SD card inserted in your computer make sure to eject it, reboot and run through the recommended steps. If none of this works I would open a ticket with Line6.

As cruisinon2 already mentioned the Fletcher-Munson curve is a harsh mistress and will always pose a dilemma for guitarists - "How do I get my presets to sound the same at performance levels as they do when I designed them at home?" The answer is you can't unless you have unbelievably tolerant neighbors and a masochistic urge to damage your hearing. So my method has been to try to get the volume up as much as I can without posing a danger to my hearing while I am designing presets intended for stage. Rehearsal has always provided my best opportunity to edit them at the higher volumes more closely resembling performance levels. Unless your band has unlimited patience you might find this difficult at first. Several things will happen though as you get more adept at programming your HX FX. You will be able to dial in the sounds you want more quickly so your drummer will look upon you more kindly, and you will learn to anticipate to a certain extent what will sound better at higher volumes so your presets will require less tweaking to get gig ready. You should also be able to use some of the presets that have proven to work at stage volumes as templates or guides for others. This is a huge timesaver. The variety of those will increase with time. Now the other dilemma. For many guitarists a traditional guitar amp just has a "feel" and limited frequency response and range that they prefer. However, that is not what your audience is going to hear whether you go direct to the PA or mic your amp. As stated already a FRFR floor monitor or IEMs will definitely give you a more accurate idea of what your audience is hearing through the PA. This makes for a more accurate translation from your practice/rehearsal created presets to the PA. If you don't like the sound of an FRFR/IEM as a stage monitor, and there are a fair number of users who don't and prefer using an amp, then there is no getting around the fact that there will be more of a tonal divergence between what the audience is hearing and what you are hearing from the stage. That makes preset design for the PA more of a challenge as you create your presets with a rig that sounds nothing like the PA. And to pile on you need to find a sound that sounds great on both your amp and the PA. You will need to account for that disconnect as best you can when designing presets. Easier to do with some presets and equipment than others. Whatever approach you decide on is fine but there are always compromises to be considered. Just to throw a third monkey wrench into things, once that guitar tone that sounded fantastic in your practice space finds itself in a mix with other instruments it may not work near as well. Could be harsh or not cutting through for example. Yet another good reason to test and modify your tones in rehearsal. If you have to, make some mental or written notes on how your presets might need to be adjusted as you may not have time to get to them during rehearsal. Refine those presets at home on your own time and try them out at the next rehearsal. There is some really great advice given in this topic that should be helpful but fundamentally there is no perfect solution that I have found yet that lends itself seamlessly to presets that work every time when transitioned from practice/rehearsal to stage. Sometimes it is only during the show that you find out that a preset you thought was ready for prime time could use a little more work. Damn you physics! Back to the drawing board. To get them right every time you would literally have to create your presets at the gig and that ain't gonna happen unless you can put chickenwire or plexiglass between you and the audience because the beer bottles will be flying. All I can say is it gets easier and faster as you spend time with the equipment. You also end up with a few go to presets that work well under most circumstances. At the risk, no, certainty, of being redundant, the more similar your monitoring equipment is to the PA, e.g. an FRFR, the more likely it is that your preset will translate more directly to the PA. But if you prefer an amp, you can make that work too probably requiring a bit more effort or adjustment. Nothing but time and money is stopping you from endlessly experimenting and vacillating between various approaches like a good number of the musicians on this forum until you find your preferred method and at last...(Nope! You then proceed to continue experimenting and vacillating, but with better results).

Heh, don't feel bad, I know for a fact you are not the only one who skimmed over that release note. When I first saw the new text in my scribble strip and was busy appreciating how useful I thought it was this is what ran through my head, "Has that been there for a while or is that new? Don't think I remember seeing that there before, but maybe it was. Am I really that unobservant? Nah, that is definitely new.". :-)

Agree with your concern but using "Force" as you state is how I would address it. I want all my Variax parameters to be set from the preset/snapshot if I am using the Helix.