Digital_Igloo

Provided 1.12 behaves nicely, that is indeed the plan.

You would think, except it's important to note that the Helix editor isn't like a plugin or DAW; it's a remote control that reflects the capabilities of the connected hardware. The Helix hardware would need to support undo/redo first, and from what I understand, that's not insignificant effort. I believe there's an IdeaScale entry for undo/redo; it's definitely worth voting up. :)

Updated thread to 1.12.0 (released 11. May 2016).

Or we have a better solution looming...

FW 1.12 adds nothing but support for the feature complete (customize footswitches, copy/paste blocks, comprehensive keyboard shortcuts) 1.12 Helix editor and bug fixes. Both were supposed to drop today at noon, but we found a bug literally at 11:59am. So probably tomorrow. Once that's done, we'll merge the new feature FW with the existing feature FW and'll see what blows up. Hopefully not much.

A pretty decent majority of Helix's models would set the impedance circuit to 1M Ohm anyway. I keep mine set to 1M Ohm as well, and will only change it if I'm looking for a specific sound.

Impedance switching isn't always perfectly transparent either, so anything that might cause sonic surprises should be avoided. It's much easier to implement (and explain!) to just pay attention to the block, not the block's bypass state—and certainly not up to 32 blocks' bypass states! :blink:

Depends on the pedal. If you only use pedals with true analog bypass and no buffer, then the loading of your guitar can move to the first active pedal. Otherwise, it typically stays with the first pedal, regardless of its bypass state. It's actually quite a bit more complicated than that, but I'm not sure we'd want to climb down the rabbit hole and have impedance jumping all over the place depending on various blocks' bypass states, especially considering Helix's routing and multiple input blocks. A ton of modelers (even some expensive ones) don't have variable impedance circuits at all. When the Guitar In Impedance parameter is set to "Auto", Helix simply looks at the first block on Path 1A and applies the value from a look-up table to the impedance circuit. I'm afraid anything more complicated than that may not have much ROI. Regardless, we think we have a better solution. Stay tuned.

Not... currently, no. ;)

If you happen to have the camera kit for your iPad, it just works. No return block necessary or wasting jacks. More flexibility with the return block tho', as it can exist anywhere on any path.

We're probably going to end up changing the default to "Auto." That seems to be most people's preference anyway.

To be fair, one of those improvements was to replace the 1/8" TRS jack (always more flimsy, especially when dealing with drunk fans) with more robust 1/4" jacks. :) But it really depends on what you're connecting: Apple/Google smartphone or tablet, Mac/PC, iPod Touch, or anything else supporting class-compliant audio—Just connect it via USB and Helix will route it directly to its outputs with no additional D/A/D conversion (plus it sounds better!) Portable CD player, iPod Classic/Mini/Nano, Minidisc player, or Zune (more rare these days)—The only difference is that you'll need a different cable—1/8" TRS > L/R 1/4" as opposed to an 1/8" TRS > 1/8" TRS. Neither cable is typically included with a playback device; you'd need to hit a music store or Radio Shack anyway Component CD player, Minidisc player, or DAT machine—Save as above, except you'd need a L/R RCA > L/R 1/4" cable as opposed to a L/R RCA > 1/8" TRS, neither of which are included with the player

Are you playing barefoot? If you have a Command Center command assigned to a footswitch, touching the footswitch with bare skin jumps to that item, whether it's on the Home screen (block bypass), Controller Assign screen (footswitch-as-controller), or Command Center (MIDI/CV/Amp command). This is by design, and means any assignment is a touch away. You can disable capacitive touch by turning Global Settings > Footswitches > Touch Select off. If you're wearing normal shoes and Helix still jumps to the Command Center screen, something's up.

