litesnsirens

I tried a bunch of different things including global reset, patch rebuild, etc. Nothing worked, I've also put in a support ticket.

Just reporting back that performing the forced patch rebuild (footswitches 10 and 11 on start up) did not resolve the issue.

Did you do just the f10 and f11 restart. Just to rebuild the patches that was suggested in your thread. I haven't tried that yet but I'm going to give it a shot.

I'm having the exact same issue. It had nothing to do with the expression pedal position. But I may try the preset rebuild trick that William suggested. Now that I think of it I don't think my helix did a patch rebuild. Usually after an update or a restore from back up it builds the presets but then does it again the next time you turn on helix. I don't think that happened this time. I'm hopeful.

I've actually now noticed on occasion that when I select a patch and start playing right away... It fades in... Again it's all random.... It's going to be awhile before I can figure out if it's patch specific

One thing I've noticed since the 2.80 update is that many of my patches randomly load quieter. If I switch back and forth between that patch and another it will eventually come back at it's normal volume. It's really quite random and can happen to pretty much any patch. I don't think it's a volume pedal state issue because I can rock the pedal and it doesn't correct it. It doesn't seem to happen on my acoustic sim patches as a sidenote there's no amp model or cab on any of them. As you can imagine it's making leveling presets a bit of a challenge and it's going to be fun at my gig tonight.... But I'm sure it'll get sorted out at some point...

Great! thanks for the info...

I was going to say the same, that it boots faster, I’ve been doing so much re-working of my patches lately anyway so my ears are kind of fried but you may be right about the latency in the patches and maybe what I’m noticing in the CC momentary toggle is just and overall reduction in latency from the entire unit and has nothing to do with the use of the old workaround. While I’m here and don’t beat me up but is there a manual or and update to the manual out yet. If it’s out I can’t seem to find it.

What a great update. I haven't had too much time to try out all the new models but the Revv is great as is Grammatico. And the Tone Sovereign is just amazing. And the feature I've been waiting for, "momentary" on the CC toggle in command centre. I was previously using the the trick that Phil_m shared and assigning a gain block and setting that to momentary. I may be wrong but it feels like there is less latency with the direct momentary vs the workaround. I use it to control my voice live rack and feels like it's responding faster. Also the tilt eq has helped make my acoustic sim patches even better. So many great features to this update. Thanks line 6 for this awesome update. It was worth the wait.

The irony is just so thick. The person who is maintaining that we're all in the wrong for making off topic posts is on his way to taking first place for just that. At least Andy just made his point and then moved on. He made a couple of rebuttals but I don't think he ever got to the point of hypocrisy. The difference between off topic posts and ongoing chastising posts is that one of them is amusing. I'm happy to say I've never looked for it on this forum (or any forum for that matter) but I've noticed some forums out there have a "report" process. Perhaps it would be better if those that don't like off topic posts just report us the the moderators. If the moderators see fit, they can tell us to get back on topic.

I think it depends on your situation. I for instance play in two bands both of which use no amps (modelers for guitar and bass) and electronic drums (Roland TD-20). So, while there are dynamics based on the actual musicians’ playing it’s pretty consistent and there are no volume wars. I use a different preset for every song, so there’s lots to level. I use my ears to compare and level a few patches that represent various gain stages, I observe how they register on a decibel metre and then go through all my presets and use the meter as a reference to level all the patches. I recognize it’s still not going to be perfect but in my environment it gets me really close.

That’s good to know. I’m “OK” at soldering but I wouldn’t want to do any of that tiny detailed work that you see in circuit boards. I’m half decent with a can of de-oxit, though. Looking back, I couldn’t really say if my issue was the double press problem or not, to be honest, I didn’t really watch it that closely. I just know that on an intermittent basis when I would try to activate or deactivate the switch it wouldn’t work. I’d have to give it a few tries. This info will be very helpful. I’ll go with the de=on it first and once I have Helix open I’ll be able to tell if I feel like i have the skills to do the solder job in necessary.

