MusicLaw

HudsonHawk: In addition to their own internal development ideas and intentions, Line 6 uses the IdeaScale method to accumulate User Inpug and Suggestions for features and improvements. IdeaScale is a good place to post your suggestion for others to vote up and for Line 6 to consider. I believe I have already seen a similar post on IdeaScale for alternate use of the large display screen. IdeaScale can be reached via the Line 6 main website. Use the search tool to see if you can find the previous similar post. If not, simply go ahead and add your own! Your suggestion make sense to me. I'd certainly add my affirmative vote!

The latest Helix 2.0 Owner Manual - Rev D - PDF is the one you want to download from the Line 6 site Manuals area. This current version was released in July 2016 to coincide with introduction of the Snapshots feature. The USB stick supplied with the Helix unit, most likely still has the now long outdated earlier version of the User Manual PDF. Line 6 has announced that the User Manual will be updated only for major firmware releases. This presumably means full interger firmware versions. Thus, no new User Manual is expected until firmware 3.0 is released. No schedule was provided. As there have been no addendums published to the 2.0 User Manual. Users are left to find the Release Notes for the interim releases on their own. Unfortunately, these are often cumbersume to find on the Line 6 website. The interim releases have been 2.10, 2.11, 2.12, and 2.20 (expected shortly). Line 6 has also mentioned a 2.30 fw is in the works. Thus, it is left up to the users to patch together on their own the aggregate new features and bug fixes of these interim releases until Line 6 revises the User Manual or provides an interim addendum.

Since July 2016 I've had three G10 base unit USB ports that failed! Each was returned to Line 6. The one I have now, received brand new as a Warranty replacement from Line 6 has yet to fail. The original product warranty is 1 year. The credit card I used for the purchase provides an extenstion of the warranty duration by one year for a total coverage period of 2 years. If the G10 breaks again, it will once again go back for warranty coverage. By the time July 2018 rolls around, it is not unreasonable to expect that Line 6 will have improved their production method to reinforce and secure the port. If not, I wouldn't be surprised to see other competitors, such as XVive, enter the market.

Give yourself time to get to know the Helix and how to dial it in. Ignore most of the Factory Presets. Build your own from scratch using any of the "New Presets" from any of the SetList folders.

A single DXR10 won't move as much air as a 2x12 combo guitar amp at band practice. However, a pair of DXR10s sure comes close! ;)

Most well designed Applications offer Preferences allowing a User to designate their preferred settings rather than OEM defaults for things such as the name and location of a download folder, backup folder, data folder, etc. I do not use the existing Helix Editor. Let's hope the forthcoming newly overhauled Helix Editor is superior and vastly improved.

If I recall correctly, each of Helix Paths (1 and 2) have equivalent DSP resources. Helix's UI and OS housekeeping chores are handled by one (or two?) different MPU(s). This was clarified by DI, some months ago, and posted either on the TGP Helix forum or here on these L6 Helix User Fourms. I'll see if I can find the link to that post and add it below.

Connecting Helix's Main L/Mono 1/4" Out to your Blackstar's FX Return will work fine to accomplish what you want to do. It also allows Helix's Main Volume knob to control the feed from Helix's Output Block (at the end of Helix's Signal Path) to your Blackstar's FX Return. As you become more familiar with Helix's versatility, you may wish to explore other signal routing options, such as using a Helix FX Send Block and Helix's corresponding 1/4" FX Send Jack to route the signal to your Blackstar's FX Return Jack. This would free Helix's Main 1/4" Out jack for other simultaneous use, if needed, such as FRFR spkrs, Studio Monitors, etc.

Don't Path's 1A and 1B share the same dedicated DSP; with Path's 2A and 2B sharing the second (additional) dedicated DSP?

The best method to assure that these instances are on Line 6's known Helix issues list is for everyone having the problem to report it to Line 6 on a Support Ticket. The more reports they get from users, the more they will be able to aggregte the input, respond accordingly, and take appropriate corrective steps as the scenarios require.

The Two DSP are dynamically allocated. One dedicated to Path's 1A and 1B. The other dedicated to Path's 2A and 2B. Aside from the Mix Parameter of the Split > A/B feature that does not appear as a square block (nor does it count as one of the 8 per Path), the Mix Parameter is common to the FX Blocks, IR Blocks, and FX Return Blocks to adjust the blend of Dry vs. Wet, IR vs. Direct, and Return vs. Main signals. Firmware 2.10 (November 22. 2016) also introduced a Pan Parameter to the Split > Y feature: - Split > Y Balance parameters—The old Split > Y block sends both left and right signals to Paths A and B equally. 2.10 adds individual balance (pan) control of the signals sent to Path A and B. By default, they’re set to “Centerâ€, which behaves exactly like the old Split > Y block. - 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)

Martin, if the G55's XLR out is always active, it could also be of use should you wish to route your signal to Helix's Mic In, or via adapter to any of Helix's other 1/4" Ins. If using the Mic In you will likely need to boost the Input sensitivity of that Input Block by at least 60db or more. This is simply another way to route your signal should you wish to use a distinct Signal Path in the Helix.

The idea of a Globally acting Reverb Bias adjustment could be very handy. It would be up to the Line 6 software engineering team to determine how best to implement the feature. Perhaps a new Global Reverb Bias Parameter (Dual state; On or Off) could be added to every Reverb Block. This could be set to "On" by the User should they wish that Reverb Block to be affected by whatever value the Global Reverb Bias control may be set for. Voted up the IdeaScale submission and posted the above as a Comment.

