Digital_Igloo

Correct. We do this on purpose, in case this happens: Open the Customize screen for a Simple Delay block. See "Simple Delay" as the default label. Think "Oh, that's kinda cool. I can customize stuff. Maybe later," and close the window by pressing Knob 6 (OK) instead of Knob 1 (Cancel). Change the delay model to Mod/Chorus Echo. The big screen reads the new model but the scribble strip still reads "Simple Delay." WHA?! Now if you accidentally press Knob 6 (OK) without changing anything, Helix knows you probably didn't want to change the label, and doesn't apply anything. What's scary is that Helix is chock full of intelligent rules like this. It's an INSANE amount of work to get things to just work the way a user might expect. The easier something is to use, the harder it is to develop.

Ah. Say you start with a serial path. If you create a block and move it down, it creates a parallel path with both a Split and a Merge block. These Split and Merge blocks can also be moved. If you move a Split block down, it creates a duplicate Input; if you move a Merge block down, it creates a duplicate Output. The grayed out block you see is the Merge block. It doesn't do anything until you move it back up to Path 1A. But it needs to be there so you can grab it and move it up (if desired). The manual goes into more detail on page 17—"Moving Split & Merge Blocks for More Parallel Routings."

1) We brought a handful of golden ears into the big studio here at Line 6 and did three or four marathon sessions, where we A/Bed against other products and commercial recordings. If our raw Amp+Cab block didn't sound as good or better than all the other boxes (with the same or very similar Amp and Cab blocks), we kept tweaking. In a couple cases, we found some issues with the models and Ben went back and fixed things. In later sessions, we stopped A/Bing and just dialed things in by ear. Amp model defaults are way more important than presets. 2) Not quite sure what you're asking. Every possible combination of knob settings in every model is the true sound; where the knobs are set when first adding a model to a preset is just our default, and it can be pretty arbitrary. Nearly any amp or effects parameter can be returned to its default setting by pressing the knob. 3) There's currently no plan to create an exhaustive model and parameter guide, but I've wanted to find time to crank out a Template guide that shows how to hook things up for presets found in Setlist 8. I would say that Helix's models should be accurate enough that any manuals, documents, or YouTube tutorials about the original amps and pedals should be wholly appropriate. For example, any video on using the Klon Centaur should apply when using the Minotaur model in Helix.

You can also increment/decrement through IRs from Pedal Edit mode. That's actually a lot of fun, and you can play guitar while doing it.

