HonestOpinion

Duncann, could you please post this up if you locate the reference from TGP. Thanks!

I don't believe Helix Edit 2.30 removes the old Helix app automatically. I think you have to do it manually. Here are the firmware release notes. See instruction #5. Updating a Helix Floor/Rack/LT Running 2.20.0 or HIGHER: 1. Download and install the all new HX Edit application, available here (this will also install the latest version of Line 6 Updater): Mac OS X: https://line6.com/so...ula.html?rid=7883 Windows 7/8/10: https://line6.com/so...ula.html?rid=7884 2. Connect Helix to your computer and launch HX Edit. From the File pull-down menu, select “Create Backup…†Follow the prompts to create a full-state backup of your Helix (Global Settings, IRs, setlists, and presets). 3. Close HX Edit, open Line 6 Updater, and follow the prompts to update your Helix's firmware. Helix will begin rebuilding presets. Wait for this process to complete. 4. Close Line 6 Updater, reopen HX Edit, and from the File pull-down menu, select “Restore From Backup…†Follow the prompts to restore Helix to its previous state. 5. Remove the old Helix application from your computer. It won't work with 2.30 firmware anyway.

I felt the same way initially as you about the Bias-X control but periodically I stumble upon amp models and presets where changing its settings makes a big difference. On others as you have observed changing it makes little to none. You can use a looper and find the models that are most impacted by it. I tend to run ripple down low or not at all. The "Ripple" I enjoy comes on a wave, in a bottle, or was written by Robert Hunter.

You never know what people can get to work but a 64-bit DAW and OS is a minimum requirement listed for running Helix Native. Worth a try though, let us know if it works. I assume the process would be to start by trying to convert the Helix Native with jBridge (can jBridge convert for VST3 files?). Then point your DAW to the converted file. I tried getting a conversion with jBridge for Helix Native and was not successful. Maybe you will have better luck but upgrading to a 64-bit OS and DAW might be your only recourse, at least right now.

The primary things I would like to see changed in both Helix and Helix Native's IR management: Increase the namespace to something reasonable that allows enough meaningful information about the IR to be displayed and does not require renaming of IRs from the many vendors that use longer names. All IRs must have a unique name. This might be required to execute the next bullet point. The IR blocks in presets use the unique names of the IRs, perhaps with some kind of aliasing, so that they can be moved from slot to slot without breaking the link between the IR and its corresponding preset(s). Indicate which IRs are in use and prompt the user before allowing them to be removed. Ideally an override setting allowing the prompt to be tuned off would be provided. Allow more IRs to be stored on the Helix and Helix Native. I find the current number insufficient on the Helix and particularly on Native where the hardware limitations are determined only by the computer's configuration. It seems that many more IRs could be accommodated in Native being run on sufficient hardware. If there is not adequate memory onboard the Helix to allow more IRs a possible alternative would be to allow a Setlist to be changed to and designated an IR list. Preset backup files and IRs are roughly the same size and I am sure there are plenty of users who would be happy to give up a Setlist in order to gain the ability to have twice as many IRs. Some users might even prefer two or three of their Setlists be IR lists instead. Perhaps there is already adequate memory on the Helix however so as not to have to lose Setlists. It seems it would be an even simpler matter to allow multiple or larger IR lists on Helix Native.

As others have noted you will need to keep the system as bare bones as possible regarding other software and processes you run. You don't want anything launching an upgrade process or attempting to check the internet, restart, etc. when you are live. Additionally you will probably want some kind of MIDI foot control. I would want a fast boot process as you might just have to reboot in the middle of a song if the system locks up. Let us know how it works out for you.

Has anyone managed to get the Helix working as a proper MIDI controller for Helix Native 1.10 in Tracktion? I am currently using Tracktion version T6. I was able to set the Helix up as a MIDI controller with no problem for other Tracktion plugins' parameters but Helix Native will only show me two parameters, 'Wet' and 'Dry' levels, that can be assigned to MIDI control or automation. I have set up the parameters that I wish to control within Helix Native using the "Automation/Controller Assign" tab but the assigned parameters/controllers do not show up anywhere in Tracktion when I try to assign the Helix as a MIDI controller to them. Tracktion's internal automation envelopes can't seem to see my Helix Native parameters either. The "Learn" function in Tracktion does not help and also can't see any Helix Native parameters. Am I missing a step, is this a Tracktion problem, or is this a Helix Native issue with automation and MIDI not being properly implemented yet? Maybe I am just missing part of the procedure. Has anyone successfully set up automation and MIDI on Tracktion for the Helix Native plugin? If so, could you please post up your procedure. Thanks!

They are giving away the new T6 version of their DAW for free. Maybe it would be worth just upgrading to Tracktion T6 instead of trying to get T5 working. Are you using a 64 bit version of T5? Helix Native has a 64bit version of your DAW as well as a 64bit OS listed as minimum requirements for Native. Free Tracktion T6 DAW software download: https://www.tracktion.com/products/t6-daw Helix Native minimum requirements: https://www.thegearpage.net/board/index.php?posts/24683148/ http://line6.com/support/page/kb/_/recording/helix-native/helix-native-faq-r866 Btw, I am running Helix Native with a 64bit version of Tracktion T6 on Windows 10(64bit) and it runs fine although I have not been able to get the MIDI and automation functionality working properly yet. Just got Helix Native though so it could be me.

Yes, the firmware notes even recommend uninstalling the old Editor.

