HonestOpinion

I think BucF16 was having a problem where he was using "momentary" latching for the fooswitch and on/off state was not being reflected properly when he switched from one preset to another and came back to the preset with the momentary latch set. I have not been able to replicate that bug although that does not mean it doesn't exist.

Yes please!

I am not sure why you would want this behavior but I think your conclusion may be correct. I know of no way to do this.

Chuckle, hope it's a boy or that could be awkward :) Let me know how it works out for you or if the instructions need clarification.

Good point, that is probably what he was referring to. The wonderful world of color begins when using the Helix in "Stomp Footswitch Mode".

+1

Yes you can assign a custom footswitch ring color and they are actually different colors by default depending on which block you assign to a footswitch. They are not all red. The procedure is in the manual page 33 and it starts from the Footswitch Assign page. Customizing a Footswitch Color (from the Helix manual) 1. From the Customize screen, turn Knob 5 (Switch LED) to select the desired color (or turn it off). Normally, you should leave this set to "Auto Color." 2. Press Knob 1 (Cancel) or to exit.

LOL! The ghost of Charlie "Bird" Parker is rolling over in his grave right now.

I agree, locking functionality is a good idea! Please put it in Ideascale, I think it might get a lot of votes.

A great jumping off point thanks! I wanted to make it clear how to set the bypass state for each block as the manual might be a little confusing as it discusses bypass in the context of whether you are setting the bypass mode (momentary vs. latching) rather than the bypass state (block on or off).

A really important point, thanks silverhead!

After struggling with this for a while myself I think I found a consistent and easy way to assign multiple blocks to a footswitch and easily bypass the ones I want bypassed when the footswitch is off with predictable results. This may seem obvious but the previous method I was using always seemed to leave me having to save and go back and play with the bypass states again to get the blocks I wanted coming on and off with the footswitch ring reflecting their state properly. PROCEDURE FOR ASSIGNING MULTIPLE BLOCKS TO A FOOTSWITCH Click the "MODE" footswitch to enter pedal view if you are not already there. Use the joystick to navigate to the block you want to assign to a footswitch. Now touch and hold the footswitch you want to assign to your block to. Do not click or tap the footswitch, just touch it gently and hold it like your favorite toy. After you hold it for a second the "Footswitch Assign" screen will pop up. Hit "OK" to assign the footswitch. Now use the joystick to navigate to the next block you want to assign and repeat step #3. Again, as long as you hold (keep your finger down without lifting) the footswitch rather than tapping it, the new block you are attempting to assign to the footswitch will stay selected and the "Footswitch Assign" screen will pop up. Now repeat step #4. You can repeat steps #2, #3, & #4 for up to 8 block assignments (at least as of this post). Finally, after all your chosen blocks are assigned. You can tap (touch and quickly lift off, don't click) the footswitch you have assigned everything to. Notice this time you are tapping, not touching and holding. Each time you tap the footswitch it will move to the next block that you have in your multiple assignment. Push bypass (or not) for each block assigned depending on whether you want if on or off when the footswitch is engaged. Once you have done this you will notice that you can tap your way through the blocks and the footswitch will light up or go dim according to each block's bypass state. Last but not least, if you want your preset to come up with your multiple assigned footswitch on, make sure that before you save it, you select (using the tap method in step #6) one of the blocks that is not bypassed on the multiple assignment. It does not matter which one of the blocks that is not bypassed you select. The opposite of course applies, if you want your preset to come up with the multiple footswitch dimmed and not selected, make sure you select any one of the blocks that is bypassed. Now save your preset or all your work is for naught! Sheesh, with all that tapping and touching and squeezing this post was starting to remind me of an old Journey tune.

After going back to investigate this further I think I have the procedure that can be reliably used to assign multiple footswitches with no weirdness or unexpected results whatsoever. Please let me know if this works for you. PROCEDURE FOR ASSIGNING MULTIPLE BLOCKS TO A FOOTSWITCH Click the "MODE" footswitch to enter pedal view if you are not already there. Use the joystick to navigate to the block you want to assign to a footswitch. Now touch and hold the footswitch you want to assign to your block to. Do not click or tap the footswitch, just touch it gently and hold it like your favorite toy. After you hold it for a second the "Footswitch Assign" screen will pop up. Hit "OK" to assign the footswitch. Now use the joystick to navigate to the next block you want to assign and repeat step #3. Again, as long as you hold (keep your finger down without lifting) the footswitch rather than tapping it, the new block you are attempting to assign to the footswitch will stay selected and the "Footswitch Assign" screen will pop up. Now repeat step #4. You can repeat steps #2, #3, & #4 for up to 8 block assignments (at least as of this post). Finally, after all your chosen blocks are assigned. You can tap (touch and quickly lift off, don't click) the footswitch you have assigned everything to. Notice this time you are tapping, not touching and holding. Each time you tap the footswitch it will move to the next block that you have in your multiple assignment. Push bypass (or not) for each block assigned depending on whether you want if on or off when the footswitch is engaged. Once you have done this you will notice that you can tap your way through the blocks and the footswitch will light up or go dim according to each block's bypass state. Last but not least, if you want your preset to come up with your multiple assigned footswitch on, make sure that before you save it, you select (using the tap method in step #6) one of the blocks that is not bypassed on the multiple assignment. It does not matter which one of the blocks that is not bypassed you select. The opposite of course applies, if you want your preset to come up with the multiple footswitch dimmed and not selected, make sure you select any one of the blocks that is bypassed. Now save your preset or all your work is for naught!

I have one too, thanks anyway :P

