codamedia

I'm surprised it's not mentioned here but the encoder ballistics changed in the 3.5 update . It is quite possible that a faulty/misbehaving encoder is being exposed by the new update. I would expect downgrading to fix that... when you downgraded did you do a factory reset to make sure the Helix was fully initialized? That is an important step whether you are upgrading or downgrading. Of course.. the encoder could have simply failed at an inopportune time. IMO... it's like taking the car to the mechanic and coming home with a new problem. As much as we want to say the mechanic broke it....99% of the time it's nothing more than coincidence.

When snapshots first appeared many users scratched there heads and said "what's wrong with stomps, I'll never use snapshots?". Fast forward just a few years and many (if not most) users will consider it a "must have feature" they "didn't know they needed". IMO, the combination of 8 snapshots and 10 stomps is exponentially more powerful than 24 single stomps. Learning a new trick is often worth the reward. If you really just want more footswitch options.... a MIDI Controller is your best approach at this time.

No, the Helix Controller can't connect to a Helix floor, however - you are on to something. Using MIDI you can enable/disable almost anything on the Helix and much more. A MIDI controller with a lot of footswitches would allow you to do exactly what you want.

IMO... you are approaching he Helix from an old school linear way of working with effects. I'm not dissing it... but that is what you are doing. Approach the Helix from a different mindset... "Presets/Snapshots/Stomps". Between the three of them you can accomplish so much more than 24 individual stomp boxes, with far less tap dancing.... but you need to take the time to figure out how and why. Open a support ticket and ask them. While you are at it... open an ideascale account (line6.ideascale.com).... search for this feature request (I know it's there already)... upvote it.

When using acoustic instruments, I always place the IR at the front of the signal chain. The way I see it... those IR's are more like adding a MIC to the instrument... and I want that tone as early as possible. The same applies to my Banjo, Mandolin, Classical and Acoustic IR's. All of my acoustic instruments are straight up PIEZO with a basic preamp... I really like adding the MIC tone to them.

My LT expression is working fine since the 3.5 update.... no different than ever. If the seller told you it didn't work, and it arrived working - you got lucky for a short time frame. It could be as simple as a bad connection internally or it could be a bigger problem. IMO, it needs service. If you are convinced the update killed it... when you updated the firmware did you do the "backup > factory reset > restore" from the instructions? Updates will adjust the global settings... a factory reset will initialize the entire machine... a restore brings it all back to a familiar operating state.

As you know, you answered your own question... There are numbers on that "cable tone" setting you can use as reference. At the highest setting you were simulating a 100' cable, at 11:00 (where you are now) it's a 20' cable - which makes more sense. FWIW, I keep my cable tone at 15'... I don't like it off because I'm used to 40+ years of using a cable. 15' sounds natural "for my use" As for noticing it most on the AC Sim... that's because the AC Sim relies on top end. If you've taken all the high end away the problem would be very pronounced. On normal guitar parts, it would just sound softer / less bright - but an AC Sim would be completely lifeless.

Two more scenario's, 1: I've known a few players over the years that toss a CAB SIM at the end of their traditional pedal board and go direct. Loading an IR in the HX Effects would do the same thing, with more versatility. 2: IR's are not only for CAB sims. In my Helix I use special IR's with my Dobro, Acoustic, Banjo and Mandolin... I wouldn't think twice of doing the same with an HX Effects.

That's a good resource... IMO... mic choice/placement/combinations is a critical stage in tone development. It doesn't end at the amp alone... traditionally that was just where you handed off the duties to an engineer or tech.

When your tone is in place and you only need to kick on a single effect, often for a quick passage. Sure... you can duplicate the snapshot to include that single effect, but that eats up snapshots pretty quickly. Fine for some, not for everyone. There are several benefits to each option on the Helix. That's why we have presets, snapshots and stomp mode. We can all choose what works best for ourselves.

I just glanced at the "tool" in question.... export preset upload preset to site choose target cab download preset import preset tweak new cab block Existing way.... copy preset to new location change cab tweak new cab block IMO, I can't understand how that tool would simplify anything.

