MusicLaw

Also see: HelixHelp.com > Amps for more info on the Amp models.

Your Preset may be corrupted. After you updated to the latest firmware version, be sure to perform the Rebuild Preset Procedure by Holding FS 9&10 while powering up the Helix (as described in the firmware installation instructions). If the problem persists after you have reloaded your pre-existing Preset, try creating an entirely new Preset with the parameters you used in your previous Preset. If still no good, get the problematic Preset to Line 6 by submitting a Support Ticket (if you have not already done so).

The closest approximation of an "installation guide" is the screen of instructions (with Red and UPPERCASE emphasis) you viewed on Line 6's sofware download website page. This entire updating process has proven to be a stumbling block/hurdle for many Helix owners. Line 6 is well aware of these frustrations, and will be revising the entire process in the months ahead. It not known how soon this will be rolled out, however, it is likely that this will NOT be resolved until AFTER firmware version 2.3, (or possibly after firmware 3.0) are released. Line 6 has stated that it should be later this year. Thus, if you can get your Helix updated to the current firmware 2.21, you should be good to go, and not likely have to redo the process for (perhaps) several months.

Great Rig Rundown Video praising the Helix! Love that Speaker Box Road Case PS uses! And, his revised four finger string strike method! Been doing that for years. The Doobie Brothers did an awesome set at last weekend's Classic West show at Dodger Stadium!

@guitarnstuff, if you have already done the Rebuild Presets routine for the latest firmware (Press and Hold FS9&10 while powering on), the corruption, if any, may have been "baked" into the offending Presets they were reinstalled following each of the earlier fw releases. Either way, my guess is that Line 6 Tech Support may appreciate a look at those problematic Preset files, regardelss, if you still have the pre-rebuild routine versions, as well as the subsequent post rebuilt files.

It has no degrading affect to the charge time. I have not had my G10T at minimal battery level for months, so I can't give you a time spec for a full charge using the accessory cable. On the other hand, when I'm done using my G10T after several days of use and I charge it with the accessory cable, it is fully charged in about 30 mins. Also, after having fully charged the G10ST using the accessory cable, and then did not use the G10T for several weeks, when I subsequently reconnected it to the charging cable to make sure it was brought back to fully charged status, it only took a very few minutes (about 3-5) before it was fully charged (i.e solid Green LED). Thus, the G10T's lithium battery does not loose very much of it's charge when not being used. During the several weeks of nonuse, I leave the G10T resting in the unpowered base receiver charger unit, but the G10T is NOT fully inserted in the base, and the base is not energized! If fully inserted, I believe the battery will drain in the non energized base unit. My guess is the Transmitter would go into Standby mode after 4 minutes fully inserted in the non energized base, and then it would have about 200 hours of Standby Battery life. So, to keep the Transmitter's battery in best shape, keep the Transmitter is OFF! This requires that the microswitch at the base of the Transmitter's 1/4 Sleeve is NOT depressed!

Lots of user's (of alll sorts of gear) still appreciate the ability to print out material for easy reading and notations offline.

