HonestOpinion

It can be a nice alternative to have an external wah in a loop if you want to be able to switch to snapshots or presets where the wah is already engaged. That way you just leave the wah engaged and use the Helix to switch it into the signal path. As r2dk points out though you would have to add a loop to each preset. You can also do this with snapshots and the internal Helix expression pedal and wah. In regards to adding one of the Helix's native wah blocks. Not sure exactly what difficulty you are having? By default (unless a preset has a conflicting setting) when you add a wah block to a preset the Wah is assigned to the expression pedal's toeswitch on EXP 1. You have to press down what may seem like fairly HARD on the toeswitch to activate it and switch between EXP 1 and EXP 2.

Good question! And also maybe the extract below from the firmware release notes? Btw, probably not the issue and you may already have done this but it never hurts to check/correct your physical MIDI connections from the Helix to the Roland and double-check the MIDI settings on the Roland as you probably unplugged it when you did your firmware update. Looks like you already checked it but just in case a little more info on the settings: - Global Settings > MIDI/Tempo > MIDI PC Send/Receive has been split into two separate parameters—MIDI PC Receive and MIDI PC Send—and moved to Page 2. In addition, you may choose whether Helix sends or receives MIDI PC (program change) messages to/from MIDI, USB, both, or neither

I would love to see the Helix add another layer and decouple the idea of a setlist from the actual physical locations where presets are stored. That way you just dial up your "setlist" before each gig and each entry would be in the setlist order and point to the proper location for the corresponding presets. You would not have to mess with the actual location of your presets. As it stands now you have to go in and move the presets around manually if you want them in setlist order for a performance. Not trying to shill for the Headrush which IMHO is a completely different beast from the Helix, and much less to my liking, but I do think they were on the right track with how they implemented a "Setlist" as a separate concept from bank and preset locations. A good interface for this kind of meta-setlist creation on the Helix Editor would make quickly setting up for gigs a breeze. As it stands now I don't have the patience to setup a separate user list for each set for every gig in order. I end up jumping from preset to preset to get to the specific preset I need for a tune, some of them spaced widely apart. Hardly a tragedy but it does lead to some extra tap-dancing, unnecessary wear and tear on the footswitches, and takes a bit more time between some songs to locate the correct preset. As described above there is a better way to do this where setlists are simply pointers to preset locations. No moving/copying of presets required and you don't have to remember where a preset is located.

^^^^This! Changing this to "Authentic" will emulate the response of many stomp pedals when the delay time is changed.

Do you own the LT? I am inferring that because you described the device as going back to your other "view" after exiting the tuner. Is it the "Signal Flow" view on the LT that you are returning to? I have not seen this sort of behavior on the Helix caused by anything other than as zooey mentioned hitting the Mode switch by accident. If you do own an LT I wonder if anyone else with one is seeing this behavior? Assuming you have Presets/Snaps selected in your global settings. Also although I would think it would be unrelated, I am curious if you have this global setting: 'Footswitches' --> 'Snapshot Mode Switches' = "Auto Return? Also, just curious, what is the 'Tuner Out' parameter set to on your Helix/LT? Again, I would not expect either of these parameters to impact the view but just trying to cover all the bases. You mention that you are on the "2.1" firmware. Maybe it would be worth updating to the latest firmware where perhaps this may not be an issue. Just upgrading might save you some time troubleshooting something that has been fixed as well as giving you all the latest bug fixes and new features.

I don't know whether Stagesource speakers have the capability to have their DSP settings changed remotely but I like the idea. Voted!

Assuming I understood your post correctly I just wanted to offer a workaround you may already be aware of and have determined not to be ideal for how you use the Helix. Instead of assigning your amp channel switches to a stomp switch (pedal mode) assign them to a MIDI Instant command. That way when you change snapshots you should properly switch to the correct amp channel and still see all of the desired effect blocks with the dim/lit states reflected properly. You can switch amp channels when you switch between snapshots this way. You just won't be switching amp channels from within a snapshot. I think phil_m's suggestion to open up a ticket is also a good idea in the event that there is a bug here that needs to be addressed or an existing method to make things work the way you want. Many have found this video helpful for setting up amp channel select upon snapshot switch:

