HonestOpinion

I have an idea in Ideascale for more acoustic guitar presets, effects, cabs and maybe even IRs. Please vote it up! http://line6.ideascale.com/a/dtd/More-amp-cabs-effects-and-presets-for-acoustic-guitar/791672-23508

Good luck!

I have gotten this error as well. I think the Helix librarian app is a bit buggy, at least on firmware 1.03.0 and Windows 10. I found that reflashing my firmware at least got rid of the "NACK" error showing on the Helix and the Helix app.

Great answer, way back when it first arose!! I think this was the correct explanation of the issue. Thanks and my apologies for batting it around until comprehension and confirmation finally set in. This may actually turn out to be a great way to implement the mix control even if it is a bit unconventional for foot pedal emulations. I already addressed this as the correct answer in another topic but I thought I would try to close the book on it over here as well since I posted a bug. Thanks!

Strongly agree!

Firmware: 1.03.0 Global Settings: Default Bug Description: Expression pedal loses ability to control wah and/or volume properly after assigning a custom name to the EXP toe switch scribble strip. Procedure to reproduce bug: Select a preset with a wah and volume pedal block. I chose 03A "Soup Pro" (I can select any preset with volume pedal and wah block and reproduce this bug) Press the "Home" button and use the joystick to select the volume pedal block. Make sure the expression toe switch is set to "Exp 2". When you move the expression pedal you should see the "Position" parameter move and your volume should change. Use the joystick to select the wah pedal block. Make sure the expression toe switch is set to "Exp 1". When you move the expression pedal you should see the "Position" parameter move and you should hear the wah effect. Press the "Global Settings" button and choose the "Command Center" Navigate to the EXP Toe Switch and press "Customize" Delete the first letter from the name displayed (if you are testing this on the 03A "Soup Pro" preset the name will be "Teardrop 310". Delete the "T" so it reads "eardrop 310"). You can rename it anything you want but I wanted to keep things as simple and repeatable as possible. Hit "OK" to save the custom name. Now hit the "Home" button again to exit the Command Center and return to the home screen. Repeat steps 2 & 3. (You should find that either the volume or the wah are no longer controlled by the expression pedal. That is the bug.) You can reverse the operation by going back into the Command Center and deleting your custom name. Normal operation is then restored to the expression pedal and it is once again able to control the wah and volume levels.

Thanks very much for testing! I think that is the same behavior I saw. So it is not just my Helix. I will submit a ticket to CS.

I reinstalled firmware version 1.03 and then reset the globals with the hold 9 & 10 and restart procedure. I am still seeing the same exact problem from a completely vanilla installation, all global parameters set to default. The "bug" is totally reproduceable and is immediately fixed when the custom label on the EXP toe switch scribble strip is removed. Can anyone else reproduce this bug? Here is my exact method for recreating the problem. I could really use some help from some other users to see if they can recreate this. DI has not been able to reproduce this bug and I am wondering if my hardware is faulty. Could some other folks please test this. Thanks!!! Select a preset with a wah and volume pedal block. I chose 03A "Soup Pro" (I can select any preset with volume pedal and wah block and reproduce this bug) Press the "Home" button and use the joystick to select the volume pedal block. Make sure the expression toe switch is set to "Exp 2". When you move the expression pedal you should see the "Position" parameter move and your volume should change. Use the joystick to select the wah pedal block. Make sure the expression toe switch is set to "Exp 1". When you move the expression pedal you should see the "Position" parameter move and you should hear the wah effect. Press the "Global Settings" button and choose the "Command Center" Navigate to the EXP Toe Switch and press "Customize" Delete the first letter from the name displayed (if you are testing this on the 03A "Soup Pro" preset the name will be "Teardrop 310". Delete the "T" so it reads "eardrop 310"). You can rename it anything you want but I wanted to keep things as simple and repeatable as possible. Hit "OK" to save the custom name. Now hit the "Home" button again to exit the Command Center and return to the home screen. Repeat steps 2 & 3. (You should find that either the volume or the wah are no longer controlled by the expression pedal. That is the bug.) You can reverse the operation by going back into the Command Center and deleting your custom name. Normal operation is then restored to the expression pedal and it is once again able to control the wah and volume levels. I would point out that I have one of the Helix units that has the extra tab sensor on both the right and the left XLR ouputs. I know there are versions floating around with only one tab sensor, on the left XLR output. Don't know if this is pertinent unless other hardware was changed as well.

