Digital_Igloo

Can any of you record a sample? Dom did A/B tests today and the Pitch Wham and Pitch Shift models sound completely identical between 1.12 and 2.0 here. Remember, global settings (including levels and impedance) have been reset to default values with the update, so it may not be the settings you're used to.

IdeaScale that sucka' up, amigo! :)

Exactly. :D

Yeah, and I use IRs as well, because there's a huge library of great-sounding IRs out there, many of which are free. Way wider variety than the 30 cabs that come stock in Helix. Who has better movies—Netflix or a small-town DVD rental place?

It's not that third-party cabs are inherently or empirically better; there's just a much wider variety to choose from. It's like buying an Akai MPC and preferring ten or twelve out of a million third-party samples to the included library... or preferring Netflix to the tiny DVD rental section at the small town general store. And like third-party MPC libraries and Netflix, there are a ton of awful third-party IRs as well.

Doesn't matter where you assign stomps to footswitches—the hardware or the editor—as long as you save the preset, they'll be there. The only thing that would cause weird behavior like this is if you failed to reset Helix after updating to 2.0. Holding FS9 and 10 while booting MUST be done as part of the update process. If you don't remember performing this step, please update again and follow the instructions exactly.

Phil's post just above yours explained this. It's still there, in the same spot. Nothing's changed footswitch-wise in 2.0 except for the ability to add a row of Snapshot switches to preset mode and the ability to have your Bank Up/Down switches act as Snapshot Up/Down.

From the manual: Snapshots also store and recall the following MIDI, CV, and Ext Amp messages sent to external devices from the Command Center: • The value of any Instant MIDI CC, Bank/Prog, MMC, and CV Out messages • The state (dim value or lit value) of any CC Toggle or CV Toggle messages as- signed to footswitches • The state (dim or lit ) of any Ext Amp messages assigned to footswitches So you don't get completely different Instant messages per snapshot—only different values.

You can skip steps 6 and 7 if you use the shortcut: Just push-turn the Page 3 Variax tuning knobs. Their values appear white and in brackets, indicating they're assigned to a controller (in this case, the Snapshots controller).

It's a heavily modified rectifier.

Move the Looper down to path 1B, select the Merge block and move it down to create a duplicate 1B output, assign Output blocks 1A and 1B to different outputs.

1.0 had exactly the features we had planned and scheduled for at the time; snapshots were always going to be a post-1.0 feature. We were originally going to release other stuff you haven't yet seen for 2.0; requests on IdeaScale dictated we prioritize snapshots instead. True. Snapshots have been in DAWs and digital mixers for well over a decade.

The preset has changed though, as the active snapshot is a storable setting. Hence the "E" icon.

Similar to the way snapshots don't let you load different blocks on the Home screen (only change bypass states and parameter values), snapshots don't change the types of messages sent from the Command Center, only the value. This is by design. Currently, TAP only sends on one Channel at at time. If you look closely at the table on page 34 of the manual, you'll see we had controlling Strymon's pedals in mind. :)

Amp models have not changed. However: Model defaults have likely changed Amp-model centric presets (beginning of FACTORY 1 setlist) have likely changed The impedance circuit on the Guitar In now defaults to "Auto" Resetting Global Settings (required for the update) may have changed some parameters that affect level

Did you click the pull-down menus that let you choose which app to download? I'd create dedicated links to each download, but that's a pain because I don't know what OS you're running.

Screw it; I'll bite. Unless your ears are somehow more finely tuned than those of the world-class LA recording engineers we invite to double-blind A/B/X shootouts, sounds like user error, a faulty Helix, cognitive bias, or extremely poor trolling.

Which link? The link in the OP is this one, which works: http://line6.com/software/

