Digital_Igloo

Impulse responses don't have to emulate a cab. They can also be used for acoustic guitar emulation, room emulation, reverb, or the frequency response of an entire song. IIRC, the first IR capture utility was a Steinberg plugin called Free Filter. At the time it was used for applying the frequency response of one song to another for mastering multiple songs against each other, but it likely could've been used for cab emulation had any of us thought to use it that way. Not sure exactly how Fractal's tone match engine works, but most tone match solutions are some variation of what Free Filter did back in the 90s.

I don't bother wasting DSP on a new block just for boost. Instead, I'll assign either the Output block's Level parameter or Amp block's Ch Vol parameter to a footswitch: Press AMP to jump to the Amp block's tonestack. Press and hold Knob 6 (Ch Vol). Helix jumps the Controller Assign page for that parameter. Press Knob 6 (Learn Controller) and then the desired footswitch. Turn Knobs 4 (Min Value) and 5 (Max Value) to set the amount of boost required. Press HOME when finished. You'll see the footswitch is now labeled "Ch Vol," but you can rename this "Boost" or "Louder" or "DI's My Hero" instead.

Not seeing it here. Either we fixed it before the build I'm on (post-1.06), or I'm doing something wrong. Either way, logged.

That's by design. FX Loop blocks' Mix parameters default to 100%, which yes, would mute any signal if a pedal's not connected. The Returns' Mix parameters default to 50%.

It's supposed to cover the Variax jack. Sometimes they come off in shipping. M'eh; it's not really necessary—toss it.

Most implementations of what people consider "tone matching" is pretty much just an IR.

FWIW, the ability to mute input blocks seems kinda scary—feels too easy for someone to inadvertently lose their signal. For the same reason, we omitted the ability to select "None" as an input for 1A or 1B. At least when assigning footswitches to processing blocks and/or parameters, the user is doing something deliberate. Doesn't solve the issue of more obvious path switching tho'. Still thinking... By the way, these are the types of conversations I like most. :)

Since they're input block types, that would be the same as toggling between Delay types (not that that wouldn't be cool). You can, however, assign an Output or Mixer block Level parameter to a footswitch. The easiest thing to do though is to start with one of the dual tone templates: 8 TEMPLATES > 02C TwoTones A-B (toggle with footswitch) or 02D TwoTones Blend (blend with expression pedal).

CS made a video.

Ideally, you should always try to get a great tone without Global EQ. It's really designed to compensate for different acoustic environments. Say you play a show in a club whose size, shape, and materials make all your presets sound boomy—Global EQ can be used to reduce some of that boominess without having to tweak individual presets. Pro Tip Shortcut: Press and hold BYPASS to turn Global EQ on and off. This way you can tell whether it's helping or hurting.