My Helix feeds Two (2) Yamaha DXR10 Monitors (Yamaha Level Knobs at 12 O'Clock) for a nice wide sound field at reasonable SPLs. I have yet to sell either of my Fender Mustang Amps (IV v.2 and III v.2) as I have them for backup (amps/powered cabs) and occasionally run them "Dry" in a W/D/W config with the Yamaha DXR10s.

Check your power cord and power strip or outlet to be sure it has a good ground connection aside from the Hot and Neutral connections. And, that your speakers and any other equipment connected to your Helix are all powered from the same outlet or power strip. Some have reported noise from their USB connection between their computer and the Helix. If your are using a USB connection disconnect it to see if that may be the cause.

Now that's truly World Class Line 6 Tech Support!!

If Helix Native arrives this or next Month, paving the way for Helix Editor (with it's newly revised User Interface) and Firmware 2.30 to arrive together before the end of Summer, and then Firmware 3.0 arrives with a new Helix 3.0 User Guide by Thanksgiving, I'll be delighted! There's a massive amount of work involved to elevate Helix's entire software and firmware infrastructure to the new level of what we'll find in firmware 3.0. I also recollect DI or Frank posting (here or on TGP) that the overhaul of the Updater, Firmware Installation, Preset and IR Backup/Restore, etc. would not be introduced until later this year. So, I'm anticipating we won't see that until at least generation 3.00 firmware.

I too favor user options and maximizing features and flexibility. The problems are that many users do not thoroughly educate themselves nor read the User Manual and Release Notes to familiarize themselves with available options. The deeper the options become, the more likely users will never discover them. There's also the requsite programming resources to implement such optional features that may serve only a small portion of the user base. Absent a larger programming team, this may divert such resources from improving and working on more justified features.

That should work great and gives you both routes!

Seems like a good candidate for an IdeaScale suggestion!

If you have not (re)installed the latest version 2.21 firmware and performed the combination Footswith 9 and 10 Press and Hold Restart Procedure, do so to determine if it doing so remedies what you are encountering.

If you'll be Copying to Duplicate your customized template Preset for your various songs, the Snapshots in the source Preset you Copy will be present in the resultant Presets. Thus, whatever parameter variable settings and names you have created for Snapshots 2 and 3 (in your source Preset) will be present in the duplicated Presets. If your customized template has the actual names and Parameter Value settings for those Snapshots, you would need to Edit those Snapshot Names and Bypass Blocks or reset Parameter Value settings for the various Presets for songs containing those Snapshots that you do not use. It may be easier to start with two versions of a customized template Preset. One for the Songs that use all Four Snapshots, and the other for the songs that Do Not Use Snaps 2 and 3. This way your customized template Preset for the later case could already contain the "NONE", BLANK" or "DONOTUSE" Names for Snapshots 2 and 3 as well as the Bypassed Blocks, or reset Parameter Value settings. This would reduce the amount of editing needed for subsequent song Presets.

@TheBoyWithDog, I would love to see multiple Parallel Split and Merge points per Signal Path (as you depicted graphically in your other post): Just not sure if Line 6 would feel too many Helix users would use the feature. You should post a separate IdeaScale suggestion for this: Multiple Parallel Split and Merge Points in a Signal Path. Your existing IdeaScale post does not adequately emphasize this suggestion!

I have no idea if the December 2015 Knowlegebase FX Loop Noise Floor Known Issue is on Line 6's Helix To Do List. It sure would be nice to see it remedied in firmware 2.30 or 3.0.

The only constraint regards the speakers, if they are connected to the Helix. Otherwise, you'd need to connect the speakers to the mixer and feed the Helix's output to the mixer (when using the Helix), and feed your computer's analog audio out to the mixer (when using the computer).

This could be done. However, there is no method to simply lockout one or two Snapshots. You may want to keep the names of your Snapshots clearly legible. Snapshots support different (i.e. altered) Parameter Values -- as well as the Bypass/Enable Status -- for the Blocks in the Preset. All the Blocks in a Preset will be present in each Snapshot! Snapshots do not support removing nor repositioning/resequencing of Blocks in the Signal Path. Keep this in mind as you consider how best to have your bandmates recognize which Snapshot to enable. The trade-off here is that if you change cabinet selection in an Amp+Cab Block, all of the Cab's Parameter values revert to that selected Cab's Factory default settings. Thus, it can be an arduous task anyway. One approach is to begin with the combined Amp+Cab Block to see how they suit your needs, and adjust the Amp and Cab Parameters as desired. Once you get the settings dialed in for what you prefer, then consider using separate Blocks for the Amp and for the Cab. And, above all, when you find your desired settings, it is highly recommended that you Save that as a separate custom template Preset configuration named as you choose, in any Library or Resourse SetList of your choosing. That way, you will have it to recall and revise as you proceed.

The Yamaha DXR line accepts a wide range of input signal level sensitivity. It also has a very convenient and informative input overload indicator. If you choose to leave the Yamaha's Input Sensitivity switch set to Line Level, you may then set the Input Level control on the DXR and the Helix as desired. This also with the Helix Main Out set to Line Level. If you want thunderous levels from your DXR set it's Input Sensitivity switch to Mic and turn down the Input Level control. Also, be sure to turn down your Helix Main output Volume Level knob.

@troyclemens, if your Helix was sent to Line 6's Calabasas HQ and delivered to them on 7/5, there's a very good chance that it may be on it's way back to you this week (unless a required part is out of stock or on backorder). Line 6's tech support has been outstanding! Keep the thread upated with developments.

I have no doubt Line 6 will want to get this diagnosed and remedied ASAP! Keep the thread updated with developments.

Glad it helped you out!

An FX Send Block, before the Output Block, may be used. Alternatively, use another Signal Path and redefine the Output Block to use one of the FX Send outputs. Either method, will give you a Level control parameter for the Block that is adjustable via the Block's small rotary encoder knob for that parameter (and Pedal Edit Mode).