Digital_Igloo

Use one of the four Return jacks, set to instrument.

It's really not. It's actually notably faster to use the hardware—we designed it that way. The only thing I use the editor for is naming presets, because of the QWERTY keyboard.

The trick is that you need to monitor three inputs (Multi [Variax+Guitar], Variax Mags, and FOH Return), mix them all to one output, but mix only two of them to another output. Therefore, the IEM feed needs its own path, no matter what. If you didn't need separate processing for the Variax Mags, you could route Path 1A (with or without parallel processing) to 2A and use 2B for your IEM feed. So it looks like you either get one parallel path with IEM feed or two serial paths with IEM feeds. Again, there might be a workaround involving Send/Return patching. Will have to take another look later. Yep. Each path gets only one split, but you sort of get a third split between Paths 1 and 2 (by routing 1A and/or 1B to both 2A and 2B).

Okay, it still works. Instead, set 1A's Input block to Multi (which includes both Variax and your wireless Electric via the Guitar In jack), and 2A's Input block to Variax Mags. The separate output blocks for your IEM feed need to be fed by a path, which precludes parallel processing on said path. I'll keep thinking about it. Maybe there's a way...

Sorry, señor. Line 6 Updater won't work on XP. I stuck with Mac OS 8.6 for years after OS X came out. Worked flawlessly. Eventually, I had to rip the band-aid off, and it hurt.

It was never going to be "POD HD2". We just needed a code name for the metric ton of project management tools and files that are sent worldwide, and that's generally done first thing, so... not long after HD500 came out. Yeah, it's about the least inspiring code name ever. Most of our older wireless projects have early 1900's scientist-based code names. There are a bunch of Star Trek-based code names too.

Hmm... If I understand what you want to do, yeah, it looks doable. If your Variax and Guitar use the same processing blocks, you can do it with only two of the four paths: Set the input block to Multi. Split the signal right before the outputs. Move the merge block down to create two outputs (one set to Multi, which includes both XLR and 1/4", the other set to Send 3/4). Place a Return 4 block on Path 1B, right before the Output > Send 3/4 block. If you need separate processing for your Variax and Guitar, you'll need all four paths: After performing Steps 1-4 above, duplicate Paths 1A and 1B to 2A and 2B. Set Path 1A's Input block to Variax and Path 2A's Input block to Guitar.

Helix works great with GarageBand, with one caveat—GB doesn't support multiple outputs, so there's no way to reamp. If you don't care about reamping, you're golden.

With Variax's acoustic models, I generally don't use one, as they represent the signal of a mic'ed up real acoustic, not a piezo. So process like you'd process the mic in a studio—some compression, reverb, maybe a bit of EQ—done. There is a mic preamp model in Helix, and it adds some character, but my tracks haven't required it.

We'll hopefully get Helix Rack and Helix Control units out toward the end of fall.

1. Yes, they do that by default. 2. When you switch over to wah (EXP 1), the delay parameters (EXP 2) will be set to toe values. You could, however, use the toe switch to bypass the current delay and engage a separate delay set to your parameter defaults (with no EXP control). 3. Yes, use a Split > A/B block and assign a footswitch (or expression pedal for dynamic blending) to the "Route To" parameter. There are template presets set up and ready to go. 4. Yes. There are so many ways to do this, it's impossible to discuss them all in one post.

No, we removed that feature. It caused more trouble than it was worth. If a bunch of people really want it, it's something we'd consider adding back in. IMHO, for the best and most consistent experience, StageSource's speaker mode should really be global when connected to Helix.

TL;DR: A fix should be available soon. Hi Guys, This seems to happen to a wide variety of developers every year, and staying ahead of things in mobile OS-land is never easy, especially when phones and tablets update themselves. It's not like ProTools, where all the studio owners agreed to stick with Mac OS9.2 for years until Digidesign finally said OS X was good to go. Here's the scoop: We are well aware of iOS 9 breaking AMPLIFi Remote (Line 6 is far from alone in this regard, if you read gear forums) and we've assigned compatibility the very highest priority. Understand that in addition to ensuring that the update resolves the current issue, we need to make sure that new issues don't sneak up on us. Additionally, as with all other iOS developers, we have no control over the time it takes for Apple to approve the new app (every update—even tiny ones—must be approved by Cupertino). So unfortunately, at this time, we can't commit to a date, but it shouldn't be too much longer. Thanks for your patience, everyone. We apologize for any inconvenience this may have caused.

TL;DR: A fix should be available soon. Hi Guys, This seems to happen to a wide variety of developers every year, and staying ahead of things in mobile OS-land is never easy, especially when phones and tablets update themselves. It's not like ProTools, where all the studio owners agreed to stick with Mac OS9.2 for years until Digidesign finally said OS X was good to go. Here's the scoop: We are well aware of iOS 9 breaking AMPLIFi Remote (Line 6 is far from alone in this regard, if you read gear forums) and we've assigned compatibility the very highest priority. Understand that in addition to ensuring that the update resolves the current issue, we need to make sure that new issues don't sneak up on us. Additionally, as with all other iOS developers, we have no control over the time it takes for Apple to approve the new app (every update—even tiny ones—must be approved by Cupertino). So unfortunately, at this time, we can't commit to a date, but it shouldn't be too much longer. Thanks for your patience, everyone. We apologize for any inconvenience this may have caused.

Fewer A/D/A connections, yeah, but the difference is slight. If XLR is more convenient, that works pretty much as well.

<deep breath> Amsterdam units have been sent to the Yamaha distributor and should head out to dealers early next week. Newark units shipped to dealers today.

Always trust your ears, but the closest approximation of what the real amp sounds like mic'ed up is with full amp models and StageSource speakers set to P.A./Reference. If Guitar speaker mode sounds better, it may be that you're looking for more of an amp-in-a-room tone, which is completely cool.

Set L2m to P.A./Reference. Done!

Yep, and I change the BANK UP/DOWN switches to act like PRESET UP/DOWN and stay in stomp mode. Everyone uses Helix differently, and it's pretty flexible to use it the way you want. We stopped just short of 100% customizability (that is, any switch can be anything) to keep things simple. For example, in preset and stomp modes, FS6 is always MODE and FS12 is always TAP/TUNER.

On second thought, maybe not. I'm back in the office tomorrow and will confirm or deny.

I believe Helix does this automatically, but playback volume is controlled through ProTools.

Units in Amsterdam have been updated and are repackaged, ready to ship out to dealers (if they haven't already). Haven't received confirmation from the team in Newark quite yet.

Team Helix released 1.00 production firmware today.

Literally just received word: If all goes well, we'll be uploading 1.00 firmware into units in both Newark, CA and Amsterdam, NL this weekend. With a bit of luck, those who got their preorders in right away should see their units sometime next week.

You don't have to waste a path on a tuner—just a Send block. Keep the Dry Thru parameter set to 0.0dB (the default), and Helix will always send signal to your Tuner. Nothing to engage at all. Actually, if you have two band members sharing Helix, you can add two of the same Sends so you can share the tuner.