I had to go listen to a few demo's.... it's a great sounding pedal. To be honest, it's sounds like a natural boost/overdrive which is where I lean to the Tee-mah (Timmy) in the Helix. The trick is to keep the gain relatively low and experiment with the clipping modes and tone controls.

Think of the tilt more like a "teeter-totter"... it teeters at the frequency set point.... that point itself will not be cut or boosted like it would in a "v shape". When you move to the dark, it raises everything below the set point while lowing everything above. When moved to the bright it's the opposite.

It's not hard... but the variables make for endless amounts of tonal variations. This is extremely rudimentary, but it may help. too immediate.... pull the mic back too distant... put the mic closer too bright... move the mic toward the edge too dark... move the mic toward the center some mics have proximity effect.... if they are too dark, pulling them back reduces the low end and vice versa Keep in mind... every 1" you move a mic makes a big difference. Sometimes a little movement is all it takes. Studio engineers will spend hours with mic positions before they touch an EQ. Do not go near the high cuts or low cuts until you have done all you can with positioning. Moving the mic toward the speaker edge will remove a lot more fizz than any high cut will. The same applies with pulling the mic away from the speaker.

I just did the update.... it works as outlined, but you do need to pay attention. If you break the sequence, all bets are off! When this appears on the screen... which is at the 50% mark give or take a little.... This also appears on HX EDIT .... You simply have to press REUME to continue.... If you panic and shut down either HX Edit or the Helix at this stage you probably end up on these forums wondering what went wrong!

Not really... It's not "snapshot 1" over and over... read on.... What is explained in that video works the same way for the helix/LT/Rack.... I wonder if you are missing the fact that this is done in STOMP mode, not SNAPSHOT mode. Programmed appropriately, a single stomp button can be programmed to lead you through any arrangement of snapshots you choose.

It's a good question.... maybe toss it over on "ideascale" (line6.ideascale.com)... with some traction they might add it back in. I suspect they wanted to get this update out.... and simply didn't have the time to add everything they wanted without holding it up longer.

Core tone updates.... nah, that's placebo or so subtle very, very few would notice. The cabs are something different. In a real world set up... any change to a speaker, cabinet or mic makes a difference. Better or worse.... that's always subjective. Some people will love this cab update, others will wonder why it was needed. IMO... Peoples knowledge of speakers/mics/placement will be a large factor in how they feel about this new option. Just in case it's not clear... L6 didn't replace anything, they just added options. All those old cabs & mics are still there and sound like they always have. When you fire up your Helix after the update your presets will sound exactly the same until you choose to try a "new cab block". At that point it WILL be different, and it's up to you if you like it or not.

You are not missing anything... they didn't include it. Remember... they didn't take your old cabs away. If you prefer the sound you get from an old cab with that mic vs a new cab with different mic(s)... you can still do that.

No they aren't... they would be fine additions, but I wasn't commenting on those. I simply like that fact that L6 continues to deliver models users are not expecting, and wouldn't want that to stop just because some users have no experience with it. I would never question your "wish list"... or anyone's wish list.

^^^^ THIS ^^^^ .... is exactly why I left the Cakewalk/Sonar platform 10 years ago Sure, this may be a legit problem with the L6 driver, but it always amazes me that Cakewalk/Sonar is the first one to fail, and fail miserably in these cases.

I fail to understand how you're lack of experience with a model makes you question it? Even after you admit it "sounds good"? Please Line 6.... do not follow this advice.

This thread is not the update instructions.... it's an attempt to help you when your update goes astray. For every problem post on this forum there are countless others that successfully update.... the instructions are fine, FOR MOST users!

I'm one of those users that reads the notes, follows them to a T and never have any issues with the updates. That said, computers are finicky little buggers and there are thousands of variables at play... we don't all have the same experience. What tends to bother me most is seeing the same post titles over and over again. Nobody takes the time to search for a solution... even when it's lurking on the same "1st page" of the forums.

Drag and drop as suggested... or.... I keep my presets in a single "working" set list. I just export that setlist then import it into Native. As stated already... be mindful of the IR's, those need to be loaded separately.