HonestOpinion

The impedance setting is now on the input block of each preset/snapshot rather than in global settings.

There are a couple of solutions discussed in this link, don't know whether they work or not. http://www.thegearpage.net/board/index.php?threads/i-have-an-ir-embedded-in-an-axe-fx-preset-that-i-love-can-any-of-you-turn-it-into-a-wav-or-cab.1608715/

See the post above, it may help solve the issue. http://line6.com/support/topic/16083-helix-bug-reports/page-12?do=findComment&comment=163277

Assuming you have done the global reset already after doing the firmware upgrade (make sure you have your presets backed up), try switching to a factory preset before you plug in the USB connection for the Helix. Make any minor change to the preset that was in use when you were getting the "Helix has stopped working" error and save the change. Now connect the USB and bring up the editor and see if having that preset up when connecting still causes a crash. Good luck!

I keep a set of backups in separate sub-directories with names that correspond to each firmware/editor version in case I ever have to roll back. Backups are tiny and it costs you nothing to keep them. I agree upgrading a day or two before a gig may not be ideal in the event that you have issues during the upgrade or need time to adjust to the new firmware. However, for those who don't use snapshots the Helix will work pretty much identically to the way you have been using it with the exception of having the guitar impedance setting available on a per preset rather than a global setting. The snapshot functionality is fairly transparent to those who don't use it. You will see a few new global settings and some new options on certain screens with the parameter buttons but the workflow you have gotten used to remains pretty much the same. The advantage to upgrading is you get all the new bug fixes, the improved tuner, snapshots, new amps and effects, etc..

I would think one of the reset options would prevent having to revert to a prior version of the firmware, have you tried any of these? http://helixhelp.com/pmwiki.php?n=Main.ResetOptions

Btw, if you are running a firewall or anti-virus software it might be interesting to see if you are still getting the same "http..." error with them turned off momentarily.

Have to agree, that new modded Marshall model kicks arse!

DI and other members of the forum have been incredibly gracious in these debates regarding which is better, the Helix or the AX8. There are clearly legitimate arguments to be made supporting either unit and I hope these two companies continue to compete and learn from each other to the benefit of every guitarist who supports them. But... I have to say, with the addition of snapshots to the Helix, and as the model and effect library steadily if slowly grows, in my mind, given all of the additional features that the Helix came out of the gate with, the Helix is quite simply the greatest modeler on the market now for the gigging musician. The list of features and flexibility is just mega-impressive - scribble strips, LED rings, incredible array of I/O options, best user interface ever developed for an MFX, cap-sensitive footswitches, mic input and multiple output paths via USB or standard I/O, headphone jack, large colored main screen, snapshots, and the list just goes on. I know there are still things to work on but let me say what the Line6 staff has been too polite, respectful, and legitimately admiring of the competition to state, the Helix is quickly rising to the top of the MFX heap. In fact, I think it is already there! In my mind the Helix is the clear pioneer, and modeler to emulate. I don't think there needs to be a winner per se, and I respect everybody's choice as to what works best for them, however, every day I use the Helix not only makes playing guitar rewarding and inspiring but also reinforces my conviction that this is currently the best modeler you can purchase. The Helix is in my opinion the best thing since sex and peanut butter (not necessarily combined)!

I know it does not fix the updater for you but alternatively you can download the 2.0 firmware file directly from the Line6 downloads page and then point the Updater to the file on your local file system on your PC instead of having it got out to the net to retrieve it.

Glad to see things are working again!

Thanks! I looked for it first in the documentation but managed to miss it somehow. Once again, great job Line6.

It may be a good idea to download the latest 2.0 firmware file to your PC before you get the new Editor installer. After you run the new editor installer which will install the latest version of the Editor and all the latest files, use the firmware file you have downloaded locally with the Updater instead of the one that is up on the Line6 website. This may help ensure an uninterrupted firmware upgrade.

Feature request - can we please get the capability to rename snapshots in the editor. As always it is easier to use the editor for renaming than spinning letters on the joystick roulette wheel. Thanks!

Firmware: Helix 2.0 OS: Windows 10 Editor: 2.0 Bug Description: Controller Assign screen is not working properly in Editor. Custom naming is not retained properly after a save from the Controller Assign screen in the editor and selecting a custom LED color has no effect. Saving while in this screen will actually cause the custom name and LED color to be lost next time you bring up the preset. Steps to reproduce bug: Select a preset in the editor where you have already assigned (using the Helix) a footswitch to a parameter with a custom label and LED ring color. Now highlight the customized block and select the "Controller Assign" screen and select the parameter you customized. It will show the custom label you assigned on the Helix but will show the LED ring color as "Off". Additionally the LED ring color selection has no effect at all on the Helix from the editor, You cannot change the LED color from the editor. Save your preset from the editor without leaving the current "Controller Assign" screen and your customized parameter. Switch to another preset and come back to the one you were editing. The custom name you assigned to the block is gone and has reverted back to the default. Your custom LED color is also gone and has reverted back to the default. If some other users can confirm this behavior or let me know if it is pilot error it would be much appreciated. Thanks!

