Helix Native and Mac Studio Not Working - M1? 12.4? DAW? Rosetta? Native?

[kmcnall]

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.

 

 

[datacommando]

On 7/14/2022 at 9:02 PM, kmcnall said:

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.

Hi,

 

From the Release Notes for Helix Native 3.15

 

New Features in 3.15

Apple Silicon Support

Helix Native

The Helix Native VST/AU/AAX plug-in now natively supports M1 and newer Apple computers without Rosetta. NOTE: HX Edit software has worked with M1 Macs from day one.

 

Hope this helps/makes sense. 
 

 

[kmcnall]

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.  

[datacommando]

On 7/14/2022 at 11:32 PM, kmcnall said:

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.  

O.K.

 

Ah, now I have read through your post(s) again, and although this post is entitled - “Helix Native and Mac Studio Not Working - M1? 12.4? DAW? Rosetta? Native?”, hidden in the body of the post is a reference to MOTU Digital Performer.

 

As pointed out, in my prior post - Helix Native does work with Mac Studio M1 computers running Big Sur and/or Monterey OS.

 

There are many happy users out there, but the gremlins can get in. Have you considered that the issue may not lie with Helix Native, your Mac Studio or Rosetta, but possibly Digital Performer.

 

Also, there was this from an old thread regarding an earlier version of Native and Mark of the Unicorn DP.

Have you tried the solution offered in this thread from Customer Support.

 

You also posted in another thread on here, where user “boynigel” had issues with his Mac Studio and it was resolved via  Customer Support. Maybe you could quote him in the thread to see if he can offer any assistance.

 

Hope this helps/makes sense.

 

[AtticusFinch1987]

I'm having a similar problem. I have a MacBook Pro with M1 pro and am using Logic Pro running OSX Monterey. I have tried to load Helix Native with and without using Rosetta, and what I get is just a blank screen. The window opens and has me log into my Line 6 account, then the plug-in just has the Line 6 logo at the top, but none of the U/I that accompanies the app. I have deleted and reinstalled Helix Native, and restarted my computer, but every time it just has an empty window. I've owned Helix Native for a few years now and have never had a problem with it in the past. 

[datacommando]

On 7/18/2022 at 6:29 AM, AtticusFinch1987 said:

I'm having a similar problem.

Hi,

 

Try this - instructions in the post from user “guilhermebreda”. Note- especially the hidden folders!

 

Hope this helps/makes sense.

[kmcnall]

On 7/14/2022 at 4:35 PM, datacommando said:

O.K.

 

Ah, now I have read through your post(s) again, and although this post is entitled - “Helix Native and Mac Studio Not Working - M1? 12.4? DAW? Rosetta? Native?”, hidden in the body of the post is a reference to MOTU Digital Performer.

 

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.

 

 

On 7/14/2022 at 4:35 PM, datacommando said:

 

 

[kmcnall]

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]

On 7/18/2022 at 5:44 PM, kmcnall said:

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. 

Hi,

 

This is a cut n paste from a previous thread to save a lot of typing.

 

AFAIK - Helix Native can be run on 4 machines at the same time and should function in Demo Mode for 15 days then all you need to do is authorised the installed demo version with the license details from your account. You should find it listed under your Purchase History listed as Helix Native for Helix owners. Also check under Product Activations where you will find the Code needed to activate the full version.

 

On 7/18/2022 at 5:21 PM, kmcnall said:

I have also tried to use 3.15 with Garage Band. 

 

In an attempt to clarify this situation, I would advise that you download and install the latest version of one of the free DAWs available for your Mac eg: Reaper - make sure you have the correct one for your OS -available here:

https://www.reaper.fm/download.php

 

If it does not function with other programs, it could be that your installation is damaged, which would require a full clean out of all Line 6 software from your Mac. Please take note of the link I provided in my reply to “AtticusFinch1987” above, especially the notes about hidden folders.

 

From your posts, my guess something has screwed up on your new Mac Studio, and/or Motu Digital Performer - there are many others using the same hardware and Native without any problems.

Hope this helps/makes sense.

 

[datacommando]

On 7/18/2022 at 5:44 PM, kmcnall said:

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".

 

Hi,

 

This keeps coming up over and over - what you have probably encountered is an over zealous GateKeeper in the Apple OS.

