HonestOpinion

I am very curious to see how the touchscreen for the Headrush will be received. When I initially wrote a review for the Helix the touchscreen was a feature I commented would have been a great addition not substitution for the physical knobs for certain operations and its exclusion was an oversight in the Helix's design (even if that "oversight" was intentional) . If I remember correctly Line6 had found in their preliminary market research that users did not like touchscreens. This impression was reinforced by negative feedback on the forum regarding touchscreens as well as lack of voting and even downvoting of touchscreen ideas on Ideascale. We may now see whether a touchscreen is the anathema it has been purported to be as things play out in realtime with Headrush sales and their user's reviews and comments. Like other users here they definitely captured my attention with this feature which I would like to see implemented on the Helix in future versions; I don't want to lose the physical knobs and switches for navigation but I would love to see a touchscreen added. It could be very helpful for many actions on the Helix like preset and snapshot naming via a virtual keyboard, dragging and dropping of blocks for preset design and path rearrangement, etc.. I think if users are given a choice between physical knobs or touchscreen they often fall into two distinct camps with perhaps more people preferring the physical knobs. However, if you gave people both I think the majority of users might find that both a touchscreen and knobs and switches combined make for a powerful and extremely easy to use interface.

A few points that may already have been touched on in this long thread regarding the Native app plugin; particularly with an eye towards transferring presets back and forth between the two. If latency is low enough the Native app might make a nice backup in case of Helix failure during a performance. Particularly with some kind of foot pedal device added that can be used with your laptop. It would be a good feature if the Native plugin supported some of the the available wireless Bluetooth pedals as well perhaps as MIDI. The current description of the Native app says it would be limited by the hardware resources available on the computer, not the Helix hardware resources. That means that you would need to have some kind of 'Max Compatibility' setting for presets that you intended to transfer back and forth between the Helix and Native app. The 'Max Compatibility' setting would limit what you could dial up a preset in the Native app such that you would not end up with a preset that used too many blocks or too much DSP to load back to the Helix. Even if the Native plugin is entirely faithful to and mimics the Helix's sound, when using the Native app on your computer you would have to dial up your presets on the same or substantially similar external monitors you use for your Helix if you expect them to behave predictably during a performance. Designing the presets with the same monitors whether using Helix or Native app would give you a better chance that the sound was similar when a preset was transferred from the Native plugin to the Helix. Dialing in a preset on the Native app using headphones or computer speakers or even studio speakers is bound to sound different once you have it pumping through your FRFRs, PA speakers, or guitar amp.

Still want to see some Helix HX reverbs come to the Helix including some mono HX versions!

If a new firmware is demonstrated at NAMM, the information about it has essentially been released to the public even if the firmware has not been officially yet. At that point, by providing the preliminary release notes, you are ensuring the larger pool of users, rather than just the ones that attended NAMM know the details. I don't think this necessarily heralds an entirely new policy regarding transparency on future Helix modifications. It may be a first (don't remember this being done before) that the future firmware release notes were provided rather than just the usual NAMM summary bullet points you see after a NAMM show detailing new features on devices demonstrated there.

There is a thin line between advertising hype and fraud. ;) That is a pretty explicit claim though. I wonder how that can even be determined?

I see these posts periodically regarding Helix freezes. In the past they were usually related to specific problematic presets. This assumes the freezes are not related to the global reset not being executed after a firmware update or an Editor version that is mismatched to the firmware version. Does this happen on multiple presets? Does it happen on factory presets? If it is happening only on presets you have customized it might be worth backing them up and then restoring them again. If that does not help rebuilding them from scratch might. Not a great solution but worth it if only a couple are causing the freezes.

Some of my greatest areas of curiosity right now regarding this device are: They are claiming "THE MOST VERSATILE, REALISTIC-SOUNDING AND RESPONSIVE AMPLIFIER, CABINET, MICROPHONE AND FX MODELS EVER FOUND IN A FLOORBOARD GUITAR FX PROCESSOR". Will this be the case? What compromises did they have to make to provide "Gapless preset switching". Did they find some really slick way to do this or are they severely limiting what choices you can make in a preset by for instance giving you one slot for each effect category? Ultimately how does their quad-core DSP processor compare with the two SHARCs on the Helix. How are IRs implemented. How large (max bytes) can they be and how many can be loaded? Will there be an editor? How will this device be supported? Frequent firmware updates? Many more effect, amps, and models? New features? How robust is the build quality?

