Hopefully Presonus will change S1 to allow users to direct the path of the of where to store and read VST 3 plugins from (same as Reaper allow). At the moment I cant use VST 3 as S1 I have never been able to get S1 to read from any other location apart from the default C drive. I have all my plugins installed on another drive, so I am on VST 2..
https://www.steinberg.net/en/newsandeve ... -4727.html |
carolinem1 wroteHopefully Presonus will change S1 to allow users to direct the path of the of where to store and read VST 3 plugins from (same as Reaper allow). At the moment I cant use VST 3 as S1 I have never been able to get S1 to read from any other location apart from the default C drive. I have all my plugins installed on another drive, so I am on VST 2..You can create a hard link at the default VST3 location (c:\Program Files\Common Files\) to your custom VST3 location. That way Studio One will read the VST3's from your custom location. Example:
https://www.howtogeek.com/howto/16226/c ... -or-linux/ |
carolinem1 wroteHopefully Presonus will change S1 to allow users to direct the path of the of where to store and read VST 3 plugins from (same as Reaper allow). They probably won't as it's in the Steinberg specs to have a hard coded folder path for VST3. If you can define a path for Reaper then it's not compliant. Sonar used to have a custom defined VST3 path until they found out they were not compliant and they 'fixed" it by hard coding it. Yes the situation is entirety ridiculous however the buck stops with Steinberg.
Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb. Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental). Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths. |
Users browsing this forum: Anderton and 67 guests