Reaper crashes when loading Helix Native

[ppoceiro]

Hi

Anyone experiencing constant crashes of Cockos Reaper when trying to load Helix Native?

 

I tried both VST3 and VST2 and always crashes Reaper.

Tried disabling windows firewall and defender with no better results. 

 

[FortyPsi]

Yes, that happens to me with both Reaper and Waveform.

I too have tried disabling the firewall and antivirus.

 

The same on two separate laptops.

[ppoceiro]

Yes, that happens to me with both Reaper and Waveform.

I too have tried disabling the firewall and antivirus.

 

The same on two separate laptops.

Hi,

Are your laptops recent and do they meet the requirements?

Already tried with two other vst hosts with no sucess.

Starting to think it's some incompatibility between my CPU which is 8 years old, and the Helix Native vst. 

Submitted a ticket to L6 and waiting for response.

[FortyPsi]

Hi there, they are not particulary recent laptops but the os is upto date and they are at least double the minimum spec.

 

I too have logged a ticket.

The response I got back gives the impression that they think it might be a network related issue. They are investing further.

[ppoceiro]

Hi there, they are not particulary recent laptops but the os is upto date and they are at least double the minimum spec.

 

I too have logged a ticket.

The response I got back gives the impression that they think it might be a network related issue. They are investing further.

Ok

Thanks for your input.

Still waiting for feedback from L6.

If you come across a solution or workaround please share.

Cheers.

[phil_m]

What version of Reaper?

 

I've been using Reaper with Native for two months now (I was a beta tester), and have never had it crash... You're using the 64-bit version, right? I don't think Native would actually show up anywhere on the 32-bit version.

[ppoceiro]

What version of Reaper?

 

I've been using Reaper with Native for two months now (I was a beta tester), and have never had it crash... You're using the 64-bit version, right? I don't think Native would actually show up anywhere on the 32-bit version.

It's the 5.40. And yes it's 64bit.

Never had any problems with similar VST's.

[chrislarue]

I have the same issue with reaper and helix native

[sleezye1]

It's been working fine in reaper for me on a 12 yr old amd w/ 4 gigs of ram

[luckett]

Mine is also crashing as soon as Helix Native is loaded.  I'm using the latest version of Reaper.  Other VSTs load and work fine.

[ppoceiro]

It's been working fine in reaper for me on a 12 yr old amd w/ 4 gigs of ram

S***... Then my suspicion regarding the CPU is crap.

Perhaps it's some internet issues...

Thanks for the info!

[gbbaker]

HP i7,  64 bit, Windows 7 Home SP1,  VST3 ,Reaper 5.4  all OK here.  Also Sonar XIII OK.

 

Bo

[bsg100]

Hi, I have same issue with both Reaper 64bit and Cubase LE 6 so don't think the issue is with Reaper itself. Tried numerous things such as disabling AV and firewalls, given full write access to VST folder and disabled routers firewall in case it is just the registration part that is being blocked. PC is couple of years old, Win 10 64 bit (fully up to date), Core I3, 8GB and using Zoom R8 as audio interface. 

Any update appreciated otherwise if I get any progress will let you know.

[ppoceiro]

Hi, I have same issue with both Reaper 64bit and Cubase LE 6 so don't think the issue is with Reaper itself. Tried numerous things such as disabling AV and firewalls, given full write access to VST folder and disabled routers firewall in case it is just the registration part that is being blocked. PC is couple of years old, Win 10 64 bit (fully up to date), Core I3, 8GB and using Zoom R8 as audio interface. 

Any update appreciated otherwise if I get any progress will let you know.

Still have the issues and still no response from L6.

Submitted a ticket a few days ago.

[luckett]

Helix native is also crashing Tracktion T5 as soon as the plugin is loaded. 

[silverhead]