Hi hideout, I didn't see a specific proposal or method as much as a request to make one specific use case—footswitch assignment of path switching—more obvious. Regardless, I've set the idea back to "In Review" and will keep thinking about it. Thanks! Because Helix can do an insane amount of things, we felt it necessary to actively avoid chasing down specific protocols for each of the millions of things users might want to accomplish. To this end, we've distilled footswitch assignment of any signal path item down to one of two extremely fast methods: To assign a footswitch to block bypass in 3 seconds: Select the desired block. Touch and hold the desired footswitch until the dialog appears. Press Knob 6 (OK). To assign a footswitch to a parameter in 3 seconds (including the A/B split Route To parameter): Select the desired block. Press and hold the desired parameter's knob. Helix jumps to the Controller Assign page for that parameter. Press Knob 6 (Learn Controller) and press the desired footswitch. Adding a third top-level footswitch assignment protocol (actually it'd have to be a Path 1A/1B, 1A/2A, 1A/2B, 1B/2A, 1B/2B, 2A/2B switch assignment protocol, since Helix has up to four paths) doesn't feel like it fits within the current UI, as preset-level parameters don't really belong on the Home screen unless they're part of a block. It would also need to account for users who don't want a hard path switch—say they'd want to blend in a bit of Path B along with Path A. Perhaps I'm missing something simple that does fit within the current paradigm; we've redesigned parts of Helix a lot.

Yep, we review every submission. If you see a bunch of switches, it's because I just logged into IdeaScale. :)

Basically, I go through every day (or sometimes every two or three days) and change the status. "In Review" means it's been looked at and discussed; "Released" means its already implemented in some fashion. Any submission that's viable and doesn't already exist in our (ridiculously huge) model/feature backlog is added and prioritized. If a submission disappears, it may have simply been merged with a similar idea. There's nothing all that telling or special about IdeaScale. It's just there to help us validate features to the rest of the organization, and of course to help prioritize our backlog.

Yep. Make sure whatever you have Helix's XLR outputs plugged into has phantom power turned off.

I've been in MI from all sides—retail sales, support, and now design/product management. Yes, there are contracts between manufacturers and dealers, but I've never heard of any sort of dealer-benefiting fee or repercussion if a product doesn't ship on time. If that were so, a lot of MI companies would be out of business. FWIU, the dealers' payment terms typically don't begin until they receive product, so no harm, no foul.

1) Nope; that's what the XLRs are designed for. 2) Not the EXT AMP, which is a footswitch remote for switching your amp's channels. In this case, you'd just use the 1/4" outputs. 3) I certainly do, but quality is always subjective. 4) There are two gate models that can be placed anywhere in the signal path, plus each input block gets its own gate as well. 5) It should. OS X El Capitan is a mess tho.' 6) Yes. It automatically appears by default, dry with no processing, as Input 8. 7) Acoustic guitar, wet-dry-wet with a mic'ed amp, vocals, or any other mic'ed instrument. Helix can process multiple signals at once.

Gotcha. You can actually do this now, but it requires switching presets: Turn Global Settings > MIDI/Tempo > MIDI PC Send/Receive to "Off." On the Command Center page, set one of the Instant (lightning bolt) commands to the desired MIDI message. Save the preset. On the next preset, set the Instant command to the next desired MIDI message and save the preset. Repeat step 5 for all desired messages. Press and hold BANK UP and BANK DOWN until they read PRESET UP and PRESET DOWN. Now pressing PRESET UP will sequentially spit out each preset's Instant command. This probably isn't what you're looking for, but it works.

Cool; thanks, guys. Nothing I've had to worry about, but that makes sense.

Thanks, Martin—RME is indeed one of the best, compatibility-wise. I'll start digging.

Sometimes I forget that not everyone has read the 9,000+ threads over decades about preset switching gaps/spillover on this forum, Fractal's forum, Roland's forum, Kemper's forum, Atomic's forum, Zoom's forum, Korg/VOX's forum, Yamaha's forum, Kurzweil's forum, Waldorf's forum, Akai's forum, E-MU's forum, etc...

Potentially dumb question: I totally get placing Helix on a pedalboard when other pedals are involved or when it's part of a flight case, but what's up with the guys who buy pedalboards for only Helix? Just... Helix in Helix Backpack, and then a pedalboard to put it on. Is it to raise the angle of the switches? Ensure better airflow underneath? Protect the rubber feet? :huh:

We're testing a custom OS X driver as I type this. Comprehensive audio driver testing is incredibly involved, however. I'm not sure when it'll be ready for public consumption.

Line 6 has 2-channel interfaces that work great with El Cap; multichannel communication is apparently where the problem lies. Do you have any 8+ channel class-compliant (read: no custom driver necessary) interfaces that have been working flawlessly with El Cap from the get go? If so, we'd love to buy one and tear it apart. :)

Of course it's an issue—one that's been discussed ad nauseum—but it's an issue that plagues ALL modelers today, so what do you want me to say? "We're working on changing the laws of physics" "We're investing tens of billions on hundreds of new employees and our own custom chip fabrication plants in an attempt to somehow best the capabilities of Intel, AMD, TI, Motorola, and Analog Devices... to hopefully make a DSP chip capable of spillover" "We're gonna force you to upgrade to a $2000 HELIX SPILL with four SHARCs that adds literally nothing but spillover" "We're going to drop the sound quality of the models by half so you get spillover" Okay, that's funny. Cheers!

Unfortunately, no. Out of curiosity, what's the use case? Toggling two external devices/models?