Digital_Igloo

Here's a secret: Solutions to realize 95+% of legit IdeaScale feature requests were already in our backlog/wish list long before Helix was even announced. The spec and UI of at least half of those were already fully designed. Oftentimes "why did Line 6 do it this way?" can be answered with "so [future feature X] will work without screwing up your workflow." Product/UX designers from other MI companies might be able to look at Helix and say "Ohhhh, I betcha they're working on..."

We were hoping to put some of Sean's videos on there (already on YouTube), but because they're only in English, it might violate certain regions' trade guidelines. The next version of the manual will remove the "and more" callout. Distributing a hardware product across the world can be immensely complicated.

You mean the feature that's been in digital mixers, multitrack recorders, and DAWs for decades? :D

Not at all—IdeaScale is one of many tools we use. We do, however, need to defend our decisions to the organization, and it helps a lot to have metrics of some sort. "Oh, these two guys on the forum were talking about it" isn't a good defense when others might say "man, it's really annoying to have to keep touching the switch fifteen times to get back to the assignment I want." IdeaScale gives me (and you) ammo. In some cases there's a better solution that may not be obvious. Personally, I treat IdeaScale's feature requests less as solutions and more as problems to solve. Much of Helix was built from understanding the problems users had with existing Line 6 (and other companies') products.

Sadly, no rest for the wicked! Gotta finish this stupid record. When it's done, however, it. is. ON. Plus, my wife works for the airlines so we can fly there for free. :D I'd agree that it may very well be irrelevant to the end user. It's mainly to keep misinformation in check, that's all. If people wanted to scream bloody murder about how "there aren't enough bars on Helix's tuner," I'd probably say "I agree—vote that sucka up!" Just asked legal if I could leak a screenshot and was told no.

It's actually a UX decision, not a technical one. Repeatedly touching a footswitch cycles through all (up to) eight assignments, and any more than that would dissuade people from using the touch-select feature. I believe there's an IdeaScale request to expand this.

Oh, I get the whole semantics thing. That's not the problem. The problem is that when people read the word "accuracy," they don't rush to their dictionary. They instantly think "Oh, Helix's tuner is broken. When I play a note that's sharp, it must say it's flat or something." Then two hours later there are ten threads on ten different forums talking about how Helix's tuner displays an A when it's really A#. Misinformation spreads like herpes at Burning Man. For example, one person mentions how Helix's reverbs and eight of its ten wahs are M-Class (actually, they're rebuilt in HX with more nuance and control), and an hour later, I'm tracking down five threads talking about how all Helix models are fifteen years old. Yes, this has actually happened multiple times. Helix's tuner is not broken; its feedback simply isn't as granular as some would like. And that's something we can improve. Conversely, we will never improve the tuner's accuracy, because that's never been an issue. In every Helix Tuner thread previous to this one, I've explained that the thing to do—in fact, the only thing one can do—is vote the request up on IdeaScale. Not enough votes? We ignore it. Enough votes? We implement it (if possible).

Yes, but will it be more Hardhome or... RED WEDDING?

It also depends on your playback system. Generally, if your two wet speakers are smaller than your center dry speaker, you'd run them 100% wet; if all of your speakers are the same size/volume, 100% wet speakers might overwhelm the dry one.

The Volume block is at the end of a serial path? Or if it's parallel, is it after the Merge block? It should affect the whole path if it's at the end. Or if you want the reverb and delay to not be affected at all by the Volume block, you'd want to place it to the left of them.

Spoiler alert! Now I know not to expect big things. :(

I typically leave a bit of dry signal in the Wet part of a WDW setup, but there aren't really any rules. The preset TEMPLATES > 03B Wet-Dry-Wet FRFR and 03C Wet-Dry-Wet Amps have the Delay at 40% and the Reverb at 30%, but trust your ears.

You must be new here. >HUGS DREWHERRING12< "The snark shall continue until morale improves." —Abraham Lincoln Thank you for not using the word "accurate"; therefore, TO DO: Increase granularity of Helix's Tuner remains where it is in the priority backlog (that is, pretty high up and perhaps already developed).

Yep. There's a request in for increasing Helix's Tuner's granularity, which we plan on doing. How soon we get to it appears to be contingent on how few people misuse the term "accurate." ;)

You should, because anyone calling Helix's tuner "inaccurate" is spreading misinformation, and that does no one any good. It's now to the point that any time someone uses the word "inaccurate" with regards to Helix's tuner, I'll push TO DO: Increase GRANULARITY of Helix's Tuner down one step in the priority backlog. Yes, this horse is dead. Everyone please be patient.

It's probably only stupid fun for me (and Igor). For the rest of you, i'll be fuel for the fire trolls.

ITT: No one knows what "accuracy" means.

If Trails are on, the Return on Helix is indeed still enabled, but yeah, if H9 receives a PC message, its own trails will cut off. This is normal. Do you want to change H9 sounds while you're in the same Helix preset? IF YES—Assign a dedicated Command Center footswitch to change the H9 sound and a different switch to enable/disable Helix's FX Loop IF NO—Assign the PC message to one of the Command Center's Instant (lightning bolt icon) commands. In this case, recalling the Helix preset will also recall the H9 preset (no footswitch assignment necessary), after which your FX Loop switch will insert/disable H9 into Helix's signal path with (or without) trails

It's not, otherwise it would've been in 1.00. MIDI Clock Tx/Rx is at the top of my personal list, but I can't say when (or even if) we'll get to it.

Don't assign anything in the Command Center; just assign an FX Loop block to the desired switch (with its Trails parameter on, of course). Unless you specifically want to change presets in H9 (or presumably reload the current preset's default parameters), there's no reason to send a PC (program change) message. H9 should always be active; the FX Loop block simply inserts/removes it from the signal path. When the FX Loop's Trails parameter is on, bypassing the FX Loop block mutes the Send to H9 but leaves the Return enabled, so you can hear trails from whatever is connected.

Hey Jetdriver, Hope you don't mind that I quoted your last post from FB. I'm not sure why you'd want to send a PC message to H9 when you don't want to change its preset. Are you trying to reset it to its last saved state? Could be that reloading presets in H9 also reloads that preset's DSP instead of resetting the individual parameters. I understand why they'd do this—it's much simpler to implement. Yep; by default, Helix will send MIDI PC messages when switching its own presets. Turn Global Settings > MIDI/Tempo > MIDI PC Send/Receive to "Off." This won't affect any PC messages you send from the Command Center.

Press MENU (three lines icon) and then Knob 6 (Global Settings). Press HOME. Does Helix stay on the Global Settings page? If so, you probably have a bad HOME button. Hit CS up and they'll get you sorted. If not, it works fine, but note that 80-90% of what people do on Helix is from the Home screen already.

This was very deliberate on our part. The stretch goal has always been to get people to play more guitar and by extension, help take the industry back from spacebar DJs.

From either the hardware or editor, add an Impulse Response block. With the IR block selected, either: ​​Drag an IR file from the Impulses tab onto the IR Select slider. As you drag, you'll see the parameter outlined. —OR— Drag the IR Select slider right to select the desired IR from the Impulses list You can't drag an IR directly to the signal flow view, as they're not blocks—they're files for utilizing within either a 1024 or 2048-sample IR block (if you can't hear the difference, always choose 1024).

Press MENU and then Knob 6 (Global Settings). Use the joystick to select the Footswitches submenu and turn Knob 2 (Preset Mode Switches) to "Lower Row." Four Stomps appear on the top row and four presets appear on the bottom row (like HD500X's default state) To view 8 stomps, just press MODE to select Stomp footswitch mode. Global Settings are not accessible from the editor software.