During beta testing I had a similar problem. Reaper v5.4 running under Windows 10 would consistently crash during startup whenever an instance of Helix Native was present in the Reaper project file. If there was no instance of Helix Native in the project file Reaper would start up normally but would then crash on the first attempt to load an instance of Helix Native. This behaviour persisted through several different beta software versions and several different uninstall/reinstall cycles of both Reaper and Helix Native. The problem was not repeatable by the Line 6 Beta Support team; it was definitely something unique to my installation.

 

The solution to the problem ended up being to uninstall Helix Native, download and install another DAW (we used the trial version of Sonar Platinum), Download and install Helix Native again, and then use the new DAW to launch Helix Native for the first time. This somehow allowed the Helix Native files to initialize properly. We closed the new DAW program immediately. Thereafter Reaper worked normally.

 

We never did track down the actual issue but there was clearly some initialization problem with my installation of Reaper in conjunction with Helix Native. We anticipated that someone else might encounter this issue at some point. Please try the workaround described above (initialize Helix Native with another DAW) and let us know if it works for you.

[ppoceiro]

During beta testing I had a similar problem. Reaper v5.4 running under Windows 10 would consistently crash during startup whenever an instance of Helix Native was present in the Reaper project file. If there was no instance of Helix Native in the project file Reaper would start up normally but would then crash on the first attempt to load an instance of Helix Native. This behaviour persisted through several different beta software versions and several different uninstall/reinstall cycles of both Reaper and Helix Native. The problem was not repeatable by the Line 6 Beta Support team; it was definitely something unique to my installation.

 

The solution to the problem ended up being to uninstall Helix Native, download and install another DAW (we used the trial version of Sonar Platinum), Download and install Helix Native again, and then use the new DAW to launch Helix Native for the first time. This somehow allowed the Helix Native files to initialize properly. We closed the new DAW program immediately. Thereafter Reaper worked normally.

 

We never did track down the actual issue but there was clearly some initialization problem with my installation of Reaper in conjunction with Helix Native. We anticipated that someone else might encounter this issue at some point. Please try the workaround described above (initialize Helix Native with another DAW) and let us know if it works for you.

Hi!

Thank you for your feedback.

I'll try what you suggest. I already tried with two other VST hosts but not another DAW. It crashed with savihost and opened just a small little windows with Cantabile but no crash in this one.

If I understood correctly you used the other DAW just for the first time, for the registration process and then you used Reaper all the time with no issues? Is that it?

I'll give it a shot.

Thank you again.

I'll let you know if it works.

[silverhead]

....

If I understood correctly you used the other DAW just for the first time, for the registration process and then you used Reaper all the time with no issues? Is that it?

.....

Yes - that's it.

[ppoceiro]

Yes - that's it.

Success finally!!

I can't quite understand how I solved it.

I followed your suggestion. Installed Studio One. Crashed. Installed FL Studio. Crashed.

Then I installed Sonar Platinum Demo. And it worked!!

Perhaps it has something to do with firewall settings or Visual C++ 2013 Redistributable.

I noticed Sonar was the only one to install the VCRedis 2013. Since I have windows 10 it probably didn't install. But maybe it fix some faulty module.

Then I started opening other software and started receiving popups from windows firewall to authorize the connections from the software. 

It's like the windows firewall settings were resetted!

I noticed specially because I had Reaper blocked in the firewall with rules I created and those rules where gone.

I didn't even logged in in Sonar. The UI appeared. I closed Sonar. Opened Reaper. Loaded Native and immediatly the log in screen appeared.

 

So bottom line.

For those having problems you can try downloading VCRedist2013 from microsoft. I'm not sure if it this was the fix or even if it was this version that was installed so do it at your own risk.

If you don't want to risk it you can't try what I did and install Sonar. Again do it at your own risk. Worked for me despite loosing some firewall configs or those having been resetted. (the firewall is working normally in case you ask)

Hope it works for those having this issue.

 

Silverhead,

Thank you very much for your input. It greatly helped!

Hope you received a copy of Native for free being a beta tester!

If not you should have!

If you want I cant refer you when I reply this solution to the support ticket I opened.

Cheers

[bsg100]

