Digital_Igloo

Yes, yes, and yes. We designed Helix to seamlessly fit into your workflow, not shoehorn you into its workflow.

The impedance parameter is really key here. We'll place the real drive into the effects loop and assign a footswitch to toggle between our model and the real pedal. We stop tweaking the model when our own golden ears (including those who build boutique drive pedals) can't tell when we switch. In one case, the signal alllllll but disappeared when our polarity flipped model was mixed with the real pedal. If the physical pedals are "far superior", something's amiss.

We don't typically rev manuals for relatively minor point releases, as it's a ton of work and translations are really expensive. The release notes should give you all you need to know.

Don't forget the Depth parameter on page 3. It makes a HUGE difference.

Admittedly, I had never played a real Archon before we got one in to model. It's an awesome-sounding, really unique amp, and pretty tricky to model properly. What's nutty is that the Lead channel can be bröötül but its Clean channel can be pristine enough for smooth jazz. Didn't expect to love that amp, but it might be my favorite now.

I consider it minor because most of the new features deal with the Bypass Assign page. That thing needed a rethink anyway.

Wait ten minutes. They'll yet again complain about how we don't listen. ;)

More below (TGP posts are limited to 1000 characters): Improvements/Changes Added a Headroom parameter to Delay > Vintage Digital Snapshots now recall the currently active expression controller (EXP 1 or EXP 2) for the built-in treadle Split > Y can now be bypassed; when bypassed, the block sends both left and right signals to both paths equally (like the old Split Y block) Looper Mode switch LEDs now display a dim/lit state to better reflect their current states Non-selected Pedal Edit Mode parameter switch LEDs now display a dim state Added forward slash [/] to list of characters for naming presets, setlists, snapshots, and Stomp mode custom labels Bypass Assign > Knob 1 (Footswitch) has been relabeled “Switch†to better reflect all values Tap Tempo no longer affects a preset’s dirty state (“E†icon) Minor updates to the Factory Preset bundle If a user fails to read and follow the update instructions, Helix will cause their car radio to play only polka death metal every Thursday from 1-3pm PST Bug Fixes Errant graphics could appear when selecting an IR block from the Controller Assign page - FIXED When assigning a command to EXP 3 on the Command Center page, the turquoise indicator could occasional fail to appear - FIXED When sending/receiving Looper MIDI CC messages through external devices, MIDI feedback could occur - FIXED General stability improvements Other minor bug fixes and optimizations Known Issues In very rare cases, corrupted presets containing a Volume/Pan > Volume Pedal block can cause volume to drop to 0%. In such cases, completely clear the Volume Pedal block and add again. If the same preset exhibits this behavior again, please contact Line 6 Customer Service and be ready to email us the raw preset so we can analyze it Bypass Assign > Wait defaults to 300ms from the hardware and 100ms when selected within the Helix edit application Copying and pasting a block assigned to auto enable/bypass from the Helix editor may result in a “Cannot paste block†error message while the Helix hardware confirms the block was indeed pasted correctly. Workaround: Save the preset to re-sync the application

Updated thread to 2.10 (released November 22, 2016).

We usually don't know until a few hours in advance!

Great! Sometimes all it takes is reordering a few chords.

Just know that if you use any incarnation of AC/DC's "Back In Black"—whether it's a karaoke or nose-flute version—you're still on the hook for royalties. Always check with the venue to see if they pay PRO (BMI and ASCAP in the US) dues. The OP seemed to ask for a soundalike, which I used to crank out all day, every day. Not for $50 tho! :wacko:

Not if your USB feed is 1/2, which it should be.

This is an interesting business model: Delay firmware updates until people sell off their Helices, then release the update, get a few people to repurchase a new Helix at full price because of the new models and features, rinse and repeat. Eventually, some people will spend $5000 on their Helix, just from selling and re-buying it. Hmmm... :P Forget the effort in developing new models and features for a second—testing new models and features is a long, arduous process. And we can't just test the new stuff; the whole system needs an über-detailed, soup-to-nuts analysis, both standalone and with the editor on every supported Mac/Windows OS. Any tiny change should and does require weeks of testing. That said, 2.10 isn't gonna be huge like 2.00, but it's still pretty fun. TL;DR: We give people bigger but less-frequent updates because... testing.

Sure! :) It was actually because Yamaha expression pedals are inverted from ours and Mission's.

Depending on the original amp's complexity, quirks, and nuances, HX component-level modeling takes anywhere from three to eight weeks per channel. If we were to speed up that process—or take shortcuts—the amps wouldn't sound and behave as close to the real thing as they do. Quality over quantity is the mantra. It's not unlike CGI. Crossing the uncanny valley takes a ton of expertise and a lot of time.

I like the thinking. Haven't tried it myself, but with a short MIDI cable, you might be able to send an Instant MIDI CC message (with different values per snapshot) back into itself to approximate this. Not in the office right now to confirm (not even on the hemisphere). We have other plans for repeated presses of the same snapshot switch, but that doesn't mean they're set in stone.

On the Rename Snapshot screen, press Knob 4 (Remove). This will restore the name to "Snapshot [X]."

I listen to Helix most often through ADAM P22A studio monitors.

Nope; you'll be able to go straight to 2.10 from 2.00.

Apparently my posts were clear as mud. Sorry 'bout that; let's try bullets: We absolutely can improve Helix <—> DT integration and have several ideas mapped out already (actually, they were largely mapped out before Helix was even announced) More robust Helix <—> DT integration continues to be on our gargantuan list of things to do; its priority is largely determined by user demand More robust Helix <—> DT integration, if or when implemented, will not be like POD HD <—> DT integration, because POD HD <—> DT integration: doesn't apply to Helix's architecture takes forever to implement and debug, and diverts resources from features with bigger ROI is needlessly complicated for our users includes a ton of features for daisy-chaining more than one DT—and almost no one daisy-chained more than one DT. There may be only one or two people worldwide who daisy-chained more than two Believe me, any DT integration we provide wouldn't be to push DT sales, as all DT50 SKUs have been discontinued. We'd do it because X number of users ask for it. We move features and models up and down the priority backlog every day.

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. :(