Digital_Igloo

Helix and HX Stomp have the exact same models. You're correct—HX Stomp is newer, and therefore the model list in its manual is more up-to-date. All Helix and HX SKUs are getting updated manuals for 3.0. They're just EXTREMELY expensive to translate, that's all. If we only had to provide English-language manuals, we'd update them every firmware rev (like we do with HX Edit and Helix Native manuals, which are software and for some reason don't fall under the same guidelines).

We do, but it's impossible to manage and share requests from here. The point of IdeaScale is as much the ease in sharing metrics with the rest of Line 6 as it is collecting metrics from our users. Considering forum interaction is literally 0% of any Line 6er's job description, what's more efficient? Capturing thousands of screenshots, organizing them all, counting them all—outside of work hours—and hoping the rest of the organization trusts my findings. Or: Sending a link to a secret IdeaScale subpage where ideas have been organized into easy-to-read charts?

Why 2.2M Ohm specifically? If we were to make a switcher, it'd have to be analog/relay. Any conversion would be into and out of any Line 6 processing (if it had any to begin with). So sort of the opposite of Helix, where instead of a D/A/D for every loop, you'd have an A/D/A for every time you wanted to insert a Line 6 amp/effect (or looper or tuner or whatever) between your pedals. I can only assume that's part of why Boss didn't add processing to their ES-5/8 switchers.

If Analog Devices made a thousand different SHARCs, all at different clock speeds, there wouldn't be an issue—we'd look at what your normal user would want to achieve with a signal path, look at the average DSP usage of a block and pick the appropriate speed for the cost. Unfortunately, the next notable step beyond POD Go's SHARC is either dual processors or a 1GHz Griffin, either of which would've pushed POD Go's price much higher, not just because of raw parts cost (and often additional components to manage, heat dissipate, and maintain EMI and ESD compliance with said faster processors), but because of development time and complexity. Also, dual-core processors like the Griffin aren't plug-and-play, and you run into many of the same pitfalls with dual processors (less flexible routing without incurring latency, etc.). One of the unwavering goals of POD Go was to make it affordable—without sacrificing sound quality—and that precluded anything other than the SHARC our system architect chose for it. We've also learned that the vast majority of our users don't use more blocks than what POD Go provides anyway. Yes, you may not be able to nail the massive swirly parallel shoegaze tone in your head, but that's why we also make Helix Floor, Rack, and LT. Or let you add pedals in POD Go's FX Loop. It's also important to understand what POD Go isn't. It's not a mini Helix. It's not even the successor to POD HD500X (which is really Helix LT). It's closest spiritual relative is the original POD bean from '98, which had one amp, one cab, a couple of effects max, was super easy to use for customers of all experience levels, and was portable enough to be taken anywhere.

There's no way to add it globally, because what happens if a preset is already at the limit and doesn't have enough DSP to accommodate it? What if all your stomp switches are assigned? In POD HD500X, we had to dedicate (some customers used the term "waste") X% of DSP just for the global looper, and those who don't care about the looper (or prefer to hook up their favorite 3rd-party looper) can't use that DSP for anything else. So it sits there, wasted. The Global EQ's the same way, but it's less than 1%, so it's not nearly as big a deal. With Helix/HX/POD Go, our solution was to make it easy enough to copy/paste a looper block into as many presets as you may need it. And ensure that as long as you use the same type of looper (mono vs. stereo, 6 Switch vs. 1 Switch), you can change presets without the looper stopping.

Nope, not yet.

Not in front of my work computer to look for hookup diagrams, but no .hlx file needs to be downloaded. It's built into Helix Floor/Rack/LT: Press the PRESETS knob. Select 8 TEMPLATES > 02B 7-Cable Method.

Blame your fellow Line 6 users. Before Helix, the top two looper-centric IdeaScale requests—by far—were: Get rid of the dedicated Looper footswitch so I can use it for something else Let me delete the Looper so I can use that DSP/block for something else We did exactly what our customers overwhelmingly wanted us to do—make the looper not global. There is no "restricted DSP processing power." Helix amps and effects simply use more sophisticated DSP tools than other boxes at POD Go's price point. If you believe the number of blocks is more important than sound quality and feel, you could request we make a special version of POD Go that has, say, 12 blocks, but omits all HX amps and HX effects. Y'know, like POD HD500X, with its global looper. Which is still available. The notion of "just add another DSP" is a non-starter. There's SO much extra design and infrastructure work involved in supporting multiple DSPs and it all but precludes the ability to use clean serial paths like the one in POD Go. In fact, it's so involved that a company copied EXACTY how we manage blocks across two DSPs in Helix (at least UI/UX-wise), because they couldn't figure out a more elegant solution. And no, we're not going to shoehorn Helix's multi-path signal flow into POD Go. POD Go doesn't use any of its SHARC for UI. Its MCU handles all of that, just like in the Mooer.

Set Global Settings > Footswitches > FS3 Function to "AllBypas." Now FS3 will bypass everything from both Stomp and Scroll footswitch modes.

Yes. There's even a template preset for this: 8 TEMPLATES > 02B 7-Cable Method. A single Helix Rack can also do 10-Cable Method and 13-Cable Method, although we don't include templates for those.

The following is found in POD Go but not Helix LT: Merged Bypass Assign and Controller Assign screens. Helix LT has too many parameters to fit on a single page of parameters Globally link or unlink separate Amp and Cab blocks. Helix LT has too many permutations of amps and cabs to apply any type of linking of separate blocks, although it does have both merged Amp+Cab and separate Amp and Cab blocks Globally assign a physical output (AMP OUT) to be tapped from right before the cab/IR block. Helix LT's routing is largely per-preset by design Quicksave the current preset to all preset locations called "New Preset" by holding ACTION and pressing Knob 5 (Save) while on the Save screen. Helix LT's fully dynamic DSP allocation precludes this Signal flow thumbnail appearing on the Play/Performance screen. Helix LT's signal flow is too big and it has more switches to display on the screen The following is found in Helix LT but not POD Go: TONS Even more once 3.0 is out

Guitarists/bassists who'd rather have something super fast and easy as opposed to powerful and flexible Guitarists/bassists who travel to gigs via subway, bus, bike, etc. Guitarists/bassists who can't or don't want to justify the cost of Helix Floor or LT Guitarists/bassists who need a backup rig for Helix Floor, Rack/Control, or LT Guitarists/bassists curious about modeling but aren't yet willing to jump in with both feet Guitarists/bassists whose friend/relative/bandmate owns Helix or HX and want the same sounds for less Guitarists/bassists wanting to learn what amps and/or effects they like so they can buy the real things later Guitarists/bassists whose local music shop or distributor is authorized to sell POD but not Helix Guitarists/bassists looking at budget $299-399 modelers and realizing that for a bit more cash (or waiting for a sale/coupon) they can snag one with a flagship engine and modern features IIRC, we initially pitched the top three bullets to sales/marketing, and the others sort of manifested themselves over time.

Two lines for stereo paths is something we talked about early on but there's no consistent way to represent what the user's actually hearing, so we punted it. For example, some blocks are mono-in, stereo out, some are mono but allow stereo dry signals through when the mix is set to anything but 100%, some are stereo in/stereo out, but the inputs are merged before processing... There wasn't an elegant way to explain all the possible combinations and even if we could, the signal flow would ultimately be more confusing than helpful. Sometimes less information is more.

The problem is that for every Helix block you use, unless it's directly before or after another Helix block, you're accruing latency, since going in and out of Helix processing requires A/D/A conversion. Presumably, that's why the BOSS MS-3 keeps all of its effects together and you can't insert a pedal between them. Of course, if you run multiple digital stompboxes without an analog dry path you end up with accrued latency too, so...

Unfortunately, the switcher market would have to get a LOT bigger for it to warrant stealing resources away from our bread and butter product lines. We had some mockups floating around for a while (IIRC, they would've been *expensive*), but they keep getting brought up, so who knows?

Helix can theoretically run up to 16 blocks per DSP, so 32 total, but you're never going to fill them all unless you really like Volume Pedals, Gain blocks, and EQs. HX Stomp is a stompbox, not a mini-Helix, and it's designed specifically for use on pedalboards with other pedals. We always knew we'd probably have to extend the block count to 8 (which is coming in 3.0), but released it with 6 because we wanted it to be a stompbox for a while (and attract pedalboard and amp guitarists) before all the high end modeler guys started applying Helix Floor guidelines to it. Plus, some of the new models that are coming up are extremely DSP-intensive, so some people won't be able to fill 6 blocks anyway, much less 8.

Wanna get up and running with POD Go quick? Watch these four videos (no talking heads, no intros, no "like and subscribe!") and in just over six minutes TOTAL, you'll be an expert: https://line6.com/meet-pod-go/

We've looked at it but unfortunately, the pedal switcher market isn't big enough for us to bother. We have limited resources and need to pick our battles carefully. Say the market changed and we were to revisit; any other features you'd like to see?

It should be printable now. We've removed the ability to edit them, however.

No, it's not a simple thing. The reason Helix doesn't have a Boomerang III, Aeros, Looperlative, or Repeater built in is because Team Helix hasn't: Stopped development of all new hardware AND Stopped development of our roadmap of new features and models AND INSTEAD Diverted all of our time, money, and effort to NOTHING BUT the looper for a year or more And we never will, because Helix is meant to be the centerpiece of a larger rig, not a picture-perfect replacement for everything everybody could possibly want to connect to it. When another company makes a standalone looper, they have an entire team of engineers and developers devoting 18-24 months to that single product. Helix's looper was always going to be utilitarian at best because no one can agree on what makes a world-class looper anyway. Look at the Headrush Looperboard—they spent gobs of time, money, and effort developing it, only to have 90% of looper geeks dismiss it outright because it didn't have the exact workflow and feature set they're accustomed to. Why would we want to follow them down that rabbit hole? If you want Helix's loops to sync to MIDI, visit IdeaScale and hope your request gets voted higher than the hundreds of other features and models that have been requested.

If one's going to control an external sound module via the Command Center, it's soooo much easier to just transmit MIDI notes. In fact, 8 TEMPLATES > 05A MIDI Bass Pedals does this automatically.

We have no idea. It always depends on the number and severity of bugs that are found. So if everyone agrees that 2.92 is perfect, yes, we'll get 3.0 out sooner. :)

Helix/HX 2.92, HX Edit 2.92, and Helix Native 1.92 are now available. All bug fixes. As always, PLEASE READ THE RELEASE NOTES and if possible, link to this page:

The bottom waveform is much closer to what I'd expect (and hope for!) than the top one. Actually, as long as you're recording 24-bit, you never want your waveforms to look like the top one; it much easier to run out of headroom on your DAW's busses. The notion of "track everything as loud as possible to get the best signal" was killed back in the 90s. Recording level is highly dependent on what blocks you use when recording USB In 1/2, but if you were to record your guitar's dry signal (USB In 3 or 4), the bottom waveform is likely what you'd get, as it's an instrument-level signal, by design. This lets you route it back into your signal path (when the Input block is set to USB In 3/4) at the same level your guitar would be at if it were plugged straight into POD Go. Otherwise, it'd be like running a half-dozen or more boost pedals before your amp; that is, it'd sound like total butt.

If you find the indication too sensitive, set it to "Coarse."