Provided connections, gain staging, and impedance are all set properly (and your Helix is working fine), toggling between the real distortion pedal in Helix's effects loop and the model of said distortion pedal should sound and feel close to identical. We spent a lotof time A/Bing, and were able to fool some hardcore golden ears in the process. One particular guitarist well known for his obsession with the Klon straight up couldn't tell which was which. If the distortion pedal is the first block on Path 1, Helix can automatically set its Guitar Input impedance circuit to match. Just set Global Settings > Ins/Outs > Guitar In Impedance to "Auto."

If I've ever said or implied that Helix's tuner's granularity is "good enough," then I apologize. I don't remember ever saying this, but I do remember saying that many people prefer specific types of tuners and we've designed Helix to seamlessly incorporate them. That shouldn't imply any sort of dismissal. Yes, we can provide greater granularity. It's toward the top of our list. Thanks, señor.

Hi Dave, The tuner in Helix has an accuracy of 0.1 cent (1/1000th of a semitone), not 1 cent, and again, we have über-expensive testing equipment that can prove this. Accuracy has nothing to do with how fine the visible feedback of the note played is displayed; it only has to do with whether or not the correct box is lit. Say you did a search for my house in Google Earth. If Google Earth tells you "Los Angeles," when you wanted a neighborhood or street address, that doesn't mean Google Earth is inaccurate, because I do indeed live in Los Angeles. Google Earth would be inaccurate if it said I lived in San Diego, just like Helix's tuner would be inaccurate if the wrong box was lit. What you mean is that Google Earth's granularity (or precision if you prefer) is not as high as you'd prefer. With greater granularity, Google Earth will tell you that I live in Hollywood. With even greater granularity, it'll tell you I live in Cahuenga Pass between Universal Studios and the Hollywood Bowl. Again, I'm not claiming Helix's tuner is perfect, and sure, we could add more granularity (greater number of bars) when the note appears close to being in tune. But unless you require better than 1/1000th of a semitone accuracy, claiming the tuner is inaccurate is... wrong. Some might then say "Sure, fine, granularity, whatever." No, not whatever. I've seen first-hand how misinformation spreads online. One dude says something like "Eight of Helix's ten wahs originally started in HD but have been rebuilt in HX with more nuance and control" and 24 hours later ten forums are filled with people claiming all of Helix's models are 15 years old.

Please stop using the word "inaccurate" if you don't know what it means. Misinformation spreads on the internet like wildfire. If you want Helix's tuner to have more granularity, vote it up on IdeaScale.

Just confirmed with Ben; Helix does indeed implement a 3dB pan law. How exactly are you panning between two split paths? Perhaps there's something in the block usage and routing.

I'm pretty sure we do it automatically; it was in the definition for sure. IIRC, it's 3dB; will have to check with Ben tomorrow. Maybe it was dropped at one point and no one told me?

Good stuff, bobguido. Cheers!

Command Center or Controller Assign? The Command Center screen shouldn't have anything to do with the Split block. Could it be that the Split's bypass is also assigned to the footswitch? Bypassing the Split > A-B block will give you your 50-50% split.

It does. Igor has an M-Audio controller and Dom has a Roland SPD-S. Both were funky before; both work fine now. Update's coming this week (hopefully).

We added the word "Firmware" to the version indicator in the upper left corner. It'll be in the next software rev.

You can't move the EXP toe switch elsewhere, but you can use another switch to toggle between, say Volume and Wah and leave both controlled by the same EXP: On the Footswitch Assign page, change the assignment of both the Volume and Wah blocks to the to the desired footswitch. On the Controller Assign page, change the assignment of one of them so they're the same. If both blocks are on (or both off), select one and press BYPASS. Pressing the switch will then toggle between control of Volume and Wah. Unfortunately, this doesn't really apply when assigning a Volume block and a Gain parameter to the same footswitch. In this case, to avoid the EXP toe switch, the best solution is to simply connect a second expression pedal.

Hold down footswitches 9 and 10 (middle two on the bottom row) while booting. This will reload all presets and reset all globals. If the volume is still really low with multiple instruments and multiple cables, it very well may be a hardware issue, I'm afraid.