HonestOpinion

Done! Please vote for it here: http://line6.ideascale.com/a/dtd/Use-less-or-no-scribble-strip-spaces-to-indicate-a-snapshot/831165-23508

I have had an idea in Ideascale for a while that could really use everyone's support, most importantly the support of Line6. Now that we have snapshots I believe it would provide an incredible degree of flexibility and save a ton of time for many users unnecessarily moving around footswitch assignments. Please vote for it here. http://line6.ideascale.com/a/dtd/Swap-footswitch-assignments-from-top-row-to-bottom-vice-versa/790520-23508 The idea is to create a setting in global settings to be able to swap all of the pedal assignments from the top row to the bottom row and vice versa. As of now, pedal assignments do not follow your preference choice of whether you want pedals on your bottom row or the top. If you change this preference you would have to reassign every pedal manually. This has become doubly important now that you can assign snapshots to the bottom or top row. This means that if you had your most critical footswitch assignments on for example the bottom row, but now want your snapshots on the bottom row, you have to reassign all the footswitch assignments manually. It would also be incredibly helpful if you decide at some point in the future to switch the row (bottom or top) that you have snapshots and pedal or preset assignments set to. Additionally right now all of the Line6 factory presets are set for the pedals to show up on the bottom row and the only way to change that is reassign every pedal, one by one. That creates a big problem if you are a player who likes to use the bottom row for presets and have your pedals on the top row. The Helix has the great feature of allowing the user to decide whether they want to split pedal and presets on either the top or bottom row as well as place snapshots on the top or bottom row. It is a shame to see this functionality entail so much manual labor by not allowing the presets to conform to the users choice without hours (days) spent on manually reassigning every footswitch assignment in the factory or user presets. If there was a global setting to swap footswitch assignments from the top to the bottom rows the player would be at their leisure to decide for themselves whether they prefer pedals, presets, or snapshots on the bottom or top row. You would be able to change your preference and have all your factory and user presets which now include snapshot as well as footswitch assignments follow your preference. Please vote for it here. http://line6.ideascale.com/a/dtd/Swap-footswitch-assignments-from-top-row-to-bottom-vice-versa/790520-23508

Please add the graphical representation of the EQ curve for the Parametric EQ to the Editor and the Helix itself if possible. It is already there for the Global EQ in the Editor so the mechanism to do it is already in place. You could just extend the same existing functionality to the Parametric EQ. The visual representation of the EQ curves on the grid as it currently exists for the Global EQ is incredibly useful. Adding the graph to the Helix as well as the Editor for both the Global and Parametric EQ would be ideal. Selecting the EQ would bring up the graphic visual showing the curves for the EQ. Please vote for it here: http://line6.ideascale.com/a/dtd/Add-graphical-representation-of-Parametric-EQ-curve-to-Editor/831163-23508 Of course, being able to bring the graphic up against an RTA would be the ultimate!

UPDATED (original post did not include the number of characters difference between snapshots and preset/pedal names): Well, I have been using the snapshots for a bit now and they are fantastic, but although that snapshot icon that resembles a camera in the scribble strip icon looks really cool it is taking up way too much space on the scribble strip. The camera icon takes up 6 character spaces. This means that although presets and pedal names can have 16 characters, snapshots are limited to only 10. It would be great if we could reduce the indicator for a snapshot to one character like a block or an asterisk (or even none) and leave the rest of the characters for the snapshot's name. Or maybe just reverse the background and font or something else that would not take up any characters. I am finding I have to abbreviate, or sometimes simply don't have enough characters to descriptively name my snapshots properly. Perhaps we could have a global option that allows those who like it to keep the camera icon and gives back the rest of us the six characters that the camera eats up and provides an alternate way of visually indicating a snapshot. Once you have used your Helix for a couple of days with snapshots you know which footswitches they are, e.g. top row or bottom row, and you really start to want your scribble strip characters back for more descriptive and longer snapshot names. I hope Line6 considers getting rid of the camera icon in the scribble strip in the next firmware release, finds a better yet still obvious way to indicate a snapshot, and rededicates most if not all of those scribble strip characters to useful namespace. Please vote for this idea here: http://line6.ideascale.com/a/dtd/Use-less-or-no-scribble-strip-spaces-to-indicate-a-snapshot/831165-23508

Why don't Line6 and Fractal just get it over with already, time for a merger. I want my next MFX to be a Fractal Helix :D I guess a little healthy competition is good though too.

I suppose you could try the EQ between the amp and cab as well. Still not the ability to insert between preamp and power amp but a possible alternative.

The mix parameter that is ("exists on the Helix itself"), not the bug :D

