Jump to content


  • Posts

  • Joined

  • Last visited

Profile Information

  • Registered Products

jdosher's Achievements


Contributor (5/14)

  • Week One Done
  • One Month Later
  • One Year In
  • First Post Rare
  • Collaborator Rare

Recent Badges



  1. Looks like fullcompass has the full kit for $5 https://www.fullcompass.com/prod/607336-line-6-97-001-0016-washer-kit-for-helix
  2. That would be great if they've finally fixed it. What firmware are you running? Did you read my original post starting this thread (or ideally the entire thread)? Make sure you're really replicating the issue discussed in this thread. The issue isn't about two different EXT amp relay states in two different snapshots; it's about the having the same saved state in two snapshots, manually changing a relay, then switching to the other snapshot. In that situation the Helix (floor model in my case) changes LED state but does not actually change the relay to the state saved in the snapshot. Basically the unit compares the saved states between the two snapshots, sees that the saved state is the same, and doesn't issue the command to revert the relay. Read the original post (from 2017). I know it wasn't fixed in 2.8 - Line 6 actually really screwed up EXT amp relay switching in 2.8 (again, read this entire thread), and I haven't seen any comments in the bug-fixes reported for subsequent firmware releases indicating this 3-year old bug has been fixed yet.
  3. Amen. I can't envision a scenario where a user wants block bypass state, external effects loop state, the state of the LED ring on a EXT AMP footswitch, but NOT the relay itself to snap back to the saved snapshot state. I really can't buy the argument of "that's the intended design". What it is, is a design flaw - one that Line 6 has been negligent in addressing every since the Helix came out. It's really frustrating to see firmware release notes touting this and that new effects or amp model, but then release after release they're not addressing some serious bugs. IN FACT, they completely broke the EXT AMP switching in 2.80 and released the firmware without even realizing it. This is clear indication to me that Line 6 isn't testing how the Helix interacts with external amps, preamps, and effects units. Again, they're selling the ability to seamlessly integrate with real amps and external MIDI gear, but they're not implementing in a reliable, professional way, and they're not thoroughly testing their firmware before releasing it. I'm not a professional musician, and I'm not currently touring, but I've played guitar for 39 years, I've recorded several albums, and I take it very seriously. While I think Line 6 almost hit the ball out of the park with the Helix, over time I've started to feel like their intended target is just a tad short of the professional, serious, touring musician. And maybe that's not a bad thing on their part because, really, the ratio of "regular" folks to pro musicians is probably 100,000:1. You target your product where the market lies. I'm sure Fender makes way more money selling MIM Strats than Custom Shop guitars. For the time being I've thrown in the towel on the Helix. It's been pulled from my rig and I'm going a different route. I'll see what transpires when 2.81 is released (and also see how long that takes). FWIW, last night I plugged into a Timmy, the front of my Bogner Shiva, and stuck an analog delay in the fx loop. I was doing some volume swells and I could hear the transition from clean to distorted in the preamp, then the Timmy, then the power tubes. It was inspiring, and felt like a level of expression somewhat like a cellist varying bow pressure. I know - sounds like a bit of hyperbole, but it was something I haven't been experiencing with my rig in a while. The electrical engineer in me knows that quality A/Ds and models can/should be imperceptible to "the real thing", but something different sure was going on there. Or maybe I'm just trying to help myself ditch the Helix despite the unarguable convenience it offers. :-)
  4. It's not really clear from the manual though, is it? Because it also says this I don't think of the EXT AMP relays as "messages" - they're hardware built into the unit and I think they should be consistent with the button state. Oh well.
  5. Thanks for the info. I guess I don't see anything in the manual that leads me to believe the intended function is for the EXT AMP relays to NOT revert to the saved snapshot state. That bit of the manual I posted says to me that I should expect the relays to track the saved state. I think that's a bug. I don't see why anyone would want their fx blocks and external loops to revert to the snapshot state, but not the EXT AMP relays (assuming you have shapshot edits set to discard, which I do). If Line 6 doesn't consider that a bug and has no intention of fixing it, then that's another solid reason for me to move on from the Helix, just as @JeffMarshMusic discussed earler in this thread. I found a good deal on a used Boss ES-8 and I have a pretty nice set of pedals I've collected over the past 30 years, plus I just picked up this great sounding Bogner Shiva. I think it's time for me to go back to real amps and pedals. I'll see what happens with 2.81, try the ES-8 for a while, and decided then. If the Helix doesn't make its way back in to my rig it may end up relegated to home use. The amp and cab sims would be handy for songwriting and recording demos at least.
  6. EVERY time I turn my Helix on after the 2.80 update now it rebuilds the presets, quadrupling the boot time. Not just once. Every f*cking time. Also, my EXT AMP controls no longer work properly.
  7. Oh GREAAAAT. Now with 2.80 firmware the EXT AMP is even MORE broken. When I engage the 'ring' relay (should engage boost on my Bogner Shiva), it's now causing it to switch back to channel 1, even though the 'tip' relay is still engaged. I hate to say it, but my time with the Helix is coming to an end. I'm probably going to pick up a Boss ES-8 and go back to real pedals. Line 6 has failed to fix this bug, and now they've actually made it worse, to the point that I can no longer use the Helix at all to switch the channels and boost on my amp. They've also failed to implement a much needed feature (global blocks) which is what has lead me to use external pre-amps and/or amps and real drive pedals in the first place. I need a consistent sound, not 100 different amp sims to sound like other musicians. addendum: This is totally fcked up. Now when I switch EXT AMP sleeve on/off the built in expression pedal changes from 98% to 100%. Line 6 has seriously messed something up in the firmware.
  8. I updated to 2.80. No luck. The bug persists. I think that's strike 3 for me - this piece of junk is going on Craigslist. I've been working around this bug every since the Helix came out, but I've had my fill. Line 6 has added a bunch of useless amp and FX models I don't need, but can't fix a major bug. I'm done.
  9. Hi C4TH, Nope, that's not the issue. Read back through this thread. Save two snapshots to have the same EXT AMP settings (dim). In snapshot two press your EXT AMP footswitch (lit). Switch back to snapshot one. The LED will go back to dim, but your amp will still be in the 'lit' state (clean in your case). The Helix is comparing the saved snapshot state rather than the actual state of the relay when decided to toggle the relay state. Maybe (hopefully) 2.80 has fixed this. I hope it has. I'm going to try it this evening.
  10. Hi Phil, yeah, read back through my previous posts: the relays track state properly when only changing snapshots. The issue is changing relay state in a snapshot, then the relay isn't getting properly changed back to its saved (and indicated) state when changing snapshots (or recalling the same snapshot). If I assign a loop to a footswitch I expect that loop to go to its saved state regardless of what happened in a different snapshot. Same with block's bypass state. And I think the same should be expected of the Ext Amp relays! Clearly the system things it's changing back to the stored state - the LED ring turns off. But the relay doesn't change to reflect the state of the footswitch. When I go from a screaming lead on channel two with the boost (on my Shiva) turned on, then I hit 'CLEAN' to go to a nice, quiet clean sound, I'd say it's pretty serious bug when my CH2 and BOOST footswitches are dim but my amp is still screaming like a banshee and I don't know what the hell is going on!
  11. well, two things: the relay state is not a command that gets sent out the MIDI port like the CCs and PC messages. If the footswitch controlling a relay changes to 'off' in a snapshot, then you'd expect the relay to reflect that state, yeah? For the LED state and the relay state to NOT match is a serious bug. Period. Also, if you have Snapshot Edits set to Recall, then it won't change the Ext Amp (or other items you've manually pressed) back to the state in the new snapshot. That would defeat the purpose of going back to, for example, the clean channel when I go to snapshot 1. When I hit a footswitch that's labeled "CLEAN" I want the dang Helix to change my amp back to its clean channel!! I don't just want the LED ring on the Ext Amp footswitch to go dim while the relay stays close and my amp stays on its dirty channel. Right!? This is firmware bug - there's just no way around that. I'm hoping it's fixed in 2.80, or I may just ditch the Helix.
  12. Thanks Phil, Ah, I didn't realize 2.80 had finally come out last month. I'll try 2.80 and see what happens. I don't see it mentioned in the bug fixes with the 2.80 release, but I'm hoping for the best. I have Snapshot Edits set to Discard, so the saved state of the snapshot should be reloaded. Hence the "Everything turns back off..." in my second example. According to the manual the Ext Amp states should be recalled when changing snapshots. The LED state (dim or lit) is recalled, but the actual relay at the hardware level is NOT being set.
  13. Hi Phil, Yes, I'm on the latest firmware, 2.71.0. It's definitely not working correctly. And just to be clear, Ext Amp states will follow the saved state in snapshots as expected. The bug is that if you manually change a relay state then switch to a different snapshot the LED ring will change to the saved state, but the relay doesn't change. To reproduce this: 1) save two snapshots, each with Ext Amp tip off 2) switch to snapshot 2 3) press the foot switch assigned to Ex Amp tip to turn it on. The LED ring lights up, the relay closes. In my case, my amp goes to its dirty channel. 4) now switch to snapshot 1. The LED ring turns off, but the relay stays latched on. In my case snapshot 1 is supposed to be clean, but my amp remains on its dirty channel. You can also reproduce this with a single snapshot: 1) Save a snapshot with everything turned off 2) turn on all loops, blocks, Ext Amp states, etc. 3) press the snapshot footswitch again. Everything turns back off, including the Ext Amp footswitch LED, but the relays do NOT change back to the off (open) state. I've reproduced this with a Bogner Shiva, an Effectrode Blackbird tube preamp, and a DMM. This is most definitely a bug - not the intended behavior.
  14. In the hope that I could bypass this software bug by purchasing something like the Voodoo Labs MIDI amp switcher and using MIDI from the Helix, I tested this by assigning a MIDI CC toggle to a footswitch. Nope. It's even worse: MIDI CC toggle is only sent by manually pressing the footswitch. Even though the state of the assigned footswitch changes per snapshot, the MIDI CC is not sent. Line 6. Please fix your software bug and make Ext Amp switching work properly.
  15. The Helix should be able to do this, but the functionality is partially broken. You can change Ext Amp relay states on a per-snapshot basis, but if you manually change states (eg switch amp channels) the Helix will NOT change the Ext Amp relay(s) to match the state when changing to another snapshot. Major bug!
  • Create New...