Digital_Igloo

Interesting... We do have a template preset to use Helix as a mixer, with pre-fader sends, post-fader sends, and per-channel compression and EQ, but you're right—all blocks are currently per-preset. 08 TEMPLATES > 05B Stereo Mixer

DSP headroom should have zero impact on models' sound quality.

If you're using 110-Ohm AES/EBU cables with two L3ts, it's better to select Output > Multi blocks, which include L6 LINK. If two L3ts are daisy-chained via L6 LINK, they should automatically become stereo (even if their displays say 1 and 2, I believe). From one of the Output blocks, turn Knob 1 (Pan) hard left or right and you should hear that reflected correctly between your speakers.

Define "occasionally." I have over 1200 posts on this forum and over 1600 on TGP (with over 4600 "likes")—most of those are since last June. If you think the creators of Helix aren't engaging their users, you haven't been paying attention.

Nope. Growing. We have big plans and would love more product gurus and rock star engineers to help realize them.

Assign the same CC# to all four Output Blocks' Level parameters? At that point, it'd effectively do the same thing. If you also needed individual control of each path, you could always add a Gain block directly to the left of each Output block and assign separate CC#s.

Attention armchair product managers: Think you can do better? We're hiring.

Not sure if this will fix the USB port driver issue that plagues mid-2012 MacBook Pros and iMacs. Guess we'll see in.. ...2 hours?! Man, I need faster internet.

I like the clock idea—even if it doesn't end up in Helix, it very well could spark an idea that does. Ignore the haters, Shawn. B)

It should, yes. The only limitation is 64 controller assignments per preset.

No. Steinberg, Nexo, and Bösendorfer, while also wholly-owned subsidiaries, are operated completely independently, and are also not Yamaha.

The Logidy EPSi is really, really cool. It supports convolution reverbs (IRs) up to 60,000 samples in length.

You don't mention which paths are being used for realtime processing (if any), but the following lets you use Paths 1A and 1B for amps and effects while using 2A, 2B, and the USB In 1/2 pass-through for routing backing tracks: Set Global Settings > Ins/Outs > USB In 1/2 Destination to 1/4". This is your secret "pass-through" routing that doesn't require a path. In Ableton, pan your click hard left and your bass hard right. The Click will now come from 1/4" Left and the bass will come from 1/4" Right Select 8 TEMPLATES > 04B Gtr+Vox+Bas+Keys. It has four stereo parallel paths—1A, 1B, 2A, and 2B. Set the paths' Input and Output blocks as follows: ​Path 1A—Input: Multi, Output: XLR (amps and effects) Path 1B—If you want to use Path 1B for parallel processing, move the dark circular Split and Merge blocks up to connect 1A and 1B back together. If you don't need parallel processing, remove all blocks on 1B and the whole path'll disappear. Path 2A—Input: USB 3/4, Output: Send 1/2 (Guitars/production) Path 2B—Input: USB 5/6, Output: Send 3/4 (BG vocals) Remove unneeded blocks from the template preset, but note that at least one block must exist on Path 2B; otherwise, it disappears ​OPTIONAL: Set Global Settings > Ins/Outs > Headphones Monitor to hear what's coming from either the 1/4" Outputs, XLR Outputs, or both (Multi). EDIT: This was my favorite question yet, by the way. B)

Helix's presets respond to boring ol' PC messages. If you also need to switch setlists, send a CC32 message (BANK LSB) before the PC message with value: 0 for Setlist 1 (FACTORY), 1 for Setlist 2, 2 for Setlist 3, etc. Otherwise, a PC message by itself keeps Helix in the same setlist. To quick assign a parameter to a specific CC: Press and hold the knob for the parameter you want to control. Helix jumps to the Controller Assign page for that parameter. Press Knob 6 (Learn Controller) and then send Helix the desired CC from Ableton. Press HOME to exit. You'll see the value's turned white and in brackets, indicating it's not controlled from an external source. You can also manually assign CCs: Press and hold the knob for the parameter you want to control. Helix jumps to the Controller Assign page for that parameter. Turn Knob 2 (Controller) to select "MIDI CC." Knob 3 appears as "CC#." Turn Knob 3 (CC#) to the desired CC type. OPTIONAL: Turn Knob 4 (Min Value) and Knob 5 (Max Value) to restrict the value range. This is more important when assigning Helix parameters to external real-time knobs and sliders; they might just confuse things when sending MIDI track automation. Press HOME to exit. You'll see the value's turned white and in brackets, indicating it's controlled from an external source. By default, Helix responds to MIDI Ch. 1, but you can change this on the Global Settings > MIDI/Tempo page. For more information, start with page 48 of the Owner's Manual.