Great idea, voted!

Yep, the dim functionality works just as anticipated. Just wanted to clarify, it still toe switches back and forth between volume and wah but the expression pedal only works on either the volume or the wah after the label is customized. Even when I am switched to the wah/volume the pedal does not work. It is the loss of function on the pedal, not the switch, that is mystifying. I will backup and reflash the firmware as well as doing the globals reset. Hopefully that will remedy it. Thanks very much for running the test on your Helix!

I apologize for jumping on the bandwagon here. I am perfectly content to wait for the editor for a reasonable amount of time although ideally at least a beta would have been available for the product release date. I know L6 polled their users and got no love for a touch screen but personally I would have loved to have seen an iPad app for programming. I have a multi-effect that uses this technology and the ease of preset setup with drag and drop, clarity and size of the screen, combined with the ability to attach it to a microphone stand or set it on a music stand makes for unrivaled ease of editing while practicing or playing live. I give L6 massive kudos for an incredibly well thought out and groundbreaking UI with so much to commend it, but there is no reason not to retain what they have and also offer a tablet based drag and drop interface. Future versions of the Helix could have a touch instead of a view screen built in as well as retaining their current revolutionary functionality. Drag and drop is one of those things that may seem like a just a drag at first but takes very little time to become a preferred method of programming for many. When iPad programming and/or a touchscreen is available along with a good PC editor and a state of the art physical interface like the Helix, you have a 1,2,3 knockout for usability. It would be irresponsible of me not to acknowledge that with this best of all worlds, kid in a candy store scenario detailed, that one of the great challenges and possible expenses for companies like L6 is keeping costs contained while trying to keep multiple platforms like Windows and iOS, and their hardware in sync, as they make improvements and add features. I understand that if I were part of a development team that had produced such an innovative physical interface I would want people to at least give it a good try before resorting to PC and iPad operation. With that said, almost no matter how good the physical interface is, apps for programming whether PC or tablet based are often preferred by many users depending on their circumstances. Determined by how and where they are using the Helix and whether it is for recording or live use (Until of course I get an interface I can operate by sheer force of will alone, are you guys working on that? ;) ).

Does that mean I may have a defective unit or need to try reapplying the firmware? Because in my case labeling the EXP toe switch is absolutely impacting pedal operation. I am on the latest firmware. Is anyone else having this issue? A simple check to see if you can still control volume and wah with the expression pedal after applying a custom label to the EXP toe switch should verify whether this is an issue.

Ah, I think I may understand what you are saying now. Changing the text on the EXP toe switch scribble strip actually modifies the toe switch behavior such that it can no longer flip back and forth between two blocks, e.g. volume and wah and operate the pedal properly. Changing the label means that the EXP switch and pedal now only control one block, for example the wah. You retain the ability to switch between blocks like the volume and wah but lose the ability to have the expression pedal work for both. If this was the operation intended wouldn't it make more sense not to allow the switch to toggle between the two blocks and only have it turn on and off the one block that the pedal can still control? I have to admit that sounds more like a bug than a "feature" but if that is what you are getting at I understand now. So for now if you wish to retain the ability to switch between two blocks (e.g. wah, volume) with the EXP toe switch AND retain proper pedal operation you CANNOT custom label the EXP toe switch. I would humbly request that behavior be modified to accommodate the ability to toggle between blocks as it does so well when the label is not customized. A request you have no doubt received many times already. Thanks for taking the time to respond and explain, much appreciated.