Great comment, dialing back the channel volumes on my amp blocks to closer to 5 than 10 seems to have made my presets way easier to manage. Small changes on the volume pedal no longer result in deafening changes in the PA. I hope this has not negatively impacted unity gain, it seems to have helped. It made the presets easier to control and I think they even sound better now.

Phil_m, I am not sure tagmusenmagnus1 has exactly described the issue. Adding a block should add it to all snapshots. I do think there is either something buggy in the way bypass states are interacting with the snapshot discard/retain modes or perhaps I either don't exactly understand the rules governing them yet. Perhaps they have not been fully documented because I could not suss them out a first glance checking the documentation after running some experiments in setting bypass states in the Snapshots. It is not yet clear to me how changing the bypass state in one Snapshot is supposed to interact with the bypass states in the other snapshots, and how this behavior differs between the "Retain" and "Discard" settings. Changing the bypass state of a block in one Snapshot seems to be changing the bypass state in the other Snapshots, not always the preferred behavior. In other words, changing the bypass state for a block changes it for the same block in the other snapshots as well. I thought retain/discard would either allow or disallow that behavior but I may just not understand how it works fully yet. Perhaps we need an additional parameter for bypass state behavior as retain/allow seems to have been targeted at block parameters and previous save state rather than bypass states. I am confused right now. Will play with it a bit more later when I have more time. If anyone has figured out the rules to setting bypass states from snapshot to snapshot please enlighten us. I may just be missing something simple.

Try holding buttons 6 & 12 and powering up to go into "Safe Boot" mode and then reflashing the firmware. You may also want to download the new 2.0 firmware file to your PC and access it locally when you hopefully can run the Updater again. Good luck!

BigRalphN, like you, I used to put my volume pedal at the beginning of the chain on my old analog pedal boards but only due to physics and space limitations. It was generally the easiest spot on the board to set it up. Sometimes I would place it at the beginning of the chain but wire it further down the line. Always a pain and confusing if there was a problem with a pedal or cable during a gig. Also, turning up or down the volume pedal in this setup would always impact the tone and operation of every effect down the line. With MFX I set up the volume block right before any blocks that add a delayed signal such as chorus, delay, and reverb. It is easy to forget that mod effects such as the chorus use a delay so they should be after the volume block. That way, not only does the volume pedal not impact the, for instance, amount of grit and tone of the distortion (by being placed after it), but the volume operation also does not impact the volume of the delayed signal of my mod/delay/reverb effects (volume block placed before these). Whatever the volume of the last note I played before adjusting the volume pedal is, determines the volume of the delayed signal on those blocks(as further determined by where you set the "Mix" parameter of the block that contains a delay). That way you do not unnaturally cut off the last bit of delayed signal from your chorus, delay, or reverb.

Woot! You guys seem to have thought of everything. This update is a magnificent piece of work! :)

From what I can see so far the implementation of Snapshots in the new 2.0 firmware is just inspired and brilliant. Line6 has taken an incredibly complex feature and made it unbelievably easy to use, at least on the Helix. I have not played with it in the Editor yet. In addition, the new global settings for determining how the footswitches display snapshots, presets, and pedals are just perfect. Line6 continues in the tradition of other Helix features in developing the friendliest user interface imaginable. I am grinning ear to ear, they not only delivered scenes but delivered them in a manner that is accessible to even the most tech-averse guitarist.

Unequivocally, YES! Buy the Helix! This is the greatest MFX device ever created IMHO. Nothing that comes before compares.

Fan-freaking-tastic update! I cannot believe my eyes and feet. The Helix has scenes (snapshots)! The already spectacular Helix just took a quantum leap forward. For all of us who have had faith in the Line6 team to improve this beautiful beast with time, our patience (and sometimes lack thereof) has been richly rewarded. Fantastic job guys! I cannot express how much I appreciate what Line6 has delivered in the Helix! Again, great job and thank you for listening to your users or just pursuing your own plan, probably a bit of both. You have delivered some phenomenal new features here. Thank you so much for this update, it is beyond impressive! This device is already my favorite thing to play guitar with by a long-shot and it just got a whole lot better!

Thanks, and awesome!

Very interesting! What happened to the "Impedance" setting in the global settings in version 2.0 of the firmware? It does not appear to be there any more.