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.

GETTING CLOSE.... At MOTU's suggestion, I created a new account on my Mac. This account did what it was supposed to do when I launched DP and accessed the Helix Native Plugin: It asked me via a Line6 dialog to log in to my account to authorize. When I did, it pulled up the plugin! I repeated this success with Reaper, which also pulled up the now-authorized plugin. SO: The problem is a user-level setting related to authorization IN THE LINE6 sphere, since it happens to that users across DAWs. Waiting for Line6 to get back to me on that.

Hello again, and thanks you for your efforts. I'm in a bit of a box primarily created by the fact that Line6 is not provided support as they have in years past. I don't think there are that many Mac Studio users yet running this app. Since Reaper, Garage Band and Digital Performer all behave the exact same way I have no reason whatever to think it is Digital Performer or any DAW. I do believe that the issue is around authorization. Lien6 may concur as they did get back to me via email and suggested I deauthorize the computer, turn wireless off, and attempt to access the plugin. This produced the same crash. I had another plugin (Ozone9) that I had not authorized; it launched its authorization program from within DP as Line6 should and O Ozone worked fine. There may be a part of the authorization process that is crashing. Again, still in both M1 and Rosetta modes. If there are any Mac Studio users on this thread, love to hear from you. To conclude, I agree with you that other users may not be able to help unless they have the Mac Studio M1 Ultra Pro / MacosX 12.4 configuration. I'll post here if/when I resolve. Kent

Hey Datacommando: I downloaded and installed Reaper, and have had the EXACT SAME results as I've had with Digital Performer. Attempting to load Helix Native on a track produced an immediate hard crash and error report to Apple. This happened in native M1 mode and in Rosetta mode. I've completely uninstalled (manually removing "components" entry) Helix Native multiple times. Still parsing through your other suggestions, but that's an early report on Reaper. Kent

one thing I'm increasingly concerned about is the number of support applications that won't install at all, with messages from Apple stating "this application needs to be updated". This includes Line6 Updater and License Manager and others. I'm not even positive which of the utilities are still needed. As it pertains to this thread, Helix Native is an ACTIVATED product, but I don't remember how it was activated. It's not managed by Ilok, and none of the utiulities seem to want to activate it. In some ways, it behaves like a product that is not activated on this computer. Since Native still runs fine on OS12.4 on my older Imac (Intel), is it possible it simply is not activated??

Datacommando: Thanks very much for your reply. I'm chasing down what I can from the info you provided. I've used Helix Native for several years with Digital Performer, pretty much flawlessly. I have also tried to use 3.15 with Garage Band. While GB handles it a little more gracefully (it does not crash), it pops up a warning dialgo indicated Native is unstable and will cause system instability, and ALSO that GB has to lower its security level to use it. I've tried without success to get it working with Studio One. Since it worn't work either in M1 mode or Rosetta mode, I'm stumped. I unfortunately really rely on the plugin (and have used it in dozens of projects that I work with frequently) it's hard to be without. I'm not even beginning to consider running older versions of MacOSX on the Mac Studio. I'm certainly hoping to hear from Line6. Thank you again.

My apologies, I should have stated that the crash occurs in BOTH m1 and the Rosetta mode, it makes no difference. If I attempt to add the plug-in on a track it crashes; if I open a project that has Helix Native active on a track it crashes.

I've been a quietly happy Helix (Floor) and Native user for several years. While updating can be complex, I've always made my way through. I've recently purchased my first new Mac since 2015, the Mac Studio. I've slugged my way through dozens of updates and issues, but I can't find my way around a Helix Native issue. I've found that Line6 support is somewhat MIA, which is disappointing. I was on Macos 12.4 on my old Imac, and the current versions of everything was working fine. I'm launching my DAW with Rosetta as recommended for Helix Native. When Helix Native is present on a project or I add it to a track, it does a hard-core crash of my DAW (Digital Performer). I glean from the lack of information on M1 for Native that it is not supported, but Rosetta should be a viable solution. It's not. My Mac Studio is a maxxed-out config, M1 ultra, RAM, storage, etc. Any information appreciated, including anyone successfully running on any M1 machine.

I agree a stand-alone app is needed, if only for testing. Especially right now, when Native is not working with new Apple OS and HW, it would be really great to be able to see what's going on with the app independent of your DAW.

I also haver a Mac Studio M1 Ultra under 12.4. Whether running in M1 or Rosetta mode, Helix Native will not work with my DAW (Digital Performer(). It runs fine on my old Imac with the save Monterrey OS version (12.4). It crashes DP hard. I can't open any project using the plugin. Line6 is quite unreachable for support these days. I have opened a ticket with them. They do not really mention Monterrey support much that I can tell. I sincerely hope they are working to support the M1 and at least Rosetta for this important new Mac model.