This tab seems to send me to the SL11 PRESETS folder. Shouldn’t it send me to the VST3 folder that contains my various VST3 plugins? This seems a negative course relative to RX that now allows use of VST3 plugins that are not iZotope plugins.
Unless you changed it on purpose, SpectraLayers 11 properly points by default to :
C:\Program Files\Common Files\VST3\ (Windows)
/Library/Audio/Plug-Ins/VST3/ (macOS)
Which are the official VST3 folders. So I’m not sure what you’re referring to here.
Robin, I think you will find that this drop down is stuck on the Presets folder. My System Pref are set to show the VST3 folder as you suggest… but SL11 drop down slot will only send you to the Preset folder.
And once that is opened you cannot select a VST3 plugin. It’s a loop that can’t be broken.
Indeed when I click Browse… it opens the Preset folder, that’ll be fixed in the next patch. However I confirm that whatever is written next to VST3 Path is the folder that is being scanned when you open the VST3 Effects module.
So if you see the proper VST3 path there, you’re all set:
Just to let you know my vst3 plugins are working fine in the Spectralayers 11 stand alone version.I havnt checked in ARA mode yet.I can view the vst plugins by category or by vendor as normal.The Vst path in the preferences is also correctly set to C:\Program Files\Common Files\VST3.
1 Like
Do you mean in the VST3 Effects module? Do you see them if you click the down arrow highlighted in yellow below?
MrSoundman, OK, that is something I did not see/know. And this does bring the VST3s to the VST Effects window. And I can save this as a Preset. This said, when I reopen SL, the GUI of the VST plugins do not open UNTIL I select the particular Preset and click on Preview. Is this normal behavior?
It’s more like in RX where the effect will be applied to the target selection like the other modules. In Cubase or WaveLab, the plug-ins are usually in the signal path, e.g. on a insert, send or main buss and are always “active”. Here, they are “applied” to the target, i.e. they are not in the playback signal path (which is why we need the preview button in order to hear the effect).
1 Like
Thanks for this explanation, Mr.Soundman. Another Q: If this is something that is applied to the audio signal/track stem (?), why, when stems are created (that have audio), why can’t we add a VST to the solo’d stem? And for that matter, why can’t I add a SL module like DeReverb to a stem? I get the message ‘No writable layer’ here when I hit ‘Apply’. Can I not DeReverb a stem by itself? I can add Gain, Normalize, or Reverse but the rest do not work. Is this normal behavior?
Thanks for your help here, BTW.
If you see the message “no writable layer” it means that you did not select the appropriate layer in the Layers panel, but instead selected a group layer or a muted layer.
If you see that message again, please post a screenshot of your entire screen.
Well, OK, my error here, I did not select the stem. I appreciate that this is all for the best and intended to make things foolproof, but I wish that SL would make the stem selection automatically if I had selected the ‘Solo’ button. Is there a setting for this?
@mr.roos when you solo a single layer, it gets automatically selected, so I suppose you had more than one soloed. Maybe the latest soloed should be selected, even if there’s already a soloed layer, would that make it easier in term of workflow ?
Definitely, Robin. In Cubase, if you’ve Solo’d various tracks and then chose to export a mixdown, the Stereo Bus would contain only those Solo’d tracks. Too, of course Cubase also gives you an option to choose which individual tracks you want to mixdown in that final Export/Mixdown pop up window which is also something SLP doesn’t have.
Since most of us here are coming from Cubase it seems a good idea to me.