These are available off Amazon although I can't vouch for them as I have not tried them (I am ordering them now). They do apparently allow you to choose the colors you want. Similar to the Mooers buttons these do not have a set screw so they will not allow capacitance sensing. https://www.amazon.com/Guitar-Effect-Protection-Effectfor-Colorful/dp/B075WCG4L7/ref=sr_1_2?ie=UTF8&qid=1512437858&sr=8-2&keywords=Footswitch+topper Another option with set screws which allow capacitance sensing but without a transparent cap. I don't know how visible the LED rings will be with these. Come in sets of three, choose color. https://www.amazon.com/Footswitch-Topper-Guitar-Protection-Effectfor/dp/B0757FKGB4/ref=sr_1_2?m=A2NDZ3WH9YVUX8&s=merchant-items&ie=UTF8&qid=1512438740&sr=1-2&keywords=effect+topper

I believe the 30% Black Friday discount ended on December 3rd unless they decided to extend it. I suppose you could try plugging in the CYBER30 discount code and see if it is still working. http://line6.com/helix/helixnative.html

LOL, I have been guilty of this more than once myself, particularly when I first got my Helix. Increasing the volume on the radio will not make the car go faster... :P

I am loving the addition of drop-down menus and lists in strategic places in both Helix Edit and Helix Native. I found the wide sliders only GUI in previous Editor versions to not only cause unnecessary paging but also to be less than ideal particularly for viewing blocks/parameters where there were many text based options. With sliders and pull-down menus (best of both worlds now), in the new editor and Native as well as informative screen sections like the new "Edit" and "Bypass/Controller Assign" screen I feel like the editor has taken huge strides forward in ease of use with the new Helix Edit 2.3. Very grateful for these extraordinary tools that seem to just keep getting better (let's back out those changes that reduce parameter resolution though). My satisfaction at having made the choice to go with the Helix continues to grow. I am delighted at its continuing success and the way this has persisted in yielding tangible improvements and enhancements for all us users. Bravo!

I love the Cosmos delay, great addition! It does use quite a bit of DSP. Probably to be expected for that kind of effect with that many parameters although perhaps it can be further optimized. I only noticed because I went to add an LA Comp on my signal path (Super Serial x2) on one of my presets and it and just about everything else were grayed out when I had the Cosmos in the path. I was able to easily add an LA Comp and a phaser after swapping the Cosmos for another delay. Very happy to have this great sounding delay and an inspired choice by Line6 to add it but just be aware it does chew up some DSP. Glad to see this level of complexity and attention to detail in an effect block though. I am more than willing to sacrifice the DSP for effects like these. Finding a way to reduce the amount of DSP used without impacting the quality of the effect would be ideal but perhaps impossible? Note: This was on a preset that had three amps set up going through a single cab as well as a couple of effects and EQ. An arrangement I often use in a preset to emulate a multi channel amp.

Great news! Hope they include mono versions.

I do find the tuner a bit more stable when set to 'Guitar' rather than 'Multi' although still feel it needs improvement. I also don't understand why it is more stable when set to 'Guitar'. I have wondered why this is the case and if other operations on the Helix are "disturbed" when "Multi" is selected for the input block. IMHO it should not make a difference and the fact that it does begs the question of whether the processing of the input signal is changed somehow other than just allowing multiple sources for the input. I wonder if this has an impact on other facets of the input signal's processing?

Absolutely agree, these changes need to be undone. Enforcing too widely spaced intervals and lack of resolution both directly on the Helix and via the Editor is particularly problematic for anything where it impacts pitch and is generally just not helpful.

There is a lot to love in the new Helix Edit but I have to agree with this, most of the time anything that starts enforcing poor or lower resolution and ceases to allow the user to dial in the value they are targeting in exchange for easier knob turning represents a poor tradeoff. Would generally prefer not to sacrifice accuracy and fine tuning just to make a knob easier to spin. In addition, allowing direct typing in of exact values is always preferable to having the Editor or Helix take the typed in value and automatically adjusting it to the closest adjacent "allowed" increment. The new change that lowers the resolution in the parameters in blocks like the Parametric EQ is a step backwards in my opinion. Perhaps this won't make that big a difference in practice but this is a change I hope they back out in future versions of the Editor. On a similar note regarding "enforced" values I would still like to see the 'Low Freq" parameter in the parametric EQ allow a higher range of values rather than the 495hz it tops out at.

Just a reminder that you can pick up Helix Native at a 30% discount right now as part of the extended Black Friday sale. The discount applies in addition to whatever discount you would get if you already own a Helix device (Floor, Rack, LT). Sale is running until December 3rd. If you have been holding off this seems like a good time to go for it.

:)

Could you tell us what cabs were modeled in the Vintage and Hi-Gain preset-IR collections? Also curious why you used both ACE and non-ACE versions of the cabs? Thanks.

Worked for me. You may have tried them a day early, that promo started on the 25th.

Thanks for the heads up! I went and got myself a few Celestion IRs straight from the source.

Glad to hear it! :)

Not sure if both banks have new presets but if you find the following in Factory 1 you probably have the new presets assuming you did not restore over Factory 2: 13B - Voltage Queen, 13C - Derailed Ingrid, 13D - Cartographer, 14A - Brit Trem Norm, 14B - Brit Trem Bright, 14C Brit Trem Jump If you don't have these after the update you can use the procedure in the bottom of this post to get them back. You will just have to backup, run the global reset on your footswitches (Helix Floor) or encoders (Rack) and then do a restore. http://line6.com/support/topic/30512-new-presets/?p=235275