Solved SpectraLayers with Studio One 7

[dominicperry]

EDIT: FIXED - See below for fix.

Does anyone have SpectraLayers 12 successfully working with Studio One 7.2.3 ?
I have ARA2 enabled in preferences, and I see the VST3 in the Effects tab in the browser, but I get an error when I drag it onto a track, and SpectraLayers doesn't appear anywhere on any of the Event or Audio menus (including right-click). SpectraLayers itself is working fine stand-alone and also in Pro Tools.

Error message is "SpectraLayers ARA SpectraLaters path could not be found"
I'm not clear what path it's looking for - as I said, works fine on its own and in PT, all paths that I can set in SL standalone prefs exist and make sense.

Any clues?

Thanks

Dominic

FIX:
Using plug-in manager inside Studio One, I located the SL plugin, right-clicked -> Show in Finder
This took me to a "ghost" folder inside the VST3 folder called ".vst3" which then had some package contents inside. I deleted this folder and restarted S1. All working now. I can only guess that the ghost folder was from a Trial version of SL or part of the odd install of SL11 which it did before upgrading me to SL12.
Just leaving this here in case anyone has the same problem.

 

[tremo]

Yes, I found this fix on the Steinberg forums. But when I installed the update to Spectralayers 12.0.40, I had to delete the invisible ".vst3" again. So it looks like SL12 is still installing that pesky file.

 

[Aragorn]

Please help! Unable to use SpectraLayers in S1 as well, but there's no "ghost" folder inside the VST folder. When I right-click on the SpectraLayers plugin in S1 Plug-in Manager and chose "Show in Explower" (Windows 10) - it points me to the file SpectraLayers.vst3 in this folder path: C:\Program Files\Common Files\VST3\Steinberg\SpectraLayers.vst3\Contents\x86_64-win - which seems to be correct.

I'm able to use SpectraLayers in Cakewalk but not in S1..... Please help!

 

[OutrageProductions]

Win 10 (and CW has had this issue as well) doesn't like a folder naming convention with an extension included.
Make notes before doing this, but in the above example remove the [.vst3] from the folder path name and try again.

 

[freddiphin]

I have issues with SpectraLayers but they are different than these. I mentioned them here in a discussion of ARA. And mine are with the version 12 and the latest Fender Studio Pro, so maybe that's part of it. SpectraLayers "shows up" fine but is all but useless in its ARA plugin mode in Studio One/Studio Pro. As I mention in the other thread:
For what it's worth, I have to update my perspective on SpectraLayers ARA in Studio Pro, based on much more attempted use now, to say that it is inconsistent at best and really basically unusable most of the time. It's "sluggishness" is really a dysfunctional breakdown of the interface between it and Studio Pro altogether. It (SpectraLayers) works beautifully in stand-alone, but only does its best to simply "show up" in Studio Pro.
I wouldn't know on whose side of the fence that the responsibility for this issue falls. Obviously PreSonus and Celemony have it figured out. I would think Steinberg would be up on it, but haven't gotten any useful help from Support there. I would also think that creating a "standard" (ARA) would mean that the interface/behavior would be consistent, certainly by this point and the ARA2 status of the protocol. But I am not a developer by any stretch.