Helix also has offers four independent signal paths you may use, and Helix provides Multiple Inputs. You could bring the Acoustic, Bass, and Mandolin signals in to Helix through the Main Guitar In, AuxIn, Mic In, or any of the 4 FX Returns. Each may be assigned to it's dedicated independent Signal Processing path as you desire. Helix's versatile signal routing and processing paths are very flexible!

In this day and age there is no excuse nor justifiable reason for Line 6 (an established leading technology vendor), to allow their flagship product: Helix, to be subject to the confusion from a version numbering disparity between the product's Firmware and Editor Software. Countless User posts reflect this. Compounding the scenario is that a successful Firmware Update procedure requires far too much user comprehension, attention and intervention. The process is not fully software supervised nor automated, and involves User intervention at critical steps during the upgrade process. For Users with pre-existing Presets, more user intervention is required to perform additional essential steps to properly backup, convert and reinstall a user's now converted pre-existing presets. This entire process creates several opportunities where missed or mistaken steps, have caused a variety of problems, significant to those whom have encountered them -- as reflected in far too many User posts all over the Internet. With the imminent release of Firmware 2.20 (expected by month's end), and the subsequent release of Helix Native later this Spring, Line 6 needs to deliver on their overhauled Helix Editor application that intelligently and comprehensively manages the entire firmware and Preset update process. Once Line 6 handles this properly, this significant Helix complaint area will be gone, thus freeing Line 6 to continue optimizing Helix's sound and performance. All in all for a product approaching it's 2nd anniversary, Helix is outstanding!

An inexpensive A/B/Y switch box could work. Or, an even less costly, 1/4" Female TS to dual 1/4" Male TS Y-adapter cable, could split your signal. In either case, but you'd need to be aware of how the load on your guitar pickup changes due to splitting the signal.

If you have registered you Helix, I believe that may also have placed you in the email cycle for Helix notifications. Perhaps an equally if not more prompt method, would be to check, the Line 6 Product Support and Helix Forums each day! That is where the firmware updates are first posted, and, I'm not sure how soon therafter the email notifications ensure.

Aside from applying an EQ Block in your Signal Path, you can also try splitting the Signal Path using the Crossover Split Type. Using the Crossover Split's freq control, route 150Hz and lower freqs, as an example, to one amp and use a compressor block to tighten up the bottom end. The other branch use another amp to accentuate the mid to upper freqs from the Bass as desired. Only a few days in with your Helix, this may likely exceed you're current learning curve point. Nonetheless, keep it in mind to tinker with, as you can not break anything. Also, in the next week or so, the new firmware 2.20 is expected and it will have plenty more Amps, Cabs, and FXs, specifically for Bass players! [Note: Edited slightly for clarity]

Even the smallest ones I've seen would easily power the G10 for at least one gig. The G10 Receiver Base's current draw is very low. As I recollect, it was only about 300mah. Every one of the rechargeable units will have it's mAh rating somewhere printed on the packaging or the unit itself. Get the largest capacity version that makes sense price wise and for your use. The one's I prefer are the flat slab formats. These work well as a pedal base for the G10 Receiver to rest on, and that allows the USB power lead to be kept short. Many of the reasonably priced units are now well up to 20,000mAh capacity. And the ones around 12,000 to 15,000mAh are really cheap. Any of the packs with multiple simultaneously usable USB jacks will do the job to power multiple G10s. The only logistical issue would be power cabling to the additional G10 Base unit(s), and running the respective audio cabling to from G10 to its respective amp, board, MFX unit, etc. For me, I would go with multiple battery packs. That way you could use one for each G10 postioned precisely as you wish to optimize all cabling runs. And, you would have backup/redundancy. Check Amazon, as they have had a proliferation of these battery packs on sale during the past year, and you'll see plenty of ratings. I've now got a couple of the RavPower packs and they're great. Both were on sale when I bought them, and they include two cables one about 8" that is perfect for use with the G10, and another about 2 feet.

What else might you have plugged into the Cyberpower unit? Or, on the same circuit the Cyberpower powered from? It could also be a nearby source of Radio Frequency Interference (RFI), that is more apt at intruding into the Cyberpowered items, than simply via the wall warts. Another option is to go with a rechargeable lithium USB battery pack. These are becoming significantly more affordable and with higher power capacities. I've been using one of these for months, to power and recharge my G10. It works great, and is also works to power/recharge any USB device Smartphone, Tablet, etc.

I found the 10" vs. 12" suitably more compact and lighter weight. The same goes for my wallet! Once I heard the spectacular sound of the Yamaha DXR10, the Alto was out of the running!

Similar to this IdeaScale post: https://line6.ideascale.com/a/dtd/Snapshot-stepping-on-the-same-again/838176-23508#idea-tab-comments

It would be great to have two additional Helix Mic Cab Parameters. One for Mic Position (medial to lateral: Cap Center, Cap Edge, Mid Cone, Cone Edge); and one for Mic Aim/Orientation (0 to 90 Degrees). Depending on whether Line 6 originally captured 3D acoustic data, it may be feasible to reimage the data based on these Parameters. Otherwise, it would almost certainly require the substantial task of re-capturing the cabs with each of the mics. Either way, it would vastly enhance the sound of Helix's built in cabs, likely with additional DSP overhead (subject to whatever algorithm optimization magic the coding teams are using). On the other hand, L6 may have intentionally left this for 3rd Party IRs.

Nice!

It will work fine!