Digital_Igloo

Note that if Fractal let you add amp/cabs to both processors in an AxeFX II, you'd end up with four total blocks as well (two in the AX8). Amps eat up a ton of DSP. I should really write a Dynamic DSP Allocation blog with diagrams or something.

Yes. Yes.

Don't expect to process four band members through four amps and a bunch of effects. But you could conceivably process four band members with two amps and a bunch of effects. Or maybe three amps and a handful of effects, depending on the amps and effects. Helix is first and foremost a processor designed for a single musician; we've just made it easy to process additional signals if necessary, with the understanding that DSP resources must be shared.

Helix supports dynamic allocation, so it's highly dependent on the models you choose. Could be anywhere from 4 blocks (the most DSP-intensive Amp+Cabs) to 32 blocks (EQs, Volume Pedals, etc.).

Yes, but only at the location between paths.

1. Yes, but if KPA acts as your amp block, why split and merge at all? Unless you want to run KPA in one path and a Helix amp in the other, which totally works. 2. Sure. If you don't mind using analog cables, the KPA can exist anywhere on any path. If you insist on using S/PDIF cables, the KPA would have to be between Paths 1A/1B and 2A/2B, as non-Send/Return I/O only exists at Input and Output blocks.

If your overdrives respond to MIDI or CV/expression, yes.

Not anywhere in the signal chain, but S/PDIF I/O could be placed between paths. FX Loop blocks are currently only for the Send and Return jacks.

It really depends on the amp. I suspect providing all channels in a Mark V or Diezel VH4 might take longer than a month, but I'm not in sound design.

You're absolutely right. It's likely that one of our guys provided the wrong info, and I've been trying to track it down. The Sweetwater guys have been nothing but stellar, and it wasn't my intention to single them out—there's a metric ton of misinformation out there.

Helix hasn't been pushed back to mid-September. If we end up shipping in mid-September, that's still well within our initial projected release date of "by the end of summer." If you hear a release date from anyone but myself, Dale, Ben, or Sean, it's pure conjecture. The 1.00 manual's finished and now duplicated on a bunch of USB flash drives, but it's not up to me when we release a PDF to the public. I'm hoping the full color Cheat Sheet can go live this week.

All over the place. Most effects blocks have level parameters, as do the mixer and output blocks. Helix doesn't, however, have any sort of facility that "auto-levels" presets. Helix's numerous paths and outputs pretty much preclude this.

Phil nailed it. Line 6 goes through great lengths to make sure almost no new work is required with each update. We might tweak model defaults, but that shouldn't affect any user presets. If there's ever a case where something might change sonically, we'll try to be as transparent and detailed as possible, so there are no surprises and users can quickly update their setlists.

1. It's not a global looper, but if you select a preset where the looper... Has been added to the preset (duh) and assigned to a footswitch Is of the same type—mono or stereo Is on the same path—A or B ...loop recording/playback will be maintained. If all three conditions are not met, the loop will stop (but remains in memory for when you select a matching preset later). Most of Helix's stock presets will support looping across preset changes. The one thing you lose is a Pre/Post switch, as Helix's Looper block can be placed anywhere on the four stereo signal paths. You can also now assign controllers to Looper block parameters. 2. Yes. 3. Yes, there are a couple ways to accomplish this.

16 or 24-bit; 44.1kHz, 48kHz, 88.2kHz, or 96kHz.

List is missing: MODS: 60s Bias Trem Optical Trem Script Mod Phase

Agreed! MIDI clock is at the top of my personal list, but it's not up to me. Vote that sucker up...

Yep, even on its own path to its own output, so the FOH guy (or gal) can mix the looper independently.

No problem.

- Not currently. - Yes. PC messages are sent and received by default, but you can disable this. Certain incoming global CCs correspond to specific global functions, but non-global CCs can be used for other stuff (incoming controllers, remote messages, etc.).

Hey guys, We're currently working on a solution for the too-long preset switching time. Unfortunately, I don't have a date for when it might be released, but rest assured it's something we're taking very seriously.

When coupled with Helix Control, Helix Rack's firmware differences are so minimal, it's probably not even worth mentioning, but here they are anyway: Input List—Additional AES/EBU item Global Settings > Ins/Outs—Additional Clock Source parameter Footswitch Assign and Command Center menus—No "Relabel Footswitch" button appears at Knob 6 when EXP Toe Switch is selected (as Helix Control has no dedicated LCD for an expression pedal) A couple minor graphic asset swaps (product logo for splash screen, etc.)

Yes.

Helix Control isn't (currently) a controller for anything but Helix Rack. DC In and USB are only there for a bit of futureproofing, so we don't end up forcing a Helix Control MkII down everyone's throat in a year. Plus, if you want to run a reaaaaally long Cat5 cable, the DC In provides a bit of insurance. We don't know the max length just yet.

1. Connect your mixer's outputs to Helix's Return 1/2 jacks (or S/PDIF if it's a digital mixer). 2. For one of your four stereo paths, set its Input to Return 1/2 and its output to 1/4" (as per the last post, where your headphones are set to monitor/mirror the 1/4" outputs). The other three stereo paths can be for guitar, vocals, whatever. If you happen to have a knobby MIDI controller box, you could map the knobs to the various output levels and pans in a few seconds. Just note that other than direct monitoring of USB Input 1/2 and direct dry tracking to USB Output 7/8, all routing in Helix must be accomplished from the Home screen and its four Input and four Output blocks. We're not trying to build StageScape here; it's still designed to be an easy-to-grok guitar processor. Absolutely. Just set the paths to the same output.