Leaderboard

The simplest fix is to hook the output up to a mixing board or a DAW and manage the signal level output from the Helix. This is how I dial in all my presets using a small 6 channel mixer. This isn't just for gain staging but helps in leveling out the volume levels in all your presets/stomps which makes you very popular with the sound crew. Short of that the easiest way is to make sure that when you add a block you're not constantly increasing the output level of your signal chain. So you can do this by simply listening to it without the block turned on and with the block turned on to make sure you're maintaining the same general volume level throughout the preset.

I know, right? I'm an iOS developer and I reported the problem in a bug report to Apple a month ago (FB7127906, if anyone from Apple is reading). But that doesn't have as much weight as a bug report from Line6 themselves, especially because they could have done more troubleshooting and maybe included details that would help Apple identify the problem. Of course it's possible that Line6 _did_ find the problem and alerted Apple and nothing happened; Apple bug reports go into a black hole and it sometimes takes a long time for them to be addressed. But even if that's true, it was bad form of them not to acknowledge the issue in this thread (or some other thread), or to post a compatibility warning earlier the way other companies like NI and Ableton did.

found a great seller in the forum!!! license purchased. excited to get creating.

Just select Helix Native from the middle pulldown box. https://line6.com/software/index.html

Hello Beamboom, In the Filters section, just find one that allows you to modify the "sensitivity" parameter (= envelope ) and set it to 0. Then, control the cut frequency with an exp. pedal or MIDI. (And also , set the the filter mode to "low pass) -> I believe the Autofilter will do the trick.

OK, found a fix. There's a bug with the folder permissions when it installs, but the app is actually there. 1. Do the install 2. Go to your Applications folder where there'll be a 'Line '6 folder with a no entry sign on it 3. Get Info on this folder (CMD-I) 4. On the bottom-right of the Info pop-up will be a little padlock. Click this and type in your Mac password 5. At the bottom of the pop-up, click the menu item under 'Privilege' for 'everyone'. It'll be set to 'No access' I think. Change to 'Read only' That's it. The app will now appear.

I'm using Cubase 9.5, and after using Line 6 Helix Native for about 24 hours it started freezing Cubase every time I tried to open an instance of the insert. Cubase only becomes unresponsive when you try to open up a new instance of the Helix insert, or open an existing instance by clicking on the insert. But, like it says in this forum, all of the sounds still work in your existing projects. Obviously, it's a huge problem for those affected, as you can't use Helix Native at all which isn't exactly ideal if you've spent (a lot of) money on the software. Given that the last post was over a month ago, has anyone seen a fix yet? Any help would be brilliant, thanks. I'm using Windows 10

Hi- I have a Helix Native license for sale if anyone is interested. $200.00 I'll be happy to send interested buyers my eBay account to check my feedback. Please let me know if you have any questions. Thank you!

Hey benvigil, this works for me perfectly. Thank you very much for your help. For Windows User, go to: C:\Users\{Your Username}\AppData\Roaming\Line 6\Helix Native and open the "Helix Native.prefs" with an text editor. Then remove everything that is marked Yellow in the pic I added. If you can't see the folder "AppDate" it is because it is hidden. In your Explorer Window, go on the top to "View", then to "Options" and there go to the rider "View" and search for Show Hidden Files and Folders in the List to activate the viewing of the hidden folder.

Kinda odd seeing this thread because I have the EXACT same problem running Presonus Studio One with Hellx Native on macOS! It will run perfectly across multiple launches for about a day (i.e. 24 hours), then it crashes the DAW. However, I DID run it up the flagpole with L6 support and their only suggestion was to completely reinstall the DAW... which made no sense, because all plugin versions (AU, VST) crashed every DAW and VST host I tried it with. But I happened upon a solution: after installation, and you use the VST for the first time, it creates a set of folders in your user directory. There is a preferences file that you need to edit. On macOS, it's located here: ~/Library/Application Support/Line 6/Helix Native/Helix Native.prefs In that file, there is a key called "Session Token" -- if you close the DAW, open that file, remove that key and value, and save the file... everything works again... for 24 hours.

Hey CryoHeart, don't feel alone and maybe resist to install Windows 10, because I have a similar problem with Helix Native on Cubse 9.0.40 and Windows 10. After the installation and registering it, everything worked fine, but now, as soon as I click on the "edit" button in the Cubase mixer to open the Helix GUI, Cubase crashes. The GUI is not working at all and not reacting to any input. Still, the Audio engine keeps running. I tried to reinstall it and it helped for exactly ONE time. The next day, I open the same project and as soon as I open the GUI of Helix, Cubase crashes again. This happened to me with the VST3 and VST 2 version. Nothing helps but another reinstall. Funny thing is though: as long as you don't try to upen the GUI, Helix works fine, meaning all the sound coming out is definetly what I configured before. Have you got eny answer from the support?

I have exactly the same problem with Helix...