Make sure you are pulling up the 2.0 version of the editor, if you see the camera icon in the upper left hand corner for the snapshots you probably have the right version. Did you do the global reset with footswitches 9 & 10 after upgrading (backup your presets first)? This is critical. Also, after the reset completes and you have restored your old presets, restart the Helix another time as there is a final rebuilding of the presets. Good luck!

I have not had any issues with the latest firmware upgrade but I have been through several already and have gained some experience. I agree that the download site could be improved to make firmware upgrades simpler, particularly for users new to the Helix. Additionally, the "Helix Editor" installer app download, which is the one your want to install to do the new 2.0 update, should appear at the top of the download page to make things more obvious. It is NOT currently the first file that appears in the download list, it is the second. As I posted elsewhere, assuming it does not already do this (I have not checked), Line6 should enhance the Updater so that it always checks that you have the latest files (installed by the latest "Helix Editor" app) before it allows you to access to the latest Firmware via the Updater app. Perhaps the problem some users have been having logging in with old "Helix Editor" versions is an attempt to implement this but in a manner that is bamboozling users instead of informing them to download the latest "Helix Editor". I believe better feedback to the user from the "Helix Editor" would help to avoid a lot of failed installs. Additionally, IMHO it is confusing to new users to even call this the "Helix Editor" as it is really an installer application that includes the Editor, driver (at least in Windows), and latest Updater version. In my opinion this should be called the "Helix Installation/Upgrade Suite" or something to that effect that indicates that it is more than simply an editor which I believe can be confusing to new users. Ideally if I were going to streamline and simplify the whole process I suppose the only file users would have to download would be the Updater, which when run would first check to see if there were a newer version of the updater and prompt the user if there was, ask if the user had their presets backed up or even back them up automatically, they would then have the option to download and install the latest version of the Updater, all of the precursor software (Editor, drivers, etc.) to doing the latest firmware update, and finally do the firmware update. I would only allow old versions of the Updater to have access to the version of the firmware and supporting software they were matched up to. This would prevent mismatched versions of what is currently called the "Helix Editor" software and the firmware. The files required for the firmware update are differentiated on the download site, just not very obviously, especially to those unfamiliar with the process. You are looking for the download that says "Helix" in the light grey bar at the top, "Helix Editor" in the dark grey bar, and "Helix Editor v.2.00 Release Notes" at the top of where the description starts (white background) on the right hand side of the download. You do NOT want the file labeled "Flash Memory" in the dark grey bar and "b8e2346" in the light grey bar, unless you are having internet or USB connectivity issues when using the Updater and need to have the firmware file locally on your PC before doing the upgrade. In either case whether connecting to the Line6 website via the Updater, or pointing to your local downloaded "Flash Memory" file the first order of business after backing up your presets is to download and install the file labeled "Helix Editor" with the latest firmware version notes (in this case 2.0) and let it install all the latest 2.0 files you need for your upgrade. If you do not execute this step first you are almost guaranteed to have problems. The whole upgrade process seems very straightforward to me but I have been through it many times. Perhaps more could be done to make it more obvious and easier for newer Helix users. My apologies for how long-winded this post became.

Quintuple rectifier ;)

It may essentially have been a problem akin to not having unity gain or adequate gain at the FOH due to your attenuated output block on the Helix. It sounds like your FOH may simply have not been getting an ideal level of signal. This would impact tone adversely and would not necessarily be the result of a significant change in the tone coming from the attenuated output block on the Helix. In other words, it was the interaction between your mixer/speakers and the level of the signal coming from the Helix rather than a substantial change in tone originating at the Helix. And of course there is always the Fletcher-Munson curve out there which reflects the interaction between volume and perceived sound.