Thanks for sharing this! :)

Nice!

It almost looks like they liberally 'borrowed' from not only the Helix design but, due to the touchscreen and graphics, also that of the Digitech IPB-10 which used an iPad as the control surface. The interface they are showing reminds me of how the Digitech looked.

I use the volume control on my L2m for monitor level as Silverhead advises. He is correct that by default the Helix master volume is set to 'Multi' which controls the volume of the XLR, 1/4, and digital (L6) outputs. There is a parameter however, 'Global Settings' --> Ins/Outs--> 'Volume Knob Controls' that can be set to XLR, 1/4, XLR + 1/4, or digital. If you decide you don't want the master volume to control your L6 LINK output level I believe you can use this setting to change it by making it either not control the L6 LINK volume or only control the L6 LINK volume.

I don't ordinarily use a mic with my Helix so I have no idea if +40db is normal. Maybe some other folks can weigh in on the settings they use. Generally it is condenser mics that require phantom. I would look at the documentation for your mic to see if it requires phantom power and if so what voltage it requires. If you can't find any docs then try it first without. https://en.wikipedia.org/wiki/Phantom_power

If you run L6 LINK out to the L3t I would use the Helix XLR out to connect to FOH so that you can take advantage of the Global EQ if you need it for FOH adjustments.

Maybe we will see a Type C USB connector on the next Helix version. I believe this would allow it to act as either a host or a client using the same connector. The only problem is most older and even many newer computers don't have this connector yet. Users might have less compatibility issues with older computers if they included both a Type A and Type B connector. Most manufacturers will not include both types due to added expense but I think primarily because the chances of someone connecting the wrong device and blowing a circuit board go way up when both connector types are provided. There is a USB coupler Type B male to Type A female that could be used to connect a flash drive directly to the Helix. I am not sure how or if the flash drive could be powered though. There is also a USB coupler Type A female to female which could be used with a USB cable and flash drive or I guess theoretically to connect two Helices to each other. Note: I am strongly recommending that no one should try this. If it is even doable on the current hardware you would need a firmware update to enable this to work for transferring presets and again the potential for someone to plug in the wrong type of device and burn something is absolutely there once you start using these. http://www.staples.com/Monoprice-USB-20-A-Female-to-B-Male-Adapter/product_1255249?cid=PS:GooglePLAs:1255249&ci_src=17588969&ci_sku=1255249&KPID=1255249&cvosrc=PLA.google-SALES.Computer%20Accessories%20%26%20Peripherals&cvo_crid=39357180702&cvo_campaign=71700000015225244&gclid=CMvgr6HqwtECFcWFswodKEcF-g http://www.miniinthebox.com/usb-3-0-type-a-female-to-female-adapter-coupler-changer-connector_p3273844.html?currency=USD&litb_from=paid_adwords_shopping&utm_source=google_shopping&utm_medium=cpc&adword_mt=&adword_ct=153426320819&adword_kw=&adword_pos=1o2&adword_pl=&adword_net=g&adword_tar=&adw_src_id=9772115911_686959326_35189017357_pla-276956234565&gclid=CPOyhN_nwtECFVBMDQodPq4Ofw

Klangmaler, master of the succinct video summation. ;) Agreed, there are so many more interesting things to be talking about regarding Helix capabilities. So let's just fix this thing and stop flogging this poor revenant of a horse already.

The 'true temper' tuning you refer that I preferred to "sidestep" for the moment would be the final stage in designing a tuner with truly superior capability. I'm with you on that "shudder to ask" thing. That functionality would be great but I would be happy if first we could get this tuner working properly with conventional tuning. Fixing the tuner is actually one of my highest priorities on the Helix right now, more so than new amps/effects or new functionality (although as always I remain enthused for the other stuff as well). I just see fast and proper tuning as fundamental to performing unless you are playing vintage blues and playing slide with an old butter knife. I can see where it might not be as important to musicians who use the Helix primarily in the studio where unless you are paying a high end studio by the hour you have the luxury to take your time tuning but I consider the tuner a real problem for stage right now. I like being in tune and getting there quickly and the tuner just is not cutting it right now. Don't mean to sound harsh but if the Helix tuner was a standalone tuner pedal on my conventional analog pedalboard I would have long since replaced it with something more practical. I really hope L6 gets to this sooner rather than later. I know DI performs live with his band and there must be others at L6 who do as well. They have to be aware this is an issue.

