
The 32-bit version of Studio One will only load 32-bit plug-ins. Studio One will only load 64-bit plug-ins into the 64-bit version of Studio One. "Run as Administrator" is the very first thing that I have tried. Right-click Studio One and choose "Run as administrator" when opening the program to determine if there is a possible permissions problem." In addition, I am running Studio One Professional, which I have already mentioned as well. If you have not noticed I have mentioned that I already tried resetting the blacklist. Press the "Reset Blacklist" button while you are in this window."
#32 LIVES CRASH WITH SOFTUBE VST PROFESSIONAL#
If you do not see the "VST Plug-ins" tab under the Locations tab, then you want to make sure that you have activated Studio One Professional or Producer or you have installed the VST, AU, and ReWire support add-on if you are running the "Artist" version of Studio One. You want to add the directory that you have your plug-ins installed to. Please open Studio One and go to Studio One>Options>Locations>VST Plugins and verify that you have the correct directory added to the list of folders that the program scans at startup. If you are still having a problem, try contacting the manufacturer of the plug-in for information about updates, compatibility issues with Studio One, or possible workarounds. Make sure that there is a white dot next to the plug-in, if it shows up in the list.ĥ. Please click the icon of the wrench in the browser window, at the top, right-hand corner of the window, to open the plug-in manager.
#32 LIVES CRASH WITH SOFTUBE VST INSTALL#
If you need to install a different bit-version of Studio One, you can do so by downloading the desired version from your my. account under My Products>Software>Studio One.Ĥ. If you loaded your VSTs from the c:\Program Files (x86) folder into Studio One under the "Locations" tab, this is more than likely your 32-bit plug-ins. Right-click Studio One and choose "Run as administrator" when opening the program to determine if there is a possible permissions problem.ģ. Press the "Reset Blacklist" button while you are in this window.Ģ. Below are some general troubleshooting steps to try.ġ. If they do, just click the dot to the left of the plug-in to make it white. Go into the Browser window and click the icon of the wrench. One thing you will want to check is the VST manager in Studio One 3. M-AUDIO Fast Track MKII (Package 6.1.12, Firmware: 0.3.0) So I know what the problem is, but I could not find a solution other than take the time to look for each dependency and find out where it was meant to be. I tried running depends22 on TSE808, where I found a big chunk of dependencies to be missing, but I looked everywhere for solutions to resolve all of them at once, to no avail. Again, my version of Studio One 3 is also 64-bit. The directory C:\Program Files\VstPlugins is still there on the list, and the 64-bit version of TSE808 is still in the same directory. I even went as far as reinstalling the program. The tech support representative from TSE told me to try using the plugin on Reaper, which I did, and it seemed to work flawlessly, given the fact that JBridge plugins had the word JBridge written in front of the plugin name on Reaper. So one of the things that I noticed with Studio One 3 圆4 is that there are a handful of plugins that it does not recognize, most notably the TSE808 圆4, which I ended up having to use the 32-bit version of instead via JBridge.
