Failed to connect to DSP engine 8201

[kim666mikkelsen]

I use Helix Native in Reaper DAW.

Every time I start Reaper with a project where Native i plugin I get the message "Failed to connect to DSP engine (Device has not been initialized properly. code -8201)

 

Then I have to deauthorize the computer an log in again and authorize the PC.

Restart Reaper and then it works.

 

Any help?????

[datacommando]

15 hours ago, kim666mikkelsen said:

Any help?????

Hi, kim666mikkelsen,

 

Good to know that you made it work for you - let’s hope that others try this and get their copy of Helix Native working properly.

 

Thank you for supplying the information.

[kim666mikkelsen]

He he he

 

It was no help, but a question.

I don't want to deauthorize/authorize every time I have to use Native - how can I avoid this??

[guitarchugga]

Hi guys, is there a fix for this please?

 

[datacommando]

3 hours ago, guitarchugga said:

Hi guys, is there a fix for this please?

 

 Did you try the suggestion above?

[gregb41]

I am having the same problem on Windows 10, using Cubase 10.5.  Helix Native  - 

"Failed to connect to DSP engine (Device has not been initialized properly. code -8201)

 

[datacommando]

10 hours ago, gregb41 said:

I am having the same problem on Windows 10, using Cubase 10.5.  Helix Native  - 

"Failed to connect to DSP engine (Device has not been initialized properly. code -8201)

 

Hi Greg, (and anyone else with this problem)

 

After checking previous posts it appears this particular error was initially reported way back in early 2018 with v1.5 Native - it looks like nobody ever bothered to report back here with the solution. 
 

I will echo the advice given by “soundog” in that old thread - Raise a ticket with support”. Oh... and it would be good if you could please keep others informed as to any resolution offered.

 

link:

Hope this helps/makes sense.

EDIT:

NOT SURE IF THE LAST COMMENT IN THIS THREAD HELPS - CHECK IT OUT!

 

 

 

Edited August 2, 2020 by datacommando
Additional info

[datacommando]

NOTE TO ALL - Not sure if this is connected to the issue in Helix Native, but...

This same error code is also known to occur on Helix hardware devices and the general opinion is that this seems to happen because of a “corrupt” preset which refuses to load. On hardware versions simply rebuilding the presets when “powering on” the unit might fix the “glitch”. Many people have complained about the amount of time it takes to run through the “rebuilding” presets after a firmware update, but it is a necessary task to make things work as they should. This was even more essential when the main “Core” of the Helix OS was changed in the v2.80 firmware. After that update, people also noted that if they loaded an older preset, or sometimes one from CustomTone, then the “rebuilding presets” routine would run again on the next power up. This is obviously needed to bring all the loaded presets in line with the latest firmware.
 

Helix Native doesn’t mention anything about “rebuilding presets”, which is rather odd as it is the same engine as the hardware, but all I can say is - “I hope you read and followed all the release notes with the 2.80 firmware regarding Native backup and restore”.

 

 

 

NOT SURE IF THIS HELPS

Note: the latest version Helix Native 1.93 (released 9th July) is available to download.

[supertonic_jack]

I can confirm I had the same problem with many reaper projects on my win 10 (both win and reaper on newest version of course). 

[datacommando]

8 hours ago, supertonic_jack said:

I can confirm I had the same problem with many reaper projects on my win 10 (both win and reaper on newest version of course). 

Hi,

 

You say that you “had” the same problem.

 

If so, does that mean you now no longer have this issue, and for the benefit of others - how did you resolve it?

 

[obi_long]

Hello Bias effects im done with this lollipop

[datacommando]

15 hours ago, obi_long said:

Hello Bias effects im done with this lollipop

First and last post and you scored a “lollipop”. Ah, well.
 

Anyhow, this is not an airport - there is no need to announce your departure.

[somebodyelse]

I get this error everytime the big Windows system updates come around eg. 21H1>21H2.

 

It's a PITA, but the de-authorising and re-authorising sorts it out (via L6 Auth Manager), but you have to go and log in to the site, as well and remove the previous Windows instance, IIRC.

 

Next time, I must try and remember to de-authorise BEFORE I do the update, to see if that removes the necessity to faff around on the website?

 

If so, then it becomes a 'nothing problem'.

 

I have a couple of other plugins that behave similarly, and if I don't keep on top of it, I end up running out of authorisations.

[xgman]

Same problem in mac OSX. re-auth and reinstall after deleting didn't help.  Failed to connect to DSP engine -8201. And Line 6 won't reply to my case request. Been a week.

[LetitLoad]

I had this issue many months ago and using the OP's solution worked for me. After that, the issue just "went away" for a long time, and now it has randomly returned for no apparent reason. Everything was fine yesterday, and then I log back into a project today and it has mysteriously returned. It's just annoying.