You can bypass this by right clicking on the file and clicking “Open”. It will possibly warn you, but it will run. 

 

https://support.apple.com/en-us/HT202491
 

Hope this helps/makes sense.

 

 

 

 

[kmcnall]

On 7/18/2022 at 10:15 AM, datacommando said:

Hi,

 

This is a cut n paste from a previous thread to save a lot of typing.

 

AFAIK - Helix Native can be run on 4 machines at the same time and should function in Demo Mode for 15 days then all you need to do is authorised the installed demo version with the license details from your account. You should find it listed under your Purchase History listed as Helix Native for Helix owners. Also check under Product Activations where you will find the Code needed to activate the full version.

 

 

In an attempt to clarify this situation, I would advise that you download and install the latest version of one of the free DAWs available for your Mac eg: Reaper - make sure you have the correct one for your OS -available here:

https://www.reaper.fm/download.php

 

If it does not function with other programs, it could be that your installation is damaged, which would require a full clean out of all Line 6 software from your Mac. Please take note of the link I provided in my reply to “AtticusFinch1987” above, especially the notes about hidden folders.

 

From your posts, my guess something has screwed up on your new Mac Studio, and/or Motu Digital Performer - there are many others using the same hardware and Native without any problems.

Hope this helps/makes sense.

 

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

[datacommando]

On 7/19/2022 at 1:29 AM, kmcnall said:

I downloaded and installed Reaper, and have had the EXACT SAME results as I've had with Digital Performer.

Hi Kent,

 

I’m very sorry to hear that you are still having issues with your new Mac Studio and Native.

 

As you have now also discovered that you cannot get Native to work as expected in Reaper, and I know that many other users out there are running trouble free with identical configurations of hardware and software, my concern is that this is beyond the scope of fellow users in these forums. I would think that by this stage it would be something that needs to be resolved by Line 6 Customer Support, and the best recourse is to raise a ticket with them.
 

This is a user group who’s members try to supply peer to peer assistance where possible, though shared experience. Members of Line 6 staff do not monitor these forums and therefore will not be aware of your current situation unless you contact them directly. 
 

I have been using Macintosh computers since the Mac Plus and have seen them fail for the most unusual reasons. In the early days, a friend of mine who was an Apple Authorised Reseller, mentioned that on several occasions when he had taken a computer in to be serviced, the first thing that the technician would do was to drop the computer onto the counter top from a few inches above. He thought this was rather odd and asked why the engineer had done what he did. The answer it seems was that the chips inside the unit could start to creep out of their slots due to heat. Banging it thing on the counter was a simple trick to reseat the chips. I have known computers do some really weird stuff just because of badly seated memory chips. Not saying that’s what is happening in your case, but for the money you have invested in the machine, I would want a guarantee of perfect health.

 

Sorry, I haven’t been able to help you fix this problem. My only other suggestion would be to also pursue this with Apple, this is an expensive high spec machine, and as you pointed out you had no problems on your old model running OS 12.4. It could be that your new machine has gone rogue.
 

Hope this helps/makes sense.

[kmcnall]

On 7/19/2022 at 2:49 AM, datacommando said:

Hi Kent,

 

I’m very sorry to hear that you are still having issues with your new Mac Studio and Native.

 

As you have now also discovered that you cannot get Native to work as expected in Reaper, and I know that many other users out there are running trouble free with identical configurations of hardware and software, my concern is that this is beyond the scope of fellow users in these forums. I would think that by this stage it would be something that needs to be resolved by Line 6 Customer Support, and the best recourse is to raise a ticket with them.

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

[datacommando]

On 7/19/2022 at 5:11 PM, kmcnall said:

If there are any Mac Studio users on this thread, love to hear from you.

The one that I definitely know about is “boynigel”, who solved similar issues in the thread (link below)  -  but I believe you already posted in that thread. You could try quoting one of his posts to see if he replies, but AFAIK he hasn’t checked in here since he fixed his copy of Native.

 

 Hope this helps/makes sense.

[kmcnall]

 

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.

[AtticusFinch1987]

On 7/18/2022 at 11:45 AM, datacommando said:

Hi,

 

Try this - instructions in the post from user “guilhermebreda”. Note- especially the hidden folders!

 

Hope this helps/makes sense.

Thank you thank you thank you! Works great!