That's a fair assessment, although I'd say that every possible knob position in Helix could be considered a sweet spot, depending on how you dial in your amps. ;) Kemper's big advantage is the ability to sample your own amps—especially those that have unique characteristics that may be lost from serial number to serial number. And of course the gigantic library of profiles available. It's really a clever platform. A good analogy might be the difference between a comprehensive Moog sample library (Kemper) and a hyper-detailed analog-modeled Moog softsynth (Helix). The sample library will have a ton of snapshots of a particular state of the Moog, and the filter and envelope knobs may work, but they don't necessarily behave exactly like the Moog's filter and envelopes. (Imagine applying an Akai or Kurzweil low pass filter instead of the Moog ladder filter—it may sound great, but it's not quite the real thing.) The analog-modeled softsynth may have fewer presets, but you can totally nail the nuance and behavior of every filter, envelope, LFO, etc., and even alter them in real time during a performance. Both approaches have their advantages and disadvantages; it's more of a philosophy difference than anything. Regardless, one would have to really hate life to not be happy with a Kemper, AxeFX, or Helix.

Yeah, you can custom label it from either the Footswitch Assign or Command Center pages. 1. From the Command Center screen, select Footswitch 1-5, 7-11, or Exp Toe with a command assigned and press Knob 6 (Customize). Move the joystick left or right to move the cursor. Turn the joystick (or move it up/down) to change the selected character. Press Knob 2 (Delete) to delete the selected character and shift all following characters to the left. Press Knob 3 (Clear) to clear the selected character. Press Knob 4 (Remove) to remove the custom label, after which the footswitch displays its normal assignment. 2. Press Knob 6 (OK).

Unlike HD500X, which were always mic level, Helix's XLR outputs are set to line level by default. If your Alesis monitors are expecting mic level signals, you'll hear what amounts to harsh clipping. Go to Global Settings > Ins/Outs > Page 2 and set "XLR Outputs" to mic to see if that helps.

Helix Rack's front bezel is tempered glass...

Ugh. C'mon, guys. Don't make me sic Line6Tony on ya'.

Nope, and we've discussed it ad nauseum on more than a dozen threads. Basically, it deals with deferred revenue, trade law, and believe it or not, Enron. No company is allowed to promise (or by extension, state something that could be inferred as a promise) anything without deferring revenue until said promise is fulfilled. Smaller independent companies, while still on the hook, are rarely baited, but larger, publicly-traded companies such as Line 6's parent, Yamaha, are under close scrutiny at all times. The only reason Apple's able to announce products or features many months in advance is because they have billions in cash and can afford to defer revenue.

Why not print the manual instead and skip the front and back covers (which are black)? Or invert the colors before printing?

Or, as has been stated many times... it's illegal for us to talk about what's coming.

Believe it or not, the number one request we had regarding the looper was to be able to remove it entirely, so it didn't use up footswitch or any DSP. As long as the same type of Looper block (mono or stereo) is on the same path (1 or 2) and is assigned to a footswitch, playback and recording should span preset changes. If any of the above criteria is not met, playback/recording will stop (which might be what you want), but as soon as you select an appropriate preset, you can restart the same loop.

We have two template presets that currently let you switch between two completely different tones within the same preset: 8 TEMPLATES > 2C and 2D. Both have spillover delay and reverb. Here's another way to build it yourself, starting with a new preset: Assign both Path's Input blocks to Multi. Place a single Volume/Pan > Gain block (both set to -120dB) somewhere on each path. Assign both Gain blocks to a single footswitch, but press BYPASS while one of them is selected. This makes the footswitch toggle one on and the other off. By extension, you'll be toggling between the blocks on Path 1 and Path 2. Any blocks (not just delay and reverb) after the Gain block on each path will spillover when switching to the other path.

I don't have Helix in front of me right now (lent it out over the weekend), so let's see if I can do this from memory... If you want to see what a footswitch does, just touch it. If you touch the A/B footswitch (FS8?), it should jump to the Controller Assign page for the Split > A/B block, where you'll see that the switch toggles between two min and max values: A100 (top path) and B100 (bottom path). This is basically switching your guitar signal between Paths 1A and 1B. If you follow the signal paths, 1A is routed down to 2A and 1B is routed down to 2B. This effectively extends both paths to the second DSP. (Path 2 uses an entirely different DSP chip.) Then the paths are merged back together before the Delay, Reverb, and Looper. So there's only one split and one merge. There's another way to accomplish the same thing, starting with a new preset: Assign both Path's Input blocks to Multi. Place a single Volume/Pan > Gain block (both set to -120dB) somewhere on each path. Assign both Gain blocks to a single footswitch, but press BYPASS while one of them is selected. This makes the footswitch toggle one on and the other off. By extension, you'll be toggling between the blocks on Path 1 and Path 2. Any blocks after the Gain block on each path will spillover into the other path. Just note that when you're running two paths full tilt with duplicate inputs, you may have to drop each Output block's Level parameter by approx. 3dB. Just like in a DAW.

Helix doesn't currently scroll banks, but it could.

Voted.

Done!

The scribble strips rows actually do have protection film, but you need a fingernail to peel them off. All are meant to be removed. The screens are easier to read without them.

I'd go VDI. You get all the communication features, like Variax model/volume/tone/tuning recall with preset, volume and tone knob as EXP 4 and EXP 5, power over VDI, etc. There's no harm in trying both to see if one sounds better than the other.

Ha! Sorry, bloodychoir. Sarcasm is harder to read when posting responses in 200 threads across two dozen forums. Cheers!

Sorry, there wasn't room to place a "Customize" button on the Controller Assign page. The Command Center page is currently the easiest way. There's nothing special about labeling a scribble strip from Footswitch Assign vs. Command Center—just two ways to get to the same window.

1.02.0 should be out tomorrow (hopefully!) with Variax fixes.

Please. As you can imagine, it's pretty easy to get lost in the madness that is the first weeks of Helix shipping. It's important to validate every feature and model request; otherwise I have to go to the team and say "Hey, yeah, some guys want this feature, but I can't remember where they asked for it, when they asked for it, or how many asked for it."

Yes. Helix has no output modes, by design. Some people will split their cabs to separate outputs so that connecting to FRFR vs. power amp+cabs is as simple as hooking up a different output. 1M causes the least amount of confusion. That's the only reason we chose to default to it. Personally, I choose Auto as well. We already know how this might be able to work in the future; add it to IdeaScale so we can vote it up! :)