I've spent the last couple hours trying to figure this out and researching other posts and I decided to ask for some help. The instructions say to move the 'Softube' folder to a location and extract everything into it. Then there is a 'plugins' folder that has .7z files for each plugin. The demonstration .jpg called 'structure' shows the .7z files being placed inside of this folder with the rest of the files. There is an 'Existing Folders' .cmd file. I run it and it generates a .txt file. That .txt file mentions the AppData/Local/Softube folder, and the AppData/Roaming/Softube folder. I'm then supposed to run the 'Symlink Installer' .cmd, When I do that, I get a message that says 'You cannot install it on the system disk! Press any key continue'. When I press a key, it just closes.

When I take the actual plugin files out of the .7z zip folders, they will show up in my DAW but they don't work. But when I just leave the .7z folders as shown in the demonstration .jpg, they don't show up. I tried leaving the .7z folders alone but also extracting them to their proper places, and while my DAW will recognize them, they won't open.

 

I think those AppData folders contain all the big files. Sounds like softube folder is where you point those to so you can have the large files on a different drive. You still have to put the plugins into your vst folders. Then they look in the appdata folder where the symlink is which points it to the softube folder on a different drive. Probably just confused you.

I still don't know much about them but this guide helped me set some up.
https://www.howtogeek.com/16226/complete-guide-to-symbolic-links-symlinks-on-windows-or-linux/

 

For some reason, the Symlink Installer won't work if I run it from my C drive. I moved it to an external and it ran fine, but I want the plugins to be on my laptops SSD. I'll check out that link, thanks!

 

why are you installing with symlinks if you don't need it on a different drive? it sounds like you're just making things harder on yourself than it needs to be

 

With this particular plugin, the Symlink installer is the only one I've found. So Symlinks are only for installing on a different drive? I wasn't aware of that.

 

Last edited: Nov 25, 2024

What is the actual release title of it? without including any links.

 

the Symlink Installer can’t work on the system drive C: Move the whole Softube folder (including .7z files) to a secondary drive D: or E: Then rerun Existing Folders.cmd and Symlink Installer.cmd. For extracted .7z files, they shouldn’t stay uncompressed. Follow exactly what the demo.jpg shows. If your DAW sees plugins but they don’t load, try repairing permissions on the Softube folders

 

I got it to work, but none of the presets seem to be installed, Any idea how I can get the vst3 and aax versions to recognize them? Also, do I need to keep the Softube folder on my external drive for good?

The only issue I see is that one plugin says 'one or more sub plugins failed to load. Please re-install and make sure you have an active license on your computer.' It's only one plugin though and I can live without it.

 

Solution to the installation issue with "SymLink Installer.cmd"

If you're having the same problem I had when installing a plugin and the installer asks you to do it on a secondary drive, here's the solution that worked for me:

Open the SymLink Installer.cmd file with a text editor.

• You can use Notepad++, Notepad, or any editor you have at hand.

Look for the part where it checks the disk.

• To find it more easily, press Ctrl + F or Ctrl + B and search for a keyword like "disk."
• If not, you can read through the entire file; the check is quite high up.

Delete that part of the code where it checks the disk.

• Make sure not to touch the parentheses or any important structure so the code continues working properly.

Save the changes and run the installer as usual.

• The installation should now run without any problems.

(Optional) Delete the .zip files:

• Once everything is installed and working, you can delete the .zip files left in the installation folder if you want.

Limitations of this method:

• Using this method may cause some issues. One of the main problems is that the installer might not recognize the plugin type or its brand.

For any question contact me via instagram ;)