Very informative post, thank you!

Wahoo, awesome!! :)

Yep, acutely aware of this, that is why I directed my comments towards the release of the next Helix version e.g. 'Double Helix'. Theoretically I suppose you might be able to use the USB connection to connect to a WiFi adaptor or maybe even some kind of Bluetooth adaptor. As long a there is a route (USB) already in existence for communicating between the Helix and an app you should be able to create an adaptor that could transmit and receive wirelessly. Seems like a lot of trouble and expense that I don't foresee happening in this version of the Helix. You never know though, those crafty L6 fellows have surprised me before.

I really am going to use your suggestion until this gets fixed. In no way was my feeble effort at sarcastic humor directed at you or anyone else for that matter. It was squarely aimed at the inanimate object - the tuner (or in this particular case the all too overly animate object).

:)

Please let us know if it works for you. If the MIDI implementation on the Carvin is similar to that on the Hughes & Kettner that the fellow sets up in the first video link I see no reason why it shouldn't.

I am surprised to hear that answer unless the combination of MIDI messages required by the Carvin can't be selected on the Helix or the MIDI function is not working properly within snapshots yet. Take a look at page 34 of the 'Helix 2.0 Owners Manual Rev. D' when you get a chance. Theoretically you should be able to do what you are attempting either through the 'Ext Amp' controller output or the instant MIDI CCs. It might be worth giving it a try. Here are two videos using channel switching via MIDI that may point you in the right direction. The first video is using snapshots and MIDI commands to do exactly what you are attempting.. Good luck!: https://www.youtube.com/watch?v=LIF1Z7ggGm4 https://www.youtube.com/watch?v=p2R1impQ2vw&t=3s From the manual: There’s always going to be a small audible gap when switching presets in any box with the Helix device's level of dynamic model allocation and routing complexity; that’s just how advanced DSP works. However, snapshots allow for a surprising amount of tonal control from within the same preset, and every change happens instantly and seamlessly. Similar to the snapshots feature in some high end digital mixers, each of the Helix device's eight snapshots stores and recalls the state of certain elements in the current preset, including: • Block Bypass—The bypass(on/off) state of all processing blocks(except Looper), independent of any footswitch assignments. Also see "Snapshots > Block Bypass" • Parameter Control—The values of any parameters assigned to controllers (up to 64 per preset). Also see "Snapshots > Parameter Control" • Command Center—The values of any instant MIDI CC, Bank/Prog, MMC, and CV Out messages, plus the state (dim or lit) of any CC Toggle, CV Toggle, and Ext Amp messages. Also see "Command Center"

You are right about the slowness of the data transmission with Bluetooth, the speeds of even the newest Bluetooth 5 standard still lag way behind WiFi. When talking about transmission speeds though you have to consider how much data actually needs to be exchanged between the two connected devices which is somewhat determined by what activities you would be trying to execute with for instance a tablet connected via Bluetooth. It doesn't matter if your pipe only has a one inch diameter if you are only pouring a few drops through it per minute. My impression judging by how small presets exports are is that the amount of data that needs to be transmitted from the app to the Helix might be relatively small for many actions. Most likely you would use a Helix footswitch for presets, snapshot, and stomp switches during a song. Your tablet would probably be used on a mic/music stand or desk to change parameters, manage and name set lists and presets, do backups and restores, and make other sorts of changes that might not require a response with close to zero latency. Many of these actions might require only a small amount of data to be sent and returned. Perhaps even slow Bluetooth could keep up with this. Ultimately though WiFi might just be a better more flexible choice given the exponentially higher data transmission rates.

No desire to own a FireHawk 1500 although more power to those who do. I don't think having wireless (and potentially as a bonus touchpad capability) and also having a PC/Mac app are mutually exclusive. I certainly would not want my PC app replaced with an iPad app, but both, ahhhh. There is potentially a problem with spreading development resources too thin and I agree with that concern but perhaps the effort would be worthwhile nonetheless. I would not be surprised if we see wireless functionality in the next Helix, even if it only works via WiFi via the same types of apps we have now on a PC or Mac.