Digital_Igloo

There's currently no EHX freeze model, but you could approximate one with delay feedback controllers in five seconds. Amp models aren't like samples—phase relationships don't really apply here. There's no delay compensation, just like real digital pedals, but after making a ton of Helix presets, I've not noticed any phase garbage. The Merge > Mixer block has a Path B polarity switch if you run into issues. The 5150 is indeed the block logo version, and yes, just like the real amp, it sounds like a can of bees. All 5150s sound like a can of bees to me. But there are a dozen ways to make it sound much less like a can of bees, just like engineers do in the studio when they track a real 5150 with a real mic on a real cabinet. Lower the cab's high cut filter—done. There's a larger gap between the treadle and the TAP switch than in previous products. There's a possibility that TAP and MODE could be switched to the left side, but that would preclude 10-stomp switch mode, so it's not a very elegant solution. Size eleven here; I would never be caught dead wearing cowboy boots, as songs with progressions that end on the tonic are like nails on a chalkboard. :P EDIT: Turns out there is indeed delay compensation, but it's only applied per path; that is, if you're placing amps on both paths 1 and 2, compensation may not always be applied correctly. Luckily, each path can normally accommodate two amps (as long as you place more DSP-intensive effects on the other path).

Anyone here in the Phily area this weekend? Helix will be at the Guitar and Bass Expo this Saturday (Aug 22nd) in Wyomissing, PA from 10am-6pm.

Not anywhere in the chain, but at the beginning (Input block) or end (Output block) of any chain. Sends and Returns are the only I/O accessible mid-chain, although they're also available as Input and/or Output blocks.

Already in there. :)

Currently, any parameter found on the Home screen (input, amp, effects, split, merge, output) can be assigned to a controller/footswitch except for Input > Variax parameters. That is, a switch cannot, for example, change Variax models or retune strings within a preset; you can, however, store and recall these settings per preset.

Yes. The controller assign limitations are: No Input > Variax parameter assignment Eight total assignments per switch 64 total assignments per preset

The FAQ is still correct.

Nothing's changed. We're still on schedule to ship by the end of summer.

Amp models don't have channels per sé; each "channel" would be a separate amp model. You could, however, assign a footswitch to control user min/max values of up to eight settings within that amp. Or you could assign a footswitch to switch between Path A (amp 1) and B (amp 2).

Nope. If the date changes from what the FAQ's said since June 11th, I'll scream it from the rooftops.

Science vs. Religion debates? C'mon, guys. Don't make me sic Tony on y'all... <_<

As with all modelers, if you change banks (presets), you won't hear effects from the previous preset... unless, of course, they exist in the current preset as well. Any MIDI/CV/Amp Control commands are tied to the preset. However, you can copy and paste your entire Command Center (MIDI/CV/Amp Control) layout to other presets. In Stomp footswitch mode, you can have up to 10 separate footswitches, all of which can be assigned to up to eight of any combination of block bypass/enable, controllers, MIDI messages, CV messages, or Amp Control messages. All within a single preset.

Depends on the blocks' states of the target preset.

D'oh! Yeah, I read the manual, which has a typo. Yeah, 10 kOhm.

The Aux In is 10 Ohm 10 kOhm. It's designed for very hot pickups, or even a line-level signal. If you're looking for additional instrument inputs, the Returns are your best bet—they can be set to instrument level and then selected as one of your four paths' input blocks. EDIT: Since Helix's guitar input has 123dB of dynamic range, and the HX audio engine is 32-bit floating point, there's no issue with running a Volume/Pan > Gain block right after the Input block to control input volume per preset.

What's baffling is how "n% improvement" could somehow be ascertained by the audio in a YouTube video.

Don't tell the team downstairs, but I love me some Bill Hicks. R.I.P. We kinda had to. Helix was going to be shown at GearFest, and there was no backing out. We would've loved to have announced and shipped Helix on the same day, but that almost never happens. How many boxes in this industry are announced 9-18 months before finally showing up in stores (to crickets, because no one cares anymore by then)? A lot. I don't think any of us (product management, engineering, marketing, executive staff, Yamaha) expected a can of worms so big. It's been pretty overwhelming, to be honest. In a good way.

We have only one development team guy and he has to do all that by himself?! :blink: Good thing we have a :ph34r:.

Imagine the insane expectations had we not disseminated information: "OMG! Did you see this thing? I heard from a guy who heard from a guy that it's got every Kemper feature, every Roland GT-100 feature, every Digitech GSP-1101 feature, every AxeFX II XL+ and AX-8 feature, every Eventide H8000 feature, is powered by eight new quantum DSP chips, has zero latency, runs a special version of ProTools, AND it's only $499!" It's really important to curb enthusiasm where appropriate, lest the natives procure our collective heads upon release.

Switching noises should be mitigated in the next release. Delay artifacts are due to a lack of Global tempo parameter, which we eventually hope to solve as well, but preset switching time is our top priority right now (and it's already WAY faster in the latest internal beta build). In the meantime, if two presets are set to the same tempo, any delay artifacts should be minimized. Thanks everyone for your patience.

If you're on a Mac, you can build an aggregate audio device with all of your audio interfaces. That's what I'm currently doing with an Apogee Symphony I/O (16 ins, 16 outs), Helix (8 ins, 8 outs), and Logic.

Forced rankings might have an affect on what models we might do in the future, but it's not like "oh, feature [X] has 36 votes after three months and feature [Y] has 34 votes after three months, so we better do feature [X]." We consider each and every IdeaScale submission.

Please please please add this to IdeaScale so I can vote it up. :wub:

Ben and I are both huge shoegaze fans, so expect some love. We were even (half) joking about modeling the Alesis Quadraverb because it's so ubiquitous on those early 90s records. My favorite band in the world is Curve and I'm currently wearing a Sigur Rós t-shirt. Swervedriver/Ride/J&MC/Chapterhouse/CatherineWheel/Low/FlyingSaucerAttack/Alison'sHalo/Halfstring/AmusementParksOnFire/Autolux/Loveliescrushing

Just checked: Least DSP-intensive Delay—Mono > Simple Delay: 32 delays in a row with 59% of DSP remaining Most DSP-intensive Delay—Stereo > Multitap 6: 10 delays in a row with 1% of DSP remaining So yeah, huge disparity between models, which is why no one can say "you'll get [X] number of blocks."