Absolutely. From the manual (page 34 "Using Snapshots"): NOTE: If you select a snapshot that hasn’t yet been altered, it appears the same as the snapshot you came from. As soon as you alter a new snapshot (say, by enabling or bypassing an amp or effect block), the snapshot becomes "active" and remembers any changes. The point of this behavior is that if you edit a snapshot and like the way it sounds, switching to a different, unused snapshot gives you the exact same sound so you can quickly create a variation of it. From the manual (page 32 "Snapshots"): Why should I care about snapshots? To be honest, maybe you shouldn’t. Ask yourself these questions: • Hey self, when performing live, does the small gap when switching tones drive me nuts? • If my delay repeats and reverb trails don’t seamlessly spill over when switching tones, does it drive me nuts? • Do I secretly wish I were an octopus, so I can constantly change amp and effects settings throughout a song? If you answered “M’eh†or “Huh?,†stop reading this now, go play guitar, completely ignore the camera icon, and you’ll never have to worry about snapshots again. Seriously.

Correct me if I'm remembering this incorrectly, but you had a Roland keyboard that wouldn't reliably trigger soft synths through Helix, right? The fix isn't that Helix strips out active sensing (actually, MIDI devices aren't supposed to do that unless it's a dedicated MOTU-level MIDI interface or MIDI filter/patchbay); it's that active sensing should no longer affect transmission of other MIDI data. Have you tried playing the keyboard? IIRC, we experienced the exact same issue you did with one of our engineer's M-Audio keyboard (which also constantly spits out active sensing), fixed the issue, and it worked fine. It's not completely unheard of that a bug could possibly find its way back into a later build, but your computer will see active sensing data regardless. EDIT: Igor just tested this again, and it's working fine with his M-Audio keyboard, along with buttloads of active sensing data. So the bug was indeed fixed. If you're still getting MIDI note dropouts, something else is going on. I have a Roland V-Synth in storage I can bust out if necessary.

Indeed. The gentleman is a guru.

If you want to press the footswitch each time, yes, Helix has always been able to do this. If you want a snapshot, however, to transmit a specific PC or CC value, it must be an Instant command. You can also create a CC toggle message on a footswitch, assign the min and max values as desired, and the snapshot will send either one, depending on whether the switch is lit or not. So the STATE of the switch determines if and what value is sent. Note that the Command Center will only transmit a CC value if it's different. Helix won't spit out a new value if it's the same. Likewise, if snapshot 1 and snapshot 2 both have the same CC toggle footswitch dim, and you switch from snapshot 1 to snapshot 2, no message is sent because the value is the same. However, if snapshot 1's CC toggle footswitch is dim and snapshot 2's is lit, switching from snapshot 1 to snapshot 2 will send the lit value. Never mind, just use the instant commands with snapshots. They're way easier to grok.

Groups of 4 snapshots can be on the upper row, lower row or both rows of Preset mode. Stomp mode is reserved for stomps. You can, however, use a short MIDI cable to send Helix itself a MIDI CC69 message from stomp mode to select a specific snapshot or even toggle between two snapshots. This is considered a power user hack, tho'. EDIT: If you try this, make sure Global Settings > MIDI/Tempo > MIDI Thru is turned off! Otherwise, you'll get a MIDI feedback loop.

:lol: Yeah, we probably wouldn't have spent resources on that feature if it didn't come for free with controller/snapshot assign of Variax parameters. It was a happy bonus. Impedance on the Variax signal is tricky—there'd have to be a variable impedance circuit in the guitar itself and there's not one—but that wouldn't preclude us from looking at it for a new Variax.

1. It is possible. Normally, any parameter assigned to a controller (including the snapshots controller) will update per snapshot. The exception is any parameter assigned to EXP 1/2/3, where people typically wouldn't want snapshots updating their wahs and volumes. However, if you set Global Settings > EXP Pedals > EXP 1 (or 2 or 3) Pedal Position to "Per Snapshot," Helix will do what you want. By default, this is set to "Per Preset," which is why snapshots aren't currently updating your values. 2. Messages assigned to footswitches are for realtime control, not per-snapshot transmission. Snapshots only transmit the following data from the Command Center: The value of any Instant MIDI CC, Bank/Prog, MMC, and CV Out messages The state (dim value or lit value) of any CC Toggle or CV Toggle messages as-signed to footswitches The state (dim or lit ) of any Ext Amp messages assigned to footswitches