Our OWN expression pedal is the Line 6 EX-1. It's obviously fully supported.

You can have up to 64 controller assignments per preset, but each footswitch is limited to eight assignments (block on/off, parameter adjust, and/or Command Center message). So eight footswitches could each have 8 assignments, but then you'd run out. Or ten footswitches with six assignments, EXP 1/2/3 with one each, and the 64th could be via MIDI or something.

And they all sound different, depending on what you're trying to accomplish. Boosting the amp's channel volume increases level into any downstream pedals, which drives them a bit differently than boosting the Output block's level parameter. Also note you can assign up to eight parameters (or other things) per footswitch. So your "BOOST" switch could increase the Ch Vol by 0.5db, increase an EQ's Mid Gain by 1.2dB, increase the Gain on the Klon by 2.1, and five other things. And remember, to tweak any of those boosts, all you have to do is touch the switch repeatedly until the assignment appears on the main LCD.

There are piano board resonance and damper pedal IRs out there, but impulses can't really make your guitar sound like a piano or anything.

Many years ago, before Helix was my baby, I suggested "Split Path" and "Merge Path" buttons be added to what became the Action Panel, but I was outvoted. The reasons I'm not too keen on adding Splits to the Model list: Splits and Merges aren't really models (neither are FX Loops and Volume Pedals, but whatever) We already have an existing implementation (whether it's the right one or not is up for debate) and changing things now would confuse more than it'd help Navigating the model list is much slower than dropping a block down Fundamental changes to the path architecture would have to take place Fundamental changes to the DSP filter would have to take place, and might break presets right on the cusp—currently, everything in the model list takes up DSP. The user should never be in a position where they cannot split or merge a signal because of DSP Of course, this doesn't mean that the submission is invalid. The underlying issue is obvious—for people who haven't read the manual, creating splits and merges isn't as clear as it could be. :)

All right, we'll keep digging.

So in addition to CC Toggle and CV Toggle, you're looking at a new Bank/Prog toggle message? Just downloaded the JVM410H manual; I can see how that might be helpful. Cheers!

Did you guys reset your global settings after the last update? Dom saw this too, but it went away after resetting everything. I'm trying to make it happen, but it's working as expected here.

The sentiment is appreciated, but if spillover is really important to someone, they shouldn't stop bugging us about it. :) However, they should understand that perfect preset spillover—that is, two full presets worth of blocks are active simultaneously during preset changing—ain't gonna happen. That requires twice the DSP and twice the DSP would give us soooo many more important things than spillover (like better modeling!), I just don't see that ever happening in any hardware product outside of DigiTech's GSP1101. But other features that might approximate spillover? That's totally within the realm of possibility. We're just getting started.

It was something we wanted for 1.0, but it just wasn't in the cards. It's toward the top of my personal wish list, as the flexibility it would afford Variax owners is pretty mind-boggling... Plus, the fact that controllers can be assigned to all Home page parameters except Variax parameters is something that totally gives me facial tics.

It wouldn't have to be a dedicated Variax block—the easiest implementation would be to allow for controller assignments to Variax parameters already found in the Input > Multi and Input > Variax blocks. Unfortunately, as Variax parameters can be both global and per preset, and controller assignments only work with per-preset Home screen parameters, it doesn't work right now. I agree that it'd be very cool, although an even crazier thing would be to assign a single momentary footswitch to completely retune each string independently. Instant B-Bender, Drop-D, or DADGAD for only a few notes!