​Awesome forum, great work...

 

I installed just the redistributable (VCRedist2013) from https://www.microsoft.com/en-gb/download/details.aspx?id=40784 and instantly resolved for me.

 

Cheers

[ppoceiro]

​Awesome forum, great work...

 

I installed just the redistributable (VCRedist2013) from https://www.microsoft.com/en-gb/download/details.aspx?id=40784 and instantly resolved for me.

 

Cheers

Glad to hear it! I'm gonna mark this as solved.

 

Just remembered...

Last week I did try this but did'nt installed the 2013 version. Tried with 2010and some other older version. Just bad luck I didn't insisted with this.

 

By the way.

Something happened to your windows firewall also? Did it started asking for permissions?

[duncann]

It's a bit disconcerting that a piece of software, whatever it is, is removing firewall rules without you're knowledge.

[silverhead]

Success finally!!

.......

Silverhead,

Thank you very much for your input. It greatly helped!

Hope you received a copy of Native for free being a beta tester!

If not you should have!

If you want I cant refer you when I reply this solution to the support ticket I opened.

Cheers

Glad it worked for you! Credit to the Line 6 Helix Native beta test support team. The lead guy on the Line 6 test team worked with me individually to resolve this for hours, even taking remote control of my PC during two different real-time phone/tech sessions, and eventually came up with the workaround in one of those moments of brilliance and insight. I remember him saying something like 'Hmm.... let's just try this for kicks'.

 

I had a suspicion that I would not be the only one in the world to face this problem when the public release hit the streets so I was kinda looking out for a thread like this.

 

As for the free copy of Helix Native..... I can't say.....😀

[LaurentJoulzy]

Hi.

Same issue here: msvcr120.dll missing. Also solved by installing Visual C++ Redistributable Packages for Visual Studio 2013, nothing more.

I think this thread should be pinned :)

[fflbrgst]

Sorry, but 'work arounds' are not anything but a temporary solution.  I use Reaper exclusively, no reason that I should have to install a different DAW to fool Native into working.  And if there are 'missing MS files', then L6 should have these (with prompts) ready during the installation process.

 

I also haven't seen a solution to the problem of having to be connected online to get the registered version working.  My recording computer is not online all the time - on purpose.

 

This reminds me of the bugginess experienced to update the Spider IV/FBV where Monkey would not recognize the devices - this never got resolved.

[silverhead]

Sorry, but 'work arounds' are not anything but a temporary solution. I use Reaper exclusively, no reason that I should have to install a different DAW to fool Native into working. ...

You're right. That's why Line 6 is working on a true fix for this. Since there is a workaround, and since the bug is not generally present and reproducibie in all Reaper environments (I believe I was the only beta tester who encountered it), this bug was not deemed a show-stopper in terms of the public release of Helix Native.

 

I don't know when a fix will be available but in the meantime people who encounter this issue can use the workaround while everyone else has Helix Native sooner rather than later.

 

(P.S. I see from another thread that the same workaround also seems to resolve a similar issue with Cubase 9 Pro, not only Reaper).

[ppoceiro]

Sorry, but 'work arounds' are not anything but a temporary solution.  I use Reaper exclusively, no reason that I should have to install a different DAW to fool Native into working.  And if there are 'missing MS files', then L6 should have these (with prompts) ready during the installation process.

 

I also haven't seen a solution to the problem of having to be connected online to get the registered version working.  My recording computer is not online all the time - on purpose.

 

This reminds me of the bugginess experienced to update the Spider IV/FBV where Monkey would not recognize the devices - this never got resolved.

 

 

You're right. That's why Line 6 is working on a true fix for this. Since there is a workaround this bug was not deemed a show-stopper in terms of the public release of Helix Native. I don't know when a fix will be available but in the meantime people who encounter this issue can use the workaround while everyone else has Helix Native sooner rather than later.

I agree with you fflbrgst.

But I have to stand with L6 also. It's like silverhead said. These were very rare situations by the few complaints this post had and from I gathered L6 couldn't replicate the problem for them to fix it.

