I get the message SpectraLayers path not found in ARA
Any suggestions??
I’m getting the same error after updating from 12.0.20 to 10.0.30. I have no idea how to correct it.
Observations: After downloading the installer using the Steinberg Download Assistant, I selected install and got the below error. I then proceeded to manually install the update by just double-clicking on the installer file in the Downloads folder.
macOS Tahoe, Studio One Pro 7.
2 Likes
I have nothing but problems with the SDA when it comes to SpectraLayers Pro and just plain avoid using the SB helper apps with SL. I’d guess it doesn’t matter which platform.
For Cubase, the SDA has seemed to work well, especially with all the dependencies of Cubase.
1 Like
On a Mac: Try creating an alias to the SpectraLayers.vst3 plugin, and put it in Library/Audio/Plug-ins/ARA. (Command-Option-drag the vst3 plugin to the ARA folder.) That fixed it for me (so far….)
1 Like
Just opened a song in Studio One and got the error again. So I guess the alias method doesn’t work after all. 
2 Likes
Tahoe is still in testing, so no wonder why it doesn´t work yet properly, it may take time till it´s finished.
Never rush on OS updates..
That’s very true, but in my case I’m still on Sequoia (the latest, 15.7.1). Hmmm… still, it could either be a Sequoia update or the SpectraLayers 12.0.20 to 12.0.30 update.
2 Likes
Until so far thanks for the reactions on the SpectraLayers failure in ARA mode in Studio One 7 
1 Like
I’ve submitted a report to Steinberg tech support. I’ll report back with any progress.
2 Likes
OK, thank you very much Charles…
For now I will translate some Studio One songs to Cubase using dawproject format…
Regards Remco…
1 Like
2 Likes
I’ve tried the solution in the post but still the same problem, unfortunately
That is very strange, if you are using Studio One Pro and vst3 like me.
Yes, tried it several times, no result, still got the SPECTRALAYERS ARA path not found.
Studio One Pro 7
Spectralayers 12
Both latest updates…
I restarted a couple of times and did a plugin rescan again, now it works…
Thanks for the help and I apologize for the inconvenience.
Regards,
Remco Heemskerk.
Great to hear, Remco! It needed a deep reset 
1 Like