LMAO :D

Btw, not trying to offend, judge, or pigeonhole anyone, just attempting to provide some diversion over a holiday weekend. I have personally been a member of most of those categories at one time or another. Most forum users reflect less extreme versions of the characteristics listed for these groups. A bit of exaggeration was employed for entertainment value. It's all good! :P

Ironic, I see where you went with that. ;)

LOL! I think I may have veered into that lane at high speed with this topic. ;)

Most of us agree it is important to discuss and encourage innovation. Hopefully with as little rancor as possible. There does seem to be a few different camps of people on the forum when it comes to technology advancement requests and new ideas in general. Feel free to add your own I know I have overlooked a few. I think many of us move from one camp to the other depending on the day: "Glum" = Part pragmatist, part realist, part depressive. Often but not necessarily an engineer (and certainly not all engineers), or practical minded sort, long on solid procedural talent, short on creativity, and highly averse to change, there is almost nothing that does not already exist on the Helix that they can envision as remotely desirable. If it is not in there already as far as they are concerned it shouldn't be. He/she can be instrumental as a first line of defense against the worst ideas for changes and contrary to their group's name can make us all happy by reminding us that the device we have already is the best design that could possibly have been imagined and absolutely nothing would make it any better. "The Dreamer" = This guy read just a little too much science fiction and Tolkien as a kid (who are we kidding, still continues to), and listened to Bowie's "Changes" just a few too many times. Their imagination is always in maximum overdrive and they would prefer a weekly firmware update. This is your manic type with two or three types of ADD as well as ADHD, a prescription to Adderall that they neglected to take and they are on their fifth cup of coffee for the day. They never met an idea, no matter how outlandish, expensive or expansive, time-consuming, unnecessary, etc. that they did not like. They are lucky to have a 50/50% ratio of good ideas to bad at best although mileage may vary. When the ideas are good they can be visionary. This person's ideas can result in paradigm shifts and major improvements to the product when they have merit and get implemented. They are also the ones who may have a difficult time appreciating what is already "in the box" and may not have taken the time to examine its contents. This leads them to passionately entreat the powers that be for features that already exist. They are just moving too fast, are on to new changes before the latest can be digested, and are particularly annoying to the "Glum" type of forum user. "Night Templar" = Demonstrating fanatical devotion bordering on the theological, this protector of the faith sees every request no matter how reasonable to be an attack on Line6. They tirelessly defend the faith by shooting down every new idea or stating categorically that it is impossible, too hard, too expensive, or would divert development resources from the status quo. They refuse to acknowledge a bug and view them all as "features" even if it means they are staring at a blank screen on a device that produces nothing but a buzzing sound. Often classified as "fan-bois" they can help put the brakes on bad ideas, explain, defend, and justify the implementation on well-designed existing features, and often demonstrate extensive product knowledge as, to them, the manual and current feature set is an immutable holy text handed down by the gods to be studied for a minimum of ten to twelve hours a day and committed to memory. They can also show a glaring lack of objectivity and are particularly annoying when something is broken and needs to be fixed. Conversely they protect us from those who would fix something that ain't broke. "Ordinary Joe" = This is probably the most ubiquitous forum user. He/she may be a busy musician, have many other hobbies, interests and responsibilities, and otherwise has limited bandwidth for the forum. Occasionally makes suggestions for improvements that tend to be easily attainable, but usually only bother when they are features of relatively high importance to the way they use the Helix. They peruse the forum for tips and are generally content to let Line6 make whatever improvements they see fit on whatever timetable Line6 chooses. They tend to either remain silent or be supportive of other's ideas and make reasonable requests when their interests align, all in a tone that offends no one. We can all be grateful for these paragons of patience, restraint, courtesy, and rationality. "The Troll" = Self explanatory, this guy is a trouble-maker, mixer, lover of conflict and turmoil, or maybe just a fan-boi of or worse yet affiliated with a competing product. They probably don't even own a Helix. They are best left unanswered or diverted as they create a vacuum that can suck all oxygen, meaningful dialogue, and even the will to live out of the room. "The Vulture" = Lurks in the metaphorical trees above and loves to pick other's ideas apart like a piece of carrion but rarely contributes any idea of their own preferring to preside over and accelerate the swift death of nascent potential developments/fiascos and feast on the remains. Some would argue they occupy a critical niche in the forum ecosystem by removing the detritus of ideas that are either dead on arrival or decaying slowly. They can be a problem however when they band together and gang up on a healthy living idea. "The Technical Genius" = This guy loves ideas for their own sake. No implementation is too complex, no routing scheme or cabling monstrosity is a river too wide. They have auditioned over a thousand IRs, although they prefer to create their own, and are laboring on networking their Helix to NASA and a supercomputer. This forum member had at least five patents pending and three chess championships under their belt by the age of nine. They live for obfuscation and puzzle solving to fend off the madness that would otherwise surely ensue from the sheer monotony of applying Occam's razor to any problem. Their suggestions can result in ingenious possibilities who's only drawback is that they require advanced degrees in physics and aeronautics as well as a team of rocket scientists and several days worth of setup time to employ. They are also an invaluable resource and the ones who most often solve the truly challenging technical questions on the forum, come up with bug fixes on their own, post the most interesting if sometimes indecipherable explanations, and generally educate the rest of us on how to achieve some of the trickier setups. "Agenda Guy" = This one-trick pony quite possibly suffering from OCD is firmly fixated for extended periods of time on only one issue. For them no number of posts regarding their pet project is excessive and there is no topic that cannot somehow be construed as relating to their object of desire. They are the very definition of tiresome but it is their single-minded perseverance when all others have lost hope that can be instrumental in keeping a good idea or necessary fix in the conversation and eventually maybe even get it addressed. "Lazy, Busy, or New Guy" = This guy may lack the energy, initiative, or perhaps just the time to properly research what has already been covered extensively in the forum. Alternatively they may just be late to the party and the prospect of reviewing potentially thousands of posts is just too daunting. It is safe to say that this type is often not a prodigy when it comes to using search engines. They consistently find it easier (for them) to post a question anew than to check the 25 previous threads that have already covered it exhaustively. They do provide some utility in that sometimes they revive a topic that needs further examination, leads to further illumination, or the circumstances have changed since the topic was first discussed. "New Guy" of course is critical to the growth of the forum, provides fresh ideas, usually moves quickly into one or more of the above groups, and without them there would be no new and entertaining user names. "Your Type Here..." =