Thanks for the response DI. I get that the scribble strip is for the toe switch and considered using the terminology "EXP toe switch" instead of "expression pedal" in my post but thought I might confuse the issue (clearly that was a miscalculation). The problem I am most perplexed by is not with the scribble strip (although I look forward to that being enhanced). What I am seeing is that the expression pedal itself actually ceases to function properly when you assign a customized name to the EXP toe switch. The ability to control the WAH or alternatively the volume pedal disappears, at least on my Helix. Depending on the preset, either the volume or the Wah ceases to be controlled by the expression pedal. This is the behavior that is concerning me. I am wondering if everyone else is having problems with expression pedal functionality after customizing the text on the EXP toe switch scribble strip? This malfunction occurs for me on any preset that has a voume pedal and a wah pedal block assigned to EXP 2 and EXP 1 (default assignment). It appears that customizing the EXP toe switch scribble strip actually adversely impacts the operation of the EXP toe switch and/or the expression pedal. You lose the ability to control the Wah or volume and the behavior does not appear to be consistent, sometimes the wah functionality is affected and sometimes it is the volume but after a custom name, one or the other always ceases to work properly. I did not expect a labeling procedure to impact pedal or Exp toe switch operation. Removing the custom text in the scribble strip restores normal operation.

I think I am seeing the same issue when I customize the text for the expression pedal scribble strip. I name the expression pedal "WAH". After I label the expression pedal the Wah pedal function ceases to function. The text shows "WAH" but the actual function of the Wah pedal no longer modifies the sound or changes the "Position" value when the Wah pedal is selected. If I delete the custom name "WAH", then the Wah pedal starts working again. Is this a known bug?

After thinking about this for another couple of days I think you are absolutely correct. I needed to make the connection between series/parallel loops to the more PA oriented terminology inline/sidechain to really get what you were saying. This implementation does provide more flexibility and may be exactly why Line6 chose to do things this way on not only rackmount emulations but the footpedal emulations as well. Not very intuitive or faithful to the original "Mix" controls as footpedals don't usually operate this way, but ultimately more powerful and flexible while still retaining the ability to accurately mimic the pedal they are modeling (albeit losing some resolution in the "Mix" setting). In essence Line6 has enabled the "Mix" control on the footpedal emulations to operate as you would expect around the 50% region, but also to excel in scenarios where ordinarily you would have to use a rackmount type "Mix" control for a wet only signal. Now that I understand it, I like it!

If you have a separate output block I suppose you can do this by assigning the output block to a footswitch, select the "Level" Parameter and then set the "Min Level" to -120. You could also add a "Gain" block and use the same procedure.

If Line6 confirms this, I think these posts sum up how the "Mix" control works on at least some if not all of the Mod effects.

Makes perfect sense!

Thanks again for your answer phil_m, it took a while for all of the implications of your post to sink in. So, at 25% I should have a mix with more direct/less effect, at 75% I should have more effect/less direct. When you factor in the point twpmeister is making about how a chorus and many other mod effects work, the perception of max effect at somewhere around 50% makes perfect sense. It also took me a while to wrap my head around the fact that the "Mix" control on foot pedal emulations is essentially implemented the way it would work on many rackmounts. If at "Mix"=100% I am only hearing the slightly detuned and delayed signal with absolutely no direct signal it most likely would be perceived as having little to no chorus sound. I am just not sure why Line6 chose this implementation for footpedal emulations. On footpedals the "Mix" control usually results in the most perceived level of effect at 100%. The operation of the "Mix" control on the Helix footpedal emulations is more like you would see on a rackmount effect where 100% is usually only affected signal such that the effect can be used inline or sidechained. In the case of an effect like a Chorus this results in 100% sounding relatively unaffected depending on the severity of the Chorus settings such as rate or depth of vibrato.

This is a good hypothesis and was what I initially assumed the problem was. I think there is more to it than that though. Even if this were the case this would be a very unconventional and non-standard way to implement the mix control. Most mix controls on foot pedal effects do not operate this way. Most mix controls appear to be their "wettest" with the most perceived level of the effect at 100% (even if under the covers this is the result of mixing the dry and affected signals such that the listeners perception is that they have the max effect sound). On many rackmount units I believe the wet(100%) sound is just the max affected sound with no direct signal mixed in which would tend to support your hypothesis. Just not sure how much sense this makes for users accustomed to standard foot pedal operation, and after all, these are foot pedal emulations. I mistakenly started this topic when another similar one already existed. Please see Duncann's topic below.

An optional daughterboard with two extra SHARCs would be awesome! Not only would this give the option for spillover but I suppose it could also serve to turn the Helix into a, heehee, "Double Helix" with monstrous and excessive amounts of processing power for incredibly complex presets when not being used for spillover. This topic of being able to plug in optional hardware as well as software packs has come up before and I imagine sooner or later the industry will provide units with this capability to cater to "power" users. Not that the Helix isn't already spectacular. I suppose the trade-off for the company making an "expandable" product would be "can we make enough money selling the optional hardware versus the upgrade cycle of selling the latest and greatest new version of the entire unit?".