Back up all your setlists, a bundle, and yes, even your individual presets before attempting any firmware update! Presets can be backed up individually all at one time by highlighting an entire Setlist and hitting "Export". This is worth doing in case one preset in a setlist you have backed up turns out to be a showstopper. This way you never have to worry about an entire setlist not being able to be restored because of one bad preset. After taking backups and before you do anything else, download and install the latest version of the "Helix Editor" installer app. This will install all the latest files you need for your firmware upgrade. Perhaps the Updater already does this, but I am beginning to think that future Updater versions should check to make sure that the latest version of the driver, editor, and Updater are on the user's PC before allowing access to the latest firmware. It seems overall like there are a few major causes of issues people tend to have when they attempt to update, the primary ones I have observed are: The PC or USB connections being used for the update either have driver conflicts or connectivity issues with the Helix. Best solution in this case is often to use a different USB port, preferably the one on the back of the PC or use a different PC for the update entirely. The PC loses connectivity while attempting to download the firmware. Best solution is to download the firmware file first and access it from your local machine through the Updater rather than having the Updater retrieve it from the net. People run the wrong version of the "Helix Editor" installer app before they try to update to the latest firmware version. Solution, Make sure you download the latest version of the "Helix Editor" and run it before you do anything else (currently this is the 2.0 version of the "Helix Editor", please check for the latest version as of your reading of this post). The "Helix Editor" will install all the latest drivers, latest version of the Updater and ensure you the most trouble-free path to a firmware upgrade. Again, it would be ideal if Line6 could force future versions of the Updater to check for the latest required files before allowing a firmware upgrade higher than the installed software. Failure to run the recommended global reset option after the firmware upgrade, for example, hold down footswitch 9&10 while rebooting. Make sure you do this before restoring your backed up presets. It is probably a good idea to restart the Helix after restoring your old presets as well before you start editing them. It will save you a lot of headaches. It seems sometimes there is a problem with some presets, usually user created or modified presets from a previous firmware version that can cause the Helix to lockup, with or without the USB attached to the Editor. If you are able to get into the preset for long enough to change any parameter even minimally and then save the preset again, often this will eliminate the lockup caused by the preset. Try to modify the preset without the USB or Editor connected. If you still can't get into the Helix before it locks up on that preset you can run the footswitches 11 & 12 reset procedure. This will delete the current preset the Helix is stuck on (make sure you have a backup of the preset first if you want to retain it). Lastly, do not abandon hope if your Helix appears to brick or the firmware update fails in some way. Most people who have found their Helix "bricked" from a new firmware update have been able to roll back to an earlier version of the firmware, sometimes a very early version, rerun the global update procedure and eventually get themselves back to the latest firmware release. There are several great posts from people who have found the right procedure to recover from a failed update and if you can't locate the correct procedure in the forum ask for help and someone can most likely get you up and running again. There is also always Line6 customer support. Good luck with your next update and fear not, they are well worth the effort and usually run smoothly (or I have just gotten lucky).

I agree, the new snapshot feature allows up to 8 footswitches that can turn on/off a huge array of pedals and parameters simultaneously. It is hard for me to envision a song that would require more than 8 potentially fairly complex scenarios. If it did you could always switch to the next preset and have 8 more snapshots/footswitches at your disposal.

Great find!

This may be an issue with the browser or a hung process on your PC. You may want to try clearing your browser cache or even rebooting your PC. If your login is working on the download page it should be working on the Updater. Also, make sure you have downloaded and installed the latest 2.0 version of the Editor installer which will install all the latest files on your PC.

You can attach an external midi controller and have additional footswitches available for use.

Big thanks and deep appreciation for how responsive you have been to your user base as well as following your own inspired design initiatives! You have a huge win on your hands and it is deserving of a prosperous future and destined to be a great success.

Try going to the download page and logging in. If that works the same username and password should work in the Updater. If necessary go through the process on the download page to get a password reset. If that does not work I would contact Line6 support for assistance or just create a new login.

I agree that a global setting to bypass cabs whether they are in an amp+cab or in separate amp & cab blocks would be great to have. Just wanted to point out that simply adding new separate amp and cab blocks to a preset (delete the old amp+cab block when you are done) and using the amp button to flip back and forth to the existing amp+cab block and match up the settings is simpler than writing down the settings. This is how I have done it when I ended up splitting out my amp+cab blocks.

From watching this pop up on the forum a few times now regarding the 2.0 update it looks like a combination of switching computers, USB ports, and/or reverting back to an earlier firmware version and the right combination of global reset options are likely to rescue most people who have had the Helix brick or have issues during the update. Hopefully though most people will get lucky and have the update succeed. Thanks for the kind words gents!

Interesting trick, what mix level and how many milliseconds are you setting the delay for? Also, are you using another delay somewhere further down in your signal chain as well?

Make sure the Helix is offline and you are not connected via USB before you edit the problem patch, otherwise it can freeze the second the editor connects.

Looks like you essentially already tried this but see this post from Inerzia, his Helix was totally bricked and this procedure brought it back. It looks like he rolled all the way back to firmware version 1.01.2 and then used the 5&6 reset procedure. Good luck! http://line6.com/sup...e-200/?p=163035

If you run into the same problem again I have generally found that changing any parameter slightly and resaving prevents the preset causing the problem from ever causing a lockup again. You must change something in the preset though. Mileage may differ but I have generally found this to work.

I have generally found that changing any parameter slightly and resaving prevents the preset causing the problem from ever causing a lockup again. You must change something in the preset though. Mileage may differ but I have generally found this to work.