The setting PeterHamm is referring to is in Global Settings --> Footswitches. Set the "EXP Pedal Postition" parameter to "Global". This will at least ensure that any patch with a volume block is reflecting the position of the expression pedal rather than just the preset's overall volume. Of course the preset's overall volume does factor into the position of the expression pedal regardless.

+1 I think the Helix is eminently worthy of purchase without wireless editing capability. However, I completely agree that wireless editing is a huge feature that I would have preferred to have seen on the Helix and have commented on this very subject as have others previously. I would love to have seen wireless functionality have been included for tablet or even PC editor modification of the Helix, even if it was only in the form of an Ethernet or USB port that would except a wireless router or USB wireless dongle. That would have kept the expense down on the hardware. The real expense of course being in the software and keeping it synched for various platforms. Perhaps we will see this in future versions of the Helix as it becomes more of a standard for the industry. PC sales are down, tablet's are up.

There are however also many examples of software within the industry where a particularly coveted item can be locked, or deletion or modify privileges revoked. There is also version control, managed/automatic backups, as well as undo features, all of which are designed to prevent accidental overwriting or deletion of code or product. I agree that if a lock feature were implemented it should absolutely be off by default and only used when someone has come up with the holy grail of patches that they absolutely want to ensure does not get overwritten, in which case, a good backup of the patch would suffice as well. As I stated before, in the list of things on my Helix wishlist, this is fairly low but still not a bad idea.

To prevent this part of your save procedure should always be to check what setlist and what preset location you are saving to before you hit the "OK" button. L6 did a great job of putting that information on the save screen so you can easily see what your target is. Although Silverhead is correct that it takes an explicit action to overwrite a preset there is still always the possibility of user error. The most likely instance being that you are either not in the list or on the preset that you think you are saving. I actually kind of like the idea of being able to lock a particular preset or even lock an entire set list. This would work well for the strategy I use. I never save tweaks to a factory preset. I actually always copy the factory preset to an alternate "User" list and tweak it there leaving the original preset untouched for future reference or in case I want to modify the factory preset differently and start again from scratch. Additionally, I don't have to worry about my tweaked presets being overwritten when L6 puts out new firmware that tweaks the factory presets, something I endorse them doing as it means the factory presets keep getting better. In my case being able to "lock" the Factory lists so they can't be edited (other than by a firmware upgrade) would work quite elegantly. With that said, this "lock" functionality falls relatively low on my priority list for things I would like to see first on the Helix. I also think it would be a great feature if the Helix App (librarian) or maybe down the road the editor could look at a saved "Bundle" or a saved "Setlist" and allow the restore of a single preset within that larger backup. It is quite a chore to save every preset individually, particularly if you edit your factory settings in place in the "Factory" lists (a bad idea in my opinion as stated earlier unless you need every preset location available on the Helix, in which case you are some kind of scary superhuman with more than 24 hours available in a day). Ideascale?

I think I understand the issue you are describing and I have struggled with it as well. To paraphrase the problem you are describing: When assigning a block to a footswitch the footswitch should light up when the block is engaged (not bypassed) In the case of a multiple block assignment, touching (not pressing) the footswitch again should cycle to the next block assigned to that footswitch, the footswitch should then light up or not depending on whether that block is bypassed or not. This does not always seem to happen consistently, particularly with the last block assigned making it difficult to tell which of your multiple blocks will be bypassed or not when the footswitch is depressed. Saving, and then going to another preset and then coming back to the one you were working on often demonstrates your assignment was successful but it would be nice for the process to be less confusing and not require this preset "save,switch preset, return to preset" procedure to establish what is actually happening with your multiple footswitch assignment. To reiterate, it often takes two attempts, switching away from and then back to the preset for a multiple assignment, to actually ensure every block is in the desired state (bypassed or not) and then possibly having to tweak bypass states a second time as needed.

Crap, found an even earlier post from DI from another thread. Guess I will have to save that frame for another day :wacko:

I see that detail about this happening on the Helix without the app, sorry I missed that. What a drag, that is just plain freaky. I would reinstall the firmware and do the button 9&10 reset procedure. If it happens again I would open a ticket with Line6. That does not sound good.

This fellow goes into these settings a bit in his video. I think he is stumbling in the dark to some extent like the rest of us but he sheds some light on the subject nonetheless.

Hey look, DI is starting to quote me now. He fills in the details better but I must finally be doing something right. I'm getting this one framed! :D

The only thing I can think of that might help is something you may already be aware of. You must have the Setlist selected from the pulldown menu (e.g. "Factory 1" or "User 1") that you want to import to in the Helix App before you run the "Import Setlist" procedure . Otherwise I believe it will just overwrite whatever Setlist you have selected. I don't think the saved/exported setlists have any context to know where you want to load them. You have to select your target list. This is probably how it should work because you might be loading to a different list than you exported from. This flexibility does unfortunately make it easier to load over the wrong list. Or alternatively, you may have run the "Import Setlist" procedure instead of the "Import" procedure, which now that I look more closely at your post may be what happened. The same rules apply there as well, make sure you select the single preset you want to overwrite before you run the "Import" procedure.

My observation has been the better a Line6 product sells, the better the support. Kind of stands to reason from a business standpoint. When they don't sell, you tend to see few or no improvements or firmware upgrades. Case in point, take the Stagescape M20d mixer. There has not been a new firmware release for that product since 9/25/2013, although they did release new drivers so it would work with OS X Yosemite & Windows 10. So the point is, everyone buy a Helix, recommend it to a friend, you 1%'ers buy a second backup Helix! The better this unit sells the more likely we will see new features, new FX/amps, and bug fixes. And btw, the track record on new firmware releases is stellar so far!