MusicLaw

Not sure if I'm hearing the same or similar characteristics as you are depicting. Having just installed 2.20 yesterday afternoon, upon exploring the Setlist 1 and 2 Factory Presets, there was a lot of granular noise from the Vintage Delay in several of the presets. In one Preset having the Industrial Delay (I don't recollect which one) the extent of the noise was absurd. I rarely use the Factory Presets, vastly preferring to cook my own, so these may have always been this way....

I'm not sure of the Surface Pro 4's screen resolution. Nonetheless, when the Updater's display window appeared on the screen (using Chrome Browser) the size of that window was small and fixed -- no corner drag & drop to resize nor fullscreen button to click. So, I launched Chrome Browser on my Samsung Android Smartphone (Galaxy S4 Active) and browsed to the exact same Release Notes document on Line 6's website download area. Zoomed in with an easy jesutre and the document was larger and far more legible to easily read. ALthough the Surface Pro 4 is a beauty of a machine, it was borrowed. I have been spoiled with the 2560x1600 resolution of my Samsung TabPro 12.2" Android Tablet. It is a shame Line 6 continues to ignore the Android market for the Helix Updater and Helix Editor Apps. The filesize and complexity of installing the firmware on the Helix is not beyond the capabilities of the Android devices!

Nice!

AA5ZX de AA6A

Installed 2.20 fw, earlier today, to Helix Floor, going directly from 2.10. It was quick and uneventful. On the borrowed Microsoft Surface Pro 4 running the latest Win10, Helix Updater was nearly microscopic! The Surface Pro 4 belongs to a friend, so I was not about to edit the Registry to attempt the Manifest file workaround.

Unless you are using air compression hoses for your cables, one foot of electrical cable does not impart any noticable lethargy! Electricity moves at the speed of light: 186,000 miles per Second. Sound moves at 767 miles per Hour; a crawl by comparison.

Emphasis added. Great tip to wear rather than hand carry the Helix backpack on board.

I've gotten really good sounding results using Shure SE530 IEMs with the Helix. The character of the sound translates quite well when monitoring via two Yamaha DXR10, or two JBL LSR308, regardless if run as Stereo or Mono. I do not have much experience with the Alto's aside from demoing them at several stores, but none of those sessions were with the Helix.

This scenario strikes me as one of those situation where the efforts to change the firmware may not justify the effort of allocated programming resources. Theoretically, Helix's firmware, should be able to truly disable an FX Block's impact affecting a A/D Noise Floor increase -- when the FX Block is the Bypassed state. This would also necessitate that the firmware anticipate that at any moment the Block's Bypassed state could be defeated, thus requiring the A/D to be immediately ready and able to perform. The trade-off may simply not justify the result of improving the noise floor, since when a signal is present the noise floor is not perceived.

Jason, Updates to HelixHelp.com look fantastic! Keep up the great work!! If riffyrafemetal is up for combining efforts, HelixHelp.com would be even more amazing as the pinacle of well compiled Helix information resources.

Awesome followup! Line 6's Customer Service and Tech Support are outstanding!

They will remain on the same frequency channel. The Channel Scanning process only occurs when the Transmitter is reseated back into the Base unit with the power on.

Get yourself a small bottle of TriFlow. It comes with a thin diameter plastic applicator tube that fits into the tip of the bottle. TriFlow will not attract any grime, grit, dust, etc. One drop works wonders!

Aside from the excellent effort presenting Helix information on HelixHelp.com, Line 6's Release Notes (accompanying each of the several firmware releases: 2.01, 2.10, 2.11, 2.12 and 2.20) following the July release of Helix 2.0 User Guide (Rev D) PDF comprise the only official contents to be found. The problem is that shortly after each is succeded by a newer release, the predecessor Release Notes on these Helix Support Forums of Line 6's website are removed from the accumulating thread: Latest Helix Firmware, thus making it quite frustrating to find them once again. If you have the time and inclination, following the threads here and on TheGearPage.net are most informative, and contain replies from Line 6 guys, beta testers, highly experienced users, as well as refreshing posts from new users with fresh eyes. When firmware 3.0 arrives that's when Line 6 will present a new Helix 3.0 User Manual PDF. Until then, about the best we can ask for is for Line 6 to at least enable the Search Requests: "Helix Release Notes" and "Release Notes Helix" on the Line 6 site, resolve to the earlier Release Notes. [Addendum: The Downloads area of the Line 6, when the first two dropdowns are set to Helix and your particular OS in the third dropdown, the Release Notes are found. However, even the current fw 2.20 Release Notes show a slightly different draft that merely states: Support for 22 new 2.20 models without listing the 22 new amps and FX models. It would be great if the info accumulated in (at least) one place without deletions, sections removed, etc. Bold content above was also added.]

Now if only Line 6 would offer a Buy One Get One at Half Price G10 bundle, I could run Stereo wirelessly. ;)

A wise man said....

With Helix Native and a newly revised Helix Editor slated for release this Spring, and having seen DI's posts that Ben and others at Line 6 have already been working on fw 2.30 for a few weeks, it is entirely likely that by Spring's end (or when Native and new Editor are released), Helix may have received, at least, one (or several) additional firmware update(s). Helix's firmware release history shows that 2.00 (7/6/16) was promptly followed by fix 2.01 (7/20/16), and 2.11 (12/5/16) promptly followed 2.10 (11/22/16). It will be interesting to see what lies ahead in the next several few weeks.... I certainly appreciate what 2.20 has delivered for Bass and Variax players (I have neither), however, I am far more interested in seeing how Helix evolves with the forthcoming new Editor and Helix Native.

I thought I read that Helix (Editor or the Helix itself) would take care of the sampling resolution conversion, if necessary, upon import? Or, might that be solely for a one IR at-a-time import basis; not for a batch operation?

Upvoted.

I did just earlier today find a Known Issue (from Dec 2015) in the Helix Knowledgebase regarding an FX Loop noise floor increase in the Helix. See: http://line6.com/support/page/kb/_/effects-controllers/helix/helix-sendsreturns-and-the-signal-noise-floor-r788 Now, apparently with fw 2.20 there is a Known Issue, of a stepped volume when adjusting the main Volume Knob.

It works great! Use the G10 Transmitter with Helix's 1/4" L/Mono Main Out, or, one of Helix's 1/4" FX Sends. Configure the Helix Global I/O and, Bypass, Enable, or Remove Helix's Amp and Cab Blocks according to where you plan to connect the G10's Receiver. The G10 Receiver works into an Amp's Main Instrument In, an Amp's FX Return, or into an Amp's Aux In (with appropriate adapter).

Recheck these to be certain that the levels are adequately set (as they revert to factory defaults when reinstalling firmware): Helix Global Settings > Mic Input and Helix Signal Path > Mic Input Block Settings and Helix Signal Path > Output Block Settings If still no good, get back in touch with your vendor to see if you can exchange the unit for a new one. Otherwise, submit a Support Ticket with Line 6 to get them to service or replace the unit ASAP.

4:55AM is way too early for Pacific DST!

This is far too commonly misunderstood, unknown or overlooked. It cannot be emphasized enough. {Emphasis Added}

Friday is always a good reason to Party! Even more so, if FW 2.20 is out by then. For me, the real celebration will start when the newly revised Helix Editor joins the party....