Helix Native Crashing on New Mac Studio After Migration - With Solution

[kmcnall]

Hello!   

 

I struggled mightily  with this problem, so I want to document it on a clean thread.   I'm grateful for those whio helped and tried to help with this issue.

 

Problem:   After migration to a new Mac Studio using Migration Assistant, Helix Native crashed my DAW hard with any access of the Helix Native Plugin.   Attempting to load any project already using the plugin also crashed immediately.

 

Ultimate Reason for Crash:   Helix Native's authorization process is not friendly to the Migration Assistant.   There does not seem to be a clean process for migrating to a new Mac.  I'm still unclear on exactly what happened and why.

 

Ultimate Solution:     Completely uninstalling and reinstalling Helix Native.   There is not a clean way provided to do this.  The following information was provided by Line6 on what needs to be removed to completely uninstall Native and whatever data file was the actual culprit.  Please use due caution before using this procedure:

 

Please look for and delete the following files:
/Library/Application Support/Avid/Audio/Plug-Ins/Line 6/Helix Native.aaxplugin
/Library/Audio/Plug-Ins/Components/Helix Native.component
/Library/Audio/Plug-Ins/VST/Line 6/Helix Native.vst
/Library/Audio/Plug-Ins/VST3/Line 6/Helix Native.vst3

Delete the following folders:
Folder 1:
/Library/Application Support/Line 6/Helix Native/
Folder 2:
~/Library/Application Support/Line 6/Helix Native/ - this folder is hidden by default. In Finder, from "Home" view, press Command/Shift/and Period to display the ~/Library folder. It will appear grayed out but able to navigate within it.

Once completed, download and install the latest version of Helix Native.  When you relaunch your DAW and access the Helix Native plugin, you may ore may not be prompted to log in and authorize.

 

+++++++++

 

Many tried to help me with this.  The tendency was to think my DAW (Digital Performer) was the culprit, so I installed Reaper and also tried to use Garage Band all with the same results.

 

If Line6 was still providing telephone support, this would have been resolved much faster.   Ticket support with 3-day turnarounds is tough.

 

I've made the following recommendations to Line56 to hopefully spare others this problem.

 

1)  If Helix Native is not friendly to Migration Assistant, let users know this, and provide a working procedure.

2)  Provide a complete uninstall program, with a means to save user data.

3). Change the authorization process to avoid this problem.

 

In the process of trying to resolve this, I did not run into a lot of people having this problem.   I don't know why they would NOT have the problem if migrating from one Mac to another, unless their strategy was to simply reinstall everything.    It may be that this occurrence was  an anomaly unrelated to the normal process.   

 

I hope this might spare someone else the time and trouble.!

 

Berst to all.

 

 

 

[crl713]

Thanks for this. Having the same problem after Migration Assistant. Native is too good not to have a comprehensive uninstall.

[chrissuddes]

Thanks for this. Worked for me, many thanks indeed for sharing

MacBook Pro M1, Monterey 12.6.1

 

[PierM]

On 7/20/2022 at 9:07 PM, kmcnall said:

Hello!   

 

I struggled mightily  with this problem, so I want to document it on a clean thread.   I'm grateful for those whio helped and tried to help with this issue.

 

Problem:   After migration to a new Mac Studio using Migration Assistant, Helix Native crashed my DAW hard with any access of the Helix Native Plugin.   Attempting to load any project already using the plugin also crashed immediately.

 

Ultimate Reason for Crash:   Helix Native's authorization process is not friendly to the Migration Assistant.   There does not seem to be a clean process for migrating to a new Mac.  I'm still unclear on exactly what happened and why.

 

Ultimate Solution:     Completely uninstalling and reinstalling Helix Native.   There is not a clean way provided to do this.  The following information was provided by Line6 on what needs to be removed to completely uninstall Native and whatever data file was the actual culprit.  Please use due caution before using this procedure:

 

Please look for and delete the following files:
/Library/Application Support/Avid/Audio/Plug-Ins/Line 6/Helix Native.aaxplugin
/Library/Audio/Plug-Ins/Components/Helix Native.component
/Library/Audio/Plug-Ins/VST/Line 6/Helix Native.vst
/Library/Audio/Plug-Ins/VST3/Line 6/Helix Native.vst3

Delete the following folders:
Folder 1:
/Library/Application Support/Line 6/Helix Native/
Folder 2:
~/Library/Application Support/Line 6/Helix Native/ - this folder is hidden by default. In Finder, from "Home" view, press Command/Shift/and Period to display the ~/Library folder. It will appear grayed out but able to navigate within it.

Once completed, download and install the latest version of Helix Native.  When you relaunch your DAW and access the Helix Native plugin, you may ore may not be prompted to log in and authorize.

 

+++++++++

 

Many tried to help me with this.  The tendency was to think my DAW (Digital Performer) was the culprit, so I installed Reaper and also tried to use Garage Band all with the same results.

 

If Line6 was still providing telephone support, this would have been resolved much faster.   Ticket support with 3-day turnarounds is tough.

 

I've made the following recommendations to Line56 to hopefully spare others this problem.

 

1)  If Helix Native is not friendly to Migration Assistant, let users know this, and provide a working procedure.

2)  Provide a complete uninstall program, with a means to save user data.

3). Change the authorization process to avoid this problem.

 

In the process of trying to resolve this, I did not run into a lot of people having this problem.   I don't know why they would NOT have the problem if migrating from one Mac to another, unless their strategy was to simply reinstall everything.    It may be that this occurrence was  an anomaly unrelated to the normal process.   

 

I hope this might spare someone else the time and trouble.!

 

Berst to all.

 

 

 

 

Man, I have to thank you for this! Lost 3 hours of my day because of that lollipop L6 authorization issue. I didnt do absolutely anything, just started with the DSP error out of the blue after a reboot, and none of the various suggestions around here worked out. Was going to give up 'til I've found this guide which worked perfectly. The core point here, at least for me, was to delete the two Application Support folders and reinstall.

 

Thanks again, and another big BOOOO for L6. Just hire better coders, jesus christ. I have a huge library of plugins from any kind of developer, and Native is the only one giving me these random problems (lost the count of how many DSP erros I've got since I use Native, and every time it's a different voodoo to solve it)