Digital_Igloo

Well, one of the lead firmware engineers on Team Helix/HX is a grumpy sound guy (ran FOH for Animals as Leaders on their recent tour). He's not old tho'.

r/comedycemetary.

Download the latest version here and install it.

We're not diametrically opposed to making a standalone version of Helix Native. It's just a lot of work, and we have to pick our battles. Voting it up on IdeaScale is your best bet to get the proper eyes (and metrics) on it.

If 2.80 just so happens to drop next Wednesday or Thursday, I can assure you 100% the timing would just be a coincidence. We want this stupid thing out more than any of you and if anyone in marketing were to suggest we wait to align it with Summer NAMM, their heads would be bitten clean off. We're not above waiting for trade show announcements to release gear (or even other firmware updates, if they're close), but in 2.80's case, it will be out the very minute QA puts their stamp of approval on it. Man, now I hope it's not Wednesday, for this reason alone. :(

Will do. This is precisely why we're linking to the instructions this time instead of posting them everywhere—so we can make corrections if and when necessary. Updated now. Clearly, Helix Native 1.80 will include a gear icon and differently-labeled tabs, so I've kept the Restoring presets step the same. Thanks!

Puscifer's great! Maynard's 50th Birthday at the Greek (Puscifer, A Perfect Circle, and Failure) was the first date with my now wife.

Instructions have just been posted:

Half the team is already working on 2.90, so no. EDIT: No, putting them all on 2.80 would slow down its release.

When HX Edit 2.80 is available, it will also install the latest version of Line 6 Updater. You MUST update both BEFORE updating your Helix/HX firmware.

Akai, Alesis, ALTO, Headrush, M-Audio, and several other brands are all under the InMusic umbrella. Both the Alesis and Headrush speakers are rebranded ALTO speakers.

Whoever told you that 96kHz full throughput is necessary for serious audio production was lying to sell you something. Note that although HX Stomp processes audio at 48kHz, its A/D and D/A converters are 24-bit/192kHz. You are correct that the only downside to driver SRC is the latency incurred by the SRC itself (which should be less than 1ms). Higher sample rates are beneficial when tracking sound effects for pitching way down later or an extremely dynamic string quartet, but the majority of major label records are still tracked at 44.1 or 48 through 24-bit/96kHz or 24-bit/192kHz converters. It gets even trickier when companies tout "32-bit/96kHz" processing, which is marketing b@#$%^*, considering 32-bit floating point processing (which Helix/HX has as well!) is table stakes these days but totally overkill for audio throughput (especially considering their dynamic range is far inferior to ours), and 96kHz—or even oversampling to 192kHz—isn't nearly high enough for nailing the intricacies of certain distortion or amp models. So they're wasting a massive amount of DSP for the models that don't need it, and are woefully lacking for those that do.

Several times, but we don't track everyone down to make sure they pay attention.

You don't need a DI box with HX Stomp unless you need to lift the ground. Just a TRS > XLR M cable should do.

Made a History of Helix keynote presentation for launch day (June 11, 2015). Still have the video but alas, lost the keynote file. If Joe and the executive staff say it's okay, I might share some early designs if and when appropriate.

Assign it to one of the Instant commands (lightning bolt icons). Instant commands are sent with each preset or snapshot selection.

You're currently in Preset footswitch mode. Press MODE, and you'll see all 10 stomp switches.

Global Settings > Footswitches > Stomp Mode Switches: Set to "10 Switches."

I don't disagree, and I could probably insist to have the manual updated for every sub-rev, but believe it or not, the cost of translating them means we'd have fewer engineers to develop the updates themselves. Yamaha does everything by the book, and legally, we can't sell or distribute products to certain parts of the world without providing a manual in that language. In some cases, translation costs more than the revenue we get from selling to those speaking that language! It's not 100% up to me, but I'd much rather have more models and features than constant up-to-date documentation. You'd think they'd be mutually exclusive, but sadly, they're not. Translating a manual into all the languages we're required to support can cost many tens of thousands of dollars. Doing that three times a year for a dozen SKUs is impossibly expensive. "But I want it all!" Okay, but we'll have to charge more for the product. The same International laws don't apply to software, however, which is why you'll notice the embedded PDF manual for HX Edit and Helix Native gets updated every single rev. Also, I have been working on an exhaustive Knowledge Base manual for the new 2.80 stuff. We're considering pushing it live once it's done, even if 2.80 isn't quite ready. If people actually read it, we'll probably keep doing that for every point release. It's a lot easier than copying/pasting release notes onto a dozen forums (and then having to fix any mistakes in every one)...

If one's new to our schtick, is sensitive, and skews toward the never-worked-in-the-service-industry-the-customer-is-always-right-let-me-speak-to-a-manager-haircut type, I'll freely admit our transparency can be jarring. In truth, I've explained the hows and whys of announcing release dates dozens of times. (Spoiler alert: the companies who announce release dates are sitting on finished product for weeks or months to align with marketing deliverables. We don't know if 2.80's done until literally 10 minutes before it's released.) Typing the same thing every week is boring, and chasing down dissenters across 20 different websites/forums is even more boring, so I come up with dumber ways to convey the same message. Today, let's try screenplay form: Karen: Line 6's PR department doesn't communicate with us! Digital Igloo: Line 6 has no PR department. A few employees post because they want to. Karen: You're being rude for someone in Line 6's PR department! Digital Igloo: Line 6 has no PR department. A few employees post because they want to. Karen: Ha! That's JUST what someone from Line 6's PR department would say! Digital Igloo: <sigh...> Line 6 has no PR department. A few employees post because they want to. Bye —— off to TGP and the Facebook groups. 20 minutes later... Karen: Line 6's PR department doesn't communicate with us!