I had my helix in recently and had a footswitch trespassed replaced...I suppose if this is going to be an ongoing problem I should learn to fix it myself.

I can't believe you actually let yourself hit the submit button on this one. It's just so ridiculous. The epitome of grasping at straws...

I severely doubt that's the case. There wouldn't be much incentive to harmonize the code amongst all the hx products if they were just going to give us this one last update. The main reason for bringing all the products in line is to make updates easier. There's still lots they can do...

I wonder if they'll announce 2.9 or 3.0 at summer NAMM....

OK, I take it all back, I will simply say I disagree with your previous statement. I’m not sure what that has to do with any of what you wrote above but, whatever.

So I originally found this pretty easy as I was just setting up the PA, which I own and which we also use to rehearse at my house. So I would tweak my tones through the system and had consistent sound when we went out to play. It sounded pretty good through my IEMs but I have JH Audio JH16s which are pretty good IEMs with 8 drivers per side. The rub was that it wasn't that great when I wanted to just plug direct into my power cab. It was confusing and I was just about to return the powercab and maybe just invest in another FRFR to leave setup (when I don't want or need to set up the PA for other reasons.) I discovered that if I brought the bass up in my patches it started to sound good in the powercab. I also noted that in my acoustic simulation patches I had a real problem somewhere between 160 and 170 hz making any of the lower E notes out of control boomy. I was controlling that with EQ on the patch but it made the acoustic sound kind of weak. So, I switched to the global EQ and dialed out some of the 170 hz with a wide enough Q to take out some of the 160 plus a bit of low cut. I re-tooled all my patches to adjust for the global eq settings. My acoustic patches are a thousand times better, and all the patches sound great on the powercab, on the PA, headphones straight out of the Helix and IEMs. I just have to remember to turn on the global EQ for the PA and turn it off for the powercab. Obviously those global EQ settings are unique to my PA. I suppose that there may be PAs that require nothing. OR that I could have added some bass on the global EQ to use with my powercab. But it seemed to me that the powercab was designed to be used with Helix so it sound good flat. And given that my a) my acoustic sim patches improved dramatically and b) I found I was dialing the bass way back on all the amp models, it was more likely the PA I should be addressing.

Ya I suppose that's an easy enough workaround... I'll mess around with it.. Thanks!

