Digital_Igloo

Sure, and that implementation wouldn't be overly complicated. It's all the other block syncing and MIDI channel WYSIWYG stuff from POD HD that doesn't really apply to Helix. We'd rather understand the problems and design elegant solutions to solve them than just check a bunch of boxes.

Ben via email (he said it's okay to quote him): By Ola’s verbal description, I get the impression that he turned off the power amp simulation for both the Fractal AX8 and the Helix. I downloaded his patch and indeed found this to be true. His reason for doing this was because he created an IR of his own cabinet using the tube power amp of the Mesa. While this will capture certain tonal aspects of the tube power amp, it certainly does not capture all of them. Plus, IRs don’t capture nonlinear elements. In short, both Helix and AX8 were essentially being played without the full, intended modeling process. Sure, tone is essentially subjective, metal music is based around preamp distortion, and I’ve heard of plenty of situations where metal dudes intentionally will use only the preamp versions of the models. Still, a very important part of our modeling process was essentially left out.​ In Ola's defense, this likely wasn't his direct intention, and the exercise was really fun and engaging regardless.

Thanks, guys. All good stuff. Regardless of what we do, it's never going to work like it did with HD500. And it shouldn't. Flexibility for flexibility's sake—at the expense of people actually using the feature—is the wrong path. That's why we spent so much time on snapshots; they needed to be dead easy and really fast to use, otherwise no one would use them and we did all that work for nothing. POD HD500 <—> DT implementation was INSANE to develop and debug. And almost no one uses it. Helix <—> DT deserves a serious rethink. The one feature that I'm not too keen on is automatic syncing of topology with the Helix amp model. I mean, which amp block gets synced? Helix has up to four and they can be freely added, moved, deleted, and swapped. (HD had two static amp block locations.) Plus, aside from tempo, there are decidedly no preset-level parameters that aren't part of an existing block; POD's Setup menu behavior (where some parameters are global and others—like DT routing and MIDI channel assignment—are per preset) is off the table. Personally, the most transparent and elegant solution is probably similar to how we accomplish remote Variax parameters, except from the Output block instead of the Input block. L6 LINK isn't dead either; we'd like to add it to future products. It's just an expensive protocol—both parts cost-wise and development time-wise—so we have to pick our battles carefully.

Ha, jokes on you! I have no hair. :(

Deeper DT integration is still toward the top of our list, but L6 LINK implementation is tricky—it was literally months of work in HD500 and almost no one took advantage of more than 10% of it. I think the number of users who regularly daisy-chained more than one DT over L6 LINK was in the single digits. It might also help if DT users specify what they'd like to accomplish via L6 LINK. Helix and POD HD have completely different architectures, and some of HD's L6 LINK implementation doesn't apply in Helix-land, like linking model bypass to DT channel selection, WYSIWYG control on/off via MIDI channels, tapping off specific amp blocks mid-path, and other stuff. I have a Helix <—> DT50/25 spec already written; it'd be nice to know if we're on the right track. Feature priority is based largely on how big a demand there is, how many users it benefits, how much buzz it'd generate, and most importantly, how much development work it'd be (that is, how many other features have to be pushed down the list to accommodate it). That said, at no point have we ever thought "yeah, we'll likely never get to full DT support." It's always been in the gargantuan Wish List.

Regrettably, my humor is almost entirely based in sarcasm and snark.

I love this thread. :wub:

I own a circa-2003 LA-2A, we modeled a vintage LA-2A, and I'm intimately familiar with UA's LA-2A plugin emulation. I'd say Helix's model is right up there with all of 'em; otherwise, I wouldn't have signed off on it.

Because this isn't a LAN party; it's 2.4GHz wireless. The rules of wireless are radically different from tethered solutions, and are subject to countless telecommunication laws and restrictions that change from country to country. Our radios are single channel, 24-bit/48kHz audio. For two channels, you can't just say "Oh, make it 96kHz and bit split at the other end," as the radio would need to shuttle literally twice the amount of data at once and use twice the bandwidth—that is, two channels worth. You could admittedly run two channels at 24kHz, but we're never going to do that because it sounds like crap. And don't forget the back channel that goes in the opposite direction. You need receiver hardware at the transmitter and transmitter hardware at the receiver, both with range parity.

One would make music that doesn't sound like the same ol' blues/classic rock that'll relegate the guitar to "dad music" and eventual insignificance. ;)

What a killer video; thanks! Added a bunch of these to the gargantuan backlog. That Subdecay Harmonic Antagonizer is massive-sounding.

Helix Control currently only supports Helix Rack. The rear-panel USB port is only there for future-proofing.

The DAW can trigger Helix and Helix's switches can also control your DAW's transport simultaneously. You can even have any tracks from your DAW routed to a specific set of outputs.

Sierra's been behaving very well here in the office.

Select any processing block, press ACTION, and then move the joystick down. It'll move that block to Path B; a Split block is created directly before it and a Merge block is added to the end. Select the Merge block, press ACTION, and move the joystick left to move it before the Looper block.

Definitely MIDIpants®.

You don't have to do much: Add a Pitch/Synth > Pitch Wham block. Adding a Pitch Wham block automatically assigns its Position parameter to EXP 1 and its bypass to the toe switch. If the pedal is currently set to EXP 2, press the hidden toe switch to switch it to EXP 1 and there's your Whammy.

Also note that you don't have to use an entire DSP for your Moog. Helix's 4 signal paths can be applied to whatever you want. 8 TEMPLATES > 04B Gtr+Vox+Bas+Keys has an entire band running through a single Helix. If you want, Paths 1A, 1B, and 2A could be dedicated for your guitar, and 2B for the Moog. My band processes 6 sources (2x guitars, bass, vocal sends, keys, and tracks) with two Helix Racks. Admittedly, it's more like 4 or 5 at a time, but still...

Oh, there's always hope. ;)

The description of MIMIQ's algorithm sounds remarkably similar to the doubler effect in Vetta.

For guys who prefer the whole pedalboard/switcher paradigm to dozens of radically different presets, snapshots let you create a large switching matrix for all blocks, plus up to 64 parameters can be set to any value—per snapshot—and the whole shebang is recalled instantly. It's a different way of working.

It sets that output to unity gain (0.0dB).

The looper can indeed continue playing across presets. From page 12 of the Helix Owner's Manual: IMPORTANT! You may change presets while looping, but loop playback will stop unless the preset you select includes the same type of looper block (mono or stereo) on the same path (1 or 2) and is assigned to a footswitch.

I don't believe Clear All Blocks resets your Input/Output blocks, aside from removing any 1B or 2B inputs/outputs. Also, the Command Center is still active, so you'd need to clear all the commands there as well. Yes, copying/pasting a blank preset over an existing one is the fastest/easiest way to completely clear a preset.

Copy/paste does not currently work across snapshots, as pasting a block with many controller assignments could clip the 64 controller limit in another preset. There are all sorts of things we could script as a workaround, but for now, there are bigger fish to fry. If there's a particular way you'd like copy/paste to work with regard to snapshots, IdeaScale is the best place to submit it. :)