Not pointed at you specifically. More a preemptive strike against those who will inevitably cry "But I don't HAVE a Powercab Plus and don't CARE about QWERTY hotkeys! Why do l have to wait?!"

It's mainly three things: Helix Core—Mountains of code had to be replaced in Power Trio (Helix Floor, Rack, and LT) to bring them into parity with Helix Native, HX Effects, and HX Stomp. Some sections had to be coded from scratch. Although the code itself was all but finished at NAMM, I'm guessing close to a thousand bugs have been found since, some of which have taken a day or more to track down and find L6 LINK with Powercab Plus—Both Helix and Powercab Plus need to be updated at once, and there are major dependencies between the two HID Controller Conflicts—After 2.80, your Mac/PC will literally recognize Helix Floor/Rack/LT and HX Effects as a QWERTY keyboard, and driver conflicts surfaced. In fact, during the update process, your computer will ask "Huh? What is this thing?!" The update notes tell you to ignore this warning and close the dialog So why didn't we just release the models as 2.75 and release the features as 2.80 later? Two reasons: Releasing and then ramping up for another release slows things down considerably We're not your monkeys Settle down, Beavis.

If you've just updated Helix, make sure you let it rebuild your presets. If you don't, the gap will be significant. With 2.71, the gap between presets should be between 50 and 120ms, depending on the source and destination preset—far less than a quarter-second. It also helps to not look at the display, as redrawing the screen does sometimes take longer than a quarter-second and it may affect the perception of preset switching time. For all others, there's snapshots. Once you understand them, they're WAY faster and easier than managing a bunch of separate presets.

Here's the Logic/GarageBand template: FS2—Click on/off FS3—Cycle on/off FS4—Rewind (hold for fast rewind) FS5—Forward (hold for fast forward) FS8—Clear take and return to previous location (doesn't do anything in GarageBand) FS9—Stop > Return to Zero FS10—Play/Pause FS11—Record/Punch In/Out Place the locator at the point you want to record, press FS11, and start playing. Screw up? Press FS8 and Logic clears the take and returns to the original location. If you nail a take, press FS9 twice and listen back. Rinse, repeat. I think Logic has over a thousand (!) user-definable hotkeys now, so there's not much you can't do remotely from Helix.

The testers who know FL Studio and DP were gone the week we made templates. They're really easy to make on your own, especially from HX Edit. The hardest part was deciding which commands to include.