Spillover is not a huge deal to me either way although it is a great feature and makes for a more organic switch between presets. I am curious as to what is physically required for spillover DSP. Is it just an additional SHARC processor or is there much more required physically? Obviously there would be all the additional programming. The SHARC DSP processor(s) in the Helix, the ADSP-21469, is I believe relatively inexpensive ($15 per processor in bulk is what I thought I saw on the Analog Devices SHARC page, assuming they are listing the same version of the ADSP-21469 the Helix is using). I have no idea how much the PC board it is attached to costs or what expense would be involved in designing a custom board and adding a third processor just for spillover (assuming that is all that is required which I doubt). No clue on this topic, not an electronics guy, just curious what the actual cost of additional hardware would be to add true preset spillover capability without sacrificing any of the current processing power? Very comprehensive and positive review here that shows the SHARC processors and some of the other parts/components on the inside of the Helix, apparently the Helix is built with top quality construction and parts, from the chassis to the components: http://www.tonymckenzie.com/line6-helix-effects-unit-floor-pedal-inside-and-out-review.htm

A couple of notes in addition to the instruction posted by Digital_Igloo in the link phil_m provided. You can also use Global Settings/Controller Assign to accomplish this. One thing that may or may not seem immediately obvious is that in, for instance an amp block, you can assign several parameters to the same footswitch. Scrolling through parameters allows you to assign several to one controller. Picking one parameter does not "undo" parameters already assigned to that controller/footswitch. The "Min"/"Max" settings determine what the parameters setting will be with the footswitch in the on or off position (Min=off, Max=on). Let's say you want the X/Y state of the amp to maintain a steady volume level when you increase the "Drive". You want the "Drive" to increase and the "Master" volume to decrease when you turn on the footswitch. Do the following using the command center or you can apply digital_igloo's instructions to take advantage of some shortcuts: Select the amp block Go into Global Settings and select Controller Assign Select the "Drive" setting with the "Parameter" controller Select the footswitch you want with the "Controller" controller (redundant I know) Use the "Min" controller to select the drive setting you want with the footswitch off Use the "Max" controller to select the drive setting you want with the footswitch on Go back to the "Parameter" controller and select "Master" Select the footswitch you want with the "Controller" controller (redundant I know) Use the "Min" controller to select the master volume setting you want with the footswitch off (NOTE: in this example you want the volume to decrease when the "Drive" is increased (footswitch on) so the "Min" setting will actually be higher than the "Max" setting for the "Master" parameter) Use the "Max" controller to select the master volume setting you want with the footswitch on Customize the footswitch name if you like. Save your patch, you are done! You can repeat this process(steps 7-10) for up to I believe eight parameters, you will notice that both your "Drive" and "Master" assignments are retained. Now when you click the footswitch on, the "Drive" setting on your amp should increase and the "Master" volume decrease. When you turn it off, the drive should return to the values you set under "Min" for the "Drive" parameter and the volume should should increase to the "Min" level you set under the "Master" parameter. Remember the "Min" and "Max" refer to the footswitch state, on/off. The "Min" can be set to a higher number than the "Max" and this will determine what happens when the footswitch is toggled off.

Make "LED Ring Brightness" setting variable instead of on/off. This setting is under Global Settings/Displays. Right now you only have a choice of on/off, instead of being able to vary the brightness of the rings around the footswitch when it is in the "off" position. It would be great if you could vary the brightness of the footswitch ring when it is "off". This would accommodate different light levels on stage (dark, daylight, etc.). I also find the default dim level in the off mode to be just a little too bright for my eyes and it can sometimes make it difficult to tell if the pedal is on or off at a quick glance. With a variable dim setting the ring brightness could be customized for different eyes. I love the footswitch ring feature! Please retain the ability to turn the ring all the way off in the "off" position but add the ability to vary the brightness (assuming it is physically possible with the LED's you are using). Thanks! You can vote for it here: http://line6.ideascale.com/a/dtd/Make-LED-Ring-Brightness-setting-variable-instead-of-on-off/792849-23508