I haven’t figured this out and I’m not looking for some elaborate workaround. If there isn’t a way to do it I’ll do an ideascale post to offer this option. For sure I might request they do an option to do dual mics on the same cab (which would likely just be a change to the look of dual cab but again in mono. The problem is that if you want to use a Royer 121 to get the main tone of the cab and use a 57 to dial in a touch of top end, you can’t without affecting the stereo field. That’s just an example but if you put on headphones or like me use in ears live, your guitar can be heavy left or right if you don’t have the levels of the two cabs balanced in volume. This defeats the purpose because if I try to balance the cabs I have more of the 57 than I want. Even if you just pull up any random dual cab and then change the second cab, the stock setting of that second cab may be louder or softer than the first cab and will have the same effect. Having said all that if there is a setting that i’ve just been blind to so far (which is completely possible) it would completely solve the issue and i won’t need to do an ideascale submission.

I went down the IR rabbit hole, bought lots of them, used them, liked them then climbed my way back out and went back to the stock cabs. I really don’t think there’s anything you can achieve with an IR that you can’t achieve with the stock cabs. Except for the electric to acoustic IRs that 3 sigma put out I use those for acoustic simulation patches, there’s no stock cab that will do that for you but that’s another topic altogether. You could argue that once you find your IR that you love it’s quick to find and load, but you still have to find it and that’s a lot of work. Probably the same amount of work as auditioning all the various stock cabs with all the different mics at all the various distances. Then you can go dual cabs given you exponentially more options. Part of my personal stock cab revival was that I found the workflow made more sense and I could learn while tweaking which would give me an edge in future experimentation. I found with IRs it was load and try, load and try etc etc. At least while I’m spending time changing mics and distances I can do all that with the same cab loaded and I can learn how the different mics sound at different distances. Maybe, I’m wrong it just seems to make more sense to me... it sticks in my head better and that might just be because I can see what it is I’m doing where as with the IRs it’s all these cryptic IR names where each one tries to fit in the name the speaker, the cab, the mic the distance the axis into the name.

I disagree.

Maybe in the future Line 6 should just tell us nothing about impending firmware updates, then there’s no criticism on release dates or lack of communication. How can you complain about lack of communication regarding an update that you don’t even know exists. Then one day it just drops and everyone is super happy with the new features. During the whole development process Line 6 was able to happily work on it with no distractions or pressures from customers. I suppose potentially people might still cry about whether or not there will even be an update and where is the info on that, but Roland uses that model and everyone just knows it’s pointless to ask because they are famous for saying nothing. Line 6 could eventually develop that reputation. Further, I’m extremely grateful that the updates are free, but I would pay a reasonable amount for updates, after all there are costs associated with the development of new models and functionality so it’s not unreasonable. You can argue that other companies give free updates so Line 6 can’t charge but there are companies that don’t update at all. It’s just mind-blowing to me that people get out of sorts over a delayed release of a free upgrade. Having said all that, would I personally prefer that Line 6 adopt a zero communication policy and start charging for updates? Of course not but it might be better than the cringe I feel when I read some of the posts on here. I could just opt out of coming to the forums but I learn a lot here and I’m as curious as anyone else about various ongoings. I just think it’s flat out wrong to criticize (regardless of how tactful or repsectful you THINK you are being) the people who are working their butts off to bring you a free update. Whether you are criticizing the fact that the update is late or whether you want to smuggle in your complaint about it being late buy discussing the lack of communication.

I may be way off here, but when I read “spring 2019” as the “release date” (and I put that in quotes because it isn’t really a date), I look at it as more of a marker that they are aiming for. Considering they announced this in January, and then used a 3 month window as the “date”, that tells me they needed a whole bunch of buffer time. So I’m not overly surprised that they missed the “date”. That language indicates that it was, at best, a guess at how much work was left to do. Further, if you want to call “Spring 2019” a “date”, then as long as they get it out sometime in “Summer 2019” they’ve only missed the target by one “day”. I’m not a Line 6 fan boy (although I do love my Helix) and I make no critcisms to those among us who appear to be more anxious for the release than others. It’s just a comment on how I interpret the language that was used. You could go ahead and call them reckless for even throwing a timeframe out there but you know that would have only changed flavour of this thread ever so slightly. And at the end of the day, they are giving us something for free and apparently working very hard to continue to improve this product line. That alone should be enough encouragement.

I have Xvive and G10. Xvive is nice in that both ends are battery and so you can just charge it, plug one end into the guitar and the other into the helix. G10 has the little pin that defeats the signal so you can just unplug it without the "pop" and the end that plugs into the guitar is smaller and less intrusive. Both work pretty much the same which is great. With the G10 since I have to plug the receiver into a power supply I like keep it at the back of the stage (I just use a line from my pedal snake back to the Helix). This sometimes presents issues due to the fact that it is then in proximity to my rack that has the PA mixer and also a wifi router so that the guys can control their in ear mixes from an app on their phone. Usually just re-positioning the receiver a little farther from the rack helps, but if not, the Xvive straight into the Helix always works. I'm wondering if I can force my router to only work in 5gz mode and eliminate that issue. I'm not meaning to de-rail the topic but these are some things to consider with regard to routers. If you play some place that has their in house router close the stage it could present a problem. So far I've only played one venue in which the g10 was dropping out and I think it was a router interference issue. But it should work 90% of the time.