:D

I have spent more than enough time over the years on the phone with licensing support, using license protection devices/dongles, and all manner of arcane licensing schemes with software ranging from retail apps that cost $50 to enterprise software that costs millions of dollars. There is definitely a point of diminishing returns, somewhat predicated on how high the price of the software is, where over-protecting your software can actually start to hinder sales. You can end up irritating your customers and ensure that they will not recommend the software to others. It is kind of like a retail store. Sure you could put everything behind glass but there are greater profits to be had in most locations by allowing consumers to buy what they need with a minimum of inconvenience and deter theft with cameras, the occasional prosecution, and reliance on the fact that most people would rather purchase than be caught stealing. Maybe you put the really pricey and smaller items that are easy to shoplift behind glass. Granted the virtual software world model is different and people will steal software who would never shoplift but you still don't lock up a $200 dollar bicycle from Walmart with the anchor chain from a battleship - it is just overkill and way too much hassle for the consumer. Additionally, if you are a software and also a hardware company and are using your software to leverage and encourage hardware sales as Line6 plans to do with Native, the $99 price tag for Helix owners seems just right to me.

Do you have a tube amp? If so it is possible one of your tubes has become microphonic and it is just particularly obvious at high gain with the whammy bar. You can always test the tubes by tapping them lightly with a pencil.

