Digital_Igloo

Try reinstalling the 2.0 firmware from Line 6 Updater.

Works here. From the 2.0 hardware, press the PRESETS knob and then Knob 1 (Rename Setlist). From the 2.0 editor, click and hold on the current setlist's name.

With 2.0, you can even assign a footswitch or snapshots to the impedance parameter so your guitar's pickups can be loaded differently for the verse vs. the chorus. Now all parameters on the home screen can be assigned to controllers (including the Snapshots controller).

Mac OS X Windows

Now it can affect up to 64 parameters, and multiple switches can set different values for all 64 parameters. You're just using snapshot switches instead of a stomp switches. What's nice is that this might free up stomp switches to do cooler performance-based things like momentary delay feedback or momentary Variax B-Bender.

Not sure how the SP1 differs, but if the only difference is polarity, then yes. I know Yamaha expression pedals now work if the polarity is inverted.

New manuals are now up: Helix 2.0 Owner's Manual Helix Rack/Control 2.0 Owner's Manual Helix Edit Application 2.0 Owner's Manual Helix 2.0 Shortcuts (PDF download)

If you read the 2-page Helix Cheat Sheet, you're 80% of the way to mastering the thing. :)

I must've discussed this over 100 times already, but since you already know about coding and processor use, I'll be able to keep it short this time. ;) Full disclosure—yes, we could've done preset spillover! Introducing... The all new Line 6 Helix—only $1499! With the XT models you know and love from such classics as POD XT, POD XT Live, and POD XT Rack, Helix now supports low-resolution 128/256-sample IR loading and a second SHARC DSP dedicated to nothing but preset spillover! FWIW, Fractal's AxeFX II XL+ with dual 600MHz TigerSHARCs can't come close to doing preset spillover either. Know why? Because like every company on the planet (except for DigiTech, who presumably didn't have the time, resources, or desire to make a new modeling engine in 2006/7), they know that sacrificing at least half your performance for one feature would be incredibly foolish.

-18dB is a good average, but there's nothing wrong with boosting it if you like. But yeah, watch out for clipping the outputs.

For use in DAWs, IRs are applied to tracks that have already been tracked and boosted to line level. In Helix, they're at instrument level.

If you're expecting gapless preset switching, only the DigiTech GSP1101 does that, so what you're saying is that every single processor ever made except for one has a colossal inexcusable error. AX8 allows for gapless scene switching, which is very different from gapless preset switching and can be approximated to some extent in Helix today.

Whatever you connect Helix to should typically have mixing capability, but here's how to do it anyway: Add a Volume/Pan > Gain block. Move it down to Path 1B (or 2B if you're already using both paths). Move the Merge block down to create a duplicate output. Move the Split block all the way right to just before the Output block. Set Output 1A to 1/4" and Output 1B to XLR. Set the XLR Output block's Level parameter to the desired level.

We need more parks in cement block basements! :D

It was added with 1.06, so it doesn't appear in the 1.0 manual. I believe the CS guys are working on a new doc that lists all current shortcuts. EDIT: Here's the Helix 2.0 Shortcuts doc (PDF download).

Impedance is very different from level control (including the Guitar In pad). They're independent. The bypass state of the first block on Path 1A shouldn't affect the impedance circuit when set to "Auto."

Downstream mono blocks (including the looper) should not affect stereo signals when bypassed.

Your guitar will probably sound the most open and bright at 1M Ohm. However, some vintage pedals' inputs with lower impedances will load your pickups differently. For example, a fuzz face pedal's input impedance is somewhere between 5k and 8k Ohm; if Helix's impedance is left at 1M Ohm, people will say "Oh man, that sounds nothing like my real fuzz face!" For the same reason, real fuzz faces should be the first pedal in your chain. When Helix's impedance is set to "Auto," it looks at the first block on Path 1A and sets its impedance circuit to match that of the real pedal or amp modeled.

You can do this today. :) Set Global Settings > Footswitches > Preset Footswitch Mode to "Lower Row." Switches from Stomp mode will appear at FS2-5 in Preset mode. If you need to move stomp switches around, you can quickly swap locations by touching the two switches you want to swap for two seconds and then press Knob 6 (OK).

Totally normal. There should be no issue with leaving Helix Rack's (and Helix Control's) power switches on. As with any rig, however, always turn your speakers on last and off first.

The physical XLR jacks don't switch; the right side has jack-sensing so if no cable is sensed at the right XLR output, the firmware merges the XLR signal to mono.

Copypasta from an earlier thread: When someone unfavorably compares modelers to the tube-amp-in-a-room experience without providing both their monitoring rig/environment and expectations, I just assume they'd also be the type to say: "When I crank a 24-bit/192kHz recording of my girlfriend's voice through my $49 desktop speakers with 4" woofers in my cement block basement, it sounds nothing like when she's actually whispering in my ear at the park. Digital recording sucks!" With an identical playback system, current modeling algorithms have already been proven to fool golden-ear session guys and engineers in double-blind A/B/X listening tests. So why is this sentiment still so strong? I see four possible reasons for claiming modeling doesn't sound "real": The person is hearing said modeling out of context—for example, comparing the experience of a PA speaker, FRFR speaker, studio monitors, or headphones with that of a roaring 4x12 pointing at the back of their knees. Hence, the playback system is the bottleneck, not the modeler. SOLUTION: Use the modeler in context; that is, a preamp model into your real power amp and cab—or—learn how to compensate for how your particular playback system affects your tone. The person hasn't played the real amps and/or effects that have been modeled, and therefore has no reference for comparison. SOLUTION: Compare the actual amp and/or pedal in context, preferably in a double-blind A/B/X listening test. The person hasn't actually used a modeler, or hasn't used one in many years, and is just joining the "modelers suck" bandwagon. SOLUTION: Try one of today's top modelers IN PROPER CONTEXT (see #1). The person has fine-tuned ears, and is legitimately hearing very minor discrepancies and artifacts between the model and a recording of that particular amp, cab, mic, and mic distance combination. SOLUTION: Cool! Keep tweaking while we strive to make modeling even better. Most people who question or discredit modeling mistakenly believe they're in the #4 camp.

Any Command Center-based messages get saved with the preset, and saving presets into a different setlist should reflect the same values. Make sure Global Settings > MIDI/Tempo > MIDI PC Send/Receive is turned off so your Marshall isn't receiving redundant messages when recalling presets. If you're controlling external gear via MIDI, you should try to get in the habit of using the Command Center instead of the default MIDI PC messages. The latter won't let you reorder anything, as they're tied to the preset number, not the preset. Some boxes have a MIDI PC mapping function, and our instant commands can be used for this, except of course you get six commands per preset instead of one.

If your external devices respond to normal program change messages, you don't have to do anything—just leave that Global Setting on. If you need to send specific PC values per preset, any box would make you program individual values anyway. Or am I misunderstanding the request?

If your external devices respond to normal program change messages, you don't have to do anything—just leave that Global Setting on. If you need to send specific PC values per preset, any box would make you program individual values anyway. Or am I misunderstanding the request?