Please ensure Javascript is enabled for purposes of website accessibility Jump to content

Helix Native blank screen after 'authorizing'


rnodern
 Share

Recommended Posts

I get this after launching helix in my DAW. Any ideas?  :(

Fresh install of helix native. 

 

2017 Macbook Pro

i7, 16gb Ram 1TB hd

Catalina 10.15.6 

DAW - Cubase 10.5 Elements 64bit

 

I tried to add a screenshot - but the line6 forums don't work. Allow me to describe. It says "Hello Andrew" and just has the Helix Logo... 

Screen Shot 2020-10-18 at 4.20.33 pm.png

Link to comment
Share on other sites

3 hours ago, rnodern said: this after launching helix in my DAW. Any ideas?  :(


Hi Andrew,
 

There is another thread that mentions this happening.  See link below.
 

I don’t recall if there was ever a solution to this, but basically you may need to contact support and raise a ticket.


Read the post to see if there is any sort of a clue, or suggestion that might get your Native to function.

 

Before raising a ticket, try all the usual suspects:- firewall, re-install, etc., then you can tell Support that you have tried the self-help options.

 

IIRC, I read where someone had this happen, but managed to launch another DAW (Reason, Garageband) and HX Native loaded up and worked as it should without having to go through the authorisation procedure again. It was as if there was a glitch while authorising, and this cleared it. If you don’t have another DAW available to test this - you can download a free copy of Reaper which might blow the bugs of the bumper. Not sure if this “trick”will work with your Cubase, as there are also lots of threads on here that are specifically to do with Cubase and Native issues. Trawl through, you will find them.

 

Hope this helps/makes sense
 

 

Link to comment
Share on other sites

  • 4 months later...

I just fixed this issue by de-authorizing one of the extra devices I had even though I only had 4 out of 5 but this seemed to do the trick. 

When I signed back in that re-authenticated and seemed to work, only problem is it will burn one of the lifetime activation codes which sucks but at least i'm back in. 

 

Hope you found a way in or hope that this may help. 

  • Upvote 1
Link to comment
Share on other sites

  • 3 months later...
On 2/28/2021 at 6:35 PM, UnTimid said:

I just fixed this issue by de-authorizing one of the extra devices I had even though I only had 4 out of 5 but this seemed to do the trick. 

When I signed back in that re-authenticated and seemed to work, only problem is it will burn one of the lifetime activation codes which sucks but at least i'm back in. 

 

Hope you found a way in or hope that this may help. 

 

I am glad I found this topic before I freaked out too much.  I had the same problem after deciding to purchase Reaper and Helix Native yesterday.  I have reached my limit of authorized devices which I didn't realize.  I deauthorized all the older units that I had retired or had crashed.  Now everything is working as expected.

 

Thank you UnTimid and datacommando for the solution and thread for further troubleshooting.

 

Dennis

  • Upvote 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...