And from the replies it's not necessary to install another DAW and this is not a workaround anymore.

The solution/fix is to install/repair Microsoft's Visual C++ Redistributable 2013. 

Windows normally already has this installed but in some systems it got corrupted somehow or with some files missing.

So it's not exactly L6 fault.

Anyway I agree they should warn about this issue in the installation notes or even force the installation. They already submitted this issue to the development team from what the L6 support guy told me in the ticket.

About the constant internet connection you are totally right! I also use Reaper exclusively and offline. Hope they find another way to authorize Native.

Cheers

[Triryche]

About the constant internet connection you are totally right! I also use Reaper exclusively and offline. Hope they find another way to authorize Native.

Cheers

 

You should not need a constant internet connection for the full license, just one time to authorize. I know some users are reporting otherwise. I have a hunch after the trial period expires it will be resolved. 

[klangmaler]

Trial period for the full license??

[...]

Helix Native needs internet...

[Triryche]

Trial period for the full license??

[...]

Helix Native needs internet...

Meaning if someone authorized the 15 day trial before purchasing and authorizing the full license, I think that may be causing the issue.

[klangmaler]

[dirkaxe]

I am using Helix Native with FL Studio and it crashes whenever I load Helix Native.  It is the trial version, but I need to know if it's going to work before I buy the full version.  I will say that the sound quality is not as good as my Helix floor pedal but I'm wiling to sacrifice a little for the convenience of having it in my DAW - only if it works!

 

[datacommando]

On 6/12/2019 at 6:33 AM, dirkaxe said:

I am using Helix Native with FL Studio and it crashes whenever I load Helix Native.  It is the trial version, but I need to know if it's going to work before I buy the full version.  I will say that the sound quality is not as good as my Helix floor pedal but I'm wiling to sacrifice a little for the convenience of having it in my DAW - only if it works!

 

 

Hi dirkaxe,

 

I don’t understand why you are saying the sound quality is not as good as your Helix Floor unit? Helix Native is the software brain that is in the hardware version - they are the exact same thing. Maybe you’re using a different monitoring system for the HXN plug-in and that’s why you perceive a difference?

 

Once again, I don’t understand this situation. It confuses me that you state that HNX is crashing FL Studio when it loads. Surely you must have had it function correctly or you wouldn’t be able to discern that Native, as you noted, has an inferior sound quality. What changed for it to stop working properly? What is different now to when it was working?

 

A little information may help.

 

Note: Line 6 are due to release version 2.80 of the Helix Firmware, hopefully in the next few weeks. The update is supposed to bring all the Helix range of products into line and a fix for these issues with Native should be resolved.

 

Regards

[wezmiy]

I have the same problem with Reaper crashing when I try to load Helix Native, and I too want to know that there is a fix before I take out my credit card. I run Reaper 5.981/x64 and Helix Native 1.80, on a fairly recent Lenovo notebook. Everything seems to work fine when I have just installed it, but when I switch off and then start things up again Reaper crashes when trying to load Helix Native.

[ppoceiro]

Hi!

Try repair/install  Microsoft's Visual C++ Redistributable 2013. 

Worked for me and a few others with an older version of Native.

If that doesn't solve the problem try to test Native on other DAW's.

Try to uninstall and reinstall Native.

Test an older version of Native.

 

[craiganderton]

FWIW 1.81 has so far ended my issues with Studio One and Cakewalk not loading properly and in some cases, crashing the programs.

[Inmate_001]

Has the same issue.  Tried the redistributable, tried repair installs of Reaper and Helix... yea it wasn't until I uninstalled native and reinstalled it that it started working.  I'm on the trial jfyi.

[CoredusK]

I've just experienced this when updating HX Native to v3.11.

 

The fix:

 

Rename/delete the following folder:

C:\Users\[your_username]\AppData\Roaming\Line 6\Helix Native

 

Open op your DAW and load HX Native.

It will not crash, but it will be factory reset.