Thanks aleclee, nice research! That "Frequency" parameter on the crossover option on the split block is almost definitely what was being referred to.

There is a split and a merge block but I am not sure exactly what this has to do with high and low cuts.

Agreed, the pricing scheme as it stands now, with a $300 discount for Helix owners, seems like it will have the greatest impact on driving Helix sales. The $100 savings on Native represents less of an incentive for LT owners although it will probably help sell a few. As you point out that $99 price for Helix owners will help defray Native's development costs and probably eventually, perhaps swiftly, result in additional profits. This will apply particularly if the changes to the firmware/software design that Line6 is currently working on result in streamlining product development for the entire Helix family on all of its various platforms. If improvements and additions to the Helix and LT firmware can be quickly incorporated into Native software (or vice-versa: Native --> Helix/LT), Line6 ends up with an efficient way to keep all the Helix products in synch and a method for maximizing profits while keeping product costs lower. Again, everyone wins. The only potential hitch I can see to the plan is if keeping the product line in synch results in substantial delays to firmware updates as it is now. Delays now are to be expected and are an inevitable downside during the revamp of the development process and its underlying components. I think the benefit to those focused on the Helix and LT rests in Line6's success in developing a relatively unified and expedited method for coding to all of the Helix products simultaneously. I know that is their goal and it should help to ensure continued success and sales and result in less time required for updates.

I agree completely and free for the Helix would be awesome and an even greater incentive although perhaps Line6 was concerned this would devalue the perception of Native for those who pay the $400 or $300(LT owner) price tag. People tend to place less value on products that are offered for free and resent having to purchase them when they are offered at no cost with another package. I can understand Line6's rationale. Not to mention that $100 multiplied by lots of Helix owners is still probably a respectable revenue stream.

Is it $299 for LT users? I will update my post, thanks for the heads up.

I just wanted to add that potential customers who are trying to decide between the Helix and the LT may find the $100 price for Native just the incentive they need to go for the Helix. They are looking at a $300 discount for the software when they buy the hardware. Similarly, hopefully those who are interested in Native may purchase the LT so they can pay $300 for it instead of $400. It seems to me that the proposed pricing for Native acts as an incentive that helps sell Helix and LT devices. As exciting as the prospect of Native may be, the Helix and its continued development, longevity, and support still remain my first priority and this pricing scheme appears as if it will help boost Helix and LT sales. I think everyone wins, Line6 and their customers. Update: Edited per price correction in twpmeister's post.

Upgrading the firmware wipes out the global settings. Any chance you had something configured in global settings that got reset?

Not sure this is the issue but are you using both paths for your preset? If not you are only utilizing half the DSP available and this can lead to dimmed blocks. Take a look at the Super Serial (X2) template. When setting up multiple amp blocks you often need to spread them across a Super Serial routing scheme to utilize all the DSP as well as get around the hard coded limitations of how many amp blocks and IRs are permitted per path. From the Helix manual: "That said, there are some rules governing the number of certain types of blocks you can add to a preset: Amp+Cab, Amp, or Preamp blocks Any combination, up to four (two per path) Cab blocks (includes Amp+Cab blocks) Up to four (two per path; Cab > Dual blocks are considered two) Impulse Response blocks Up to four 1024-point IRs (two per path) or two 2048-point IRs (one per path) Looper block One"

Does anyone know which block Ben Adrian was referring to in his quote referencing "Crossover filters" as 4 pole and 24db? Where is there a "Crossover filter" on the Helix? I feel like I missed some piece of information earlier in this topic or perhaps in TGP where this quote was extracted.