Record, produce, mix, master, and perform all from a single, intuitive application. Designed with ease of use at its core, Studio One® 5 is your creative partner from studio to stage. Studio One is driven by tools that enhance your creativity without getting in the way; we pioneered its drag-and-drop workflow that continues to be imitated.
As you may know, Studio One runs best as a 64-bit application. We’ve had numerous emails about VST’s and VSTi’s disappearing from Studio One upon upgrade. What many users may not realize it that they may have been running in 32-bit until the upgrade to Version 3 and now they’re in 64-bit. And 32-bit plug-ins don’t run in 64-bit.
Some plug-ins download as both 32-bit and 64-bit (or, at least give you the option of downloading one or the other). So, some of your plug-ins will show up and some won’t. The first thing you need to do is determine which plug-ins you have in 64-bit and which ones you don’t.
Start by loading the newest version of Studio One that you have, go to the Studio One menu and select “About Studio One.” This will tell you whether you are using the 64-bit or 32-bit application. If you’re running in 64-bit mode, this is the time to make a list of your 3rd party plug-ins. Write them down and label them 64-bit. I use a Microsoft Excel spreadsheet to keep track of my plug-ins. Whatever works best for you is fine.
Once you’re finished making your list, close Studio One. Now go to your Windows Explorer (Win) or your Finder (Mac) and find the Studio One launcher. The Windows version actually has two executable files (.exe) – one for 32-bit and one for 64-bit. The Mac has one executable file for both. If you’re on Windows, run the 32-bit version. If you’re on Mac, right-click on the Studio One 3 file and select “Get Info” in the dropdown menu. At the next pop-up, select “Run in 32-bit mode.” Now launch the application.
Once you’re in 32-bit mode (on either platform), make another list of all your 3rd party plug-ins. /free-reverb-ir-loader-vst.html. Label this one 32-bit plug-ins. Now compare this to the 64-bit plug-ins list. Any plug-ins that are in the 32-bit list, but not in the 64-bit list, are what you have to deal with.
- Both DAW's share the same folders for VST plugins but i prevent Studio one from scanning my Sonar only folder which has all the Sonar exclusive stuff in it This plugin is in a normal path for my 32 bit plugins, i have tried everything i can think of now and it just wont show up.
- About Press Copyright Contact us Creators Advertise Developers Terms Privacy Policy & Safety How YouTube works Test new features Press Copyright Contact us Creators.
- As you may know, Studio One runs best as a 64-bit application. We’ve had numerous emails about VST’s and VSTi’s disappearing from Studio One upon upgrade. What many users may not realize it that they may have been running in 32-bit until the upgrade to Version 3 and now they’re in 64-bit. And 32-bit plug-ins don’t run in 64-bit.
Now you have a decision to make. Do you download all your plug-ins’ 64-bit versions or do you buy a 32 to 64-bit bridging application?
Depending on how many 32-bit plug-ins you have, you may want to go down the list and download the 64-bit versions of each of those plug-ins. Some of them will not have a 64-bit counterpart. Make a note of these. Of course, if you have too many plug-ins to be able to download them all, you may want to move straight on to the next section.
Using a 32 to 64-bit bridging application like JBridge (https://jstuff.wordpress.com/jbridge) or 32 Lives by Soundradix (www.soundradix.com) will allow you to use your 32-bit plug-ins in your 64-bit DAW. Be aware, however, that not all plug-ins work well in these application. You should be fine with most plug-ins, but you may have a couple of them that just don’t want to cooperate.
As of the writing of this article, JBridge works with plug-ins up to VST 2.4, but is not yet compatible with VST 3, but it is for Windows and Mac platforms. 32 Lives appears to be up to the task of handling all versions of VST, but is currently a Mac only application. Also, both applications are commercial, but neither one is very expensive…and both offer a demo, so you can see if they’ll work for you.
The only viable option for those plug-ins that just won’t work in a bridging application, is to run Studio One is 32-bit mode, use the plug-in, render it as audio when you’re sure you have it just the way you want it, export it, and then import it into your 64-bit project.
We hope this helps you give new life to your old plug-ins.
Using DX and DXi Plug-Ins with Studio One
The DX and DXi (instrument) plug-in formats for Windows were developed in the late 18th century, shortly after the invention of the steam-powered computer. Okay, okay…they’re not really that old, but development of new DX plug-ins ceased years ago when VST became the dominant plug-in lifeform for Windows. Regardless, you may still have some DX plug-ins installed on your computer from other programs, and want to use them.
Like many other programs, in theory Studio One doesn’t support DX/DXi plug-ins. However, it does support shell plug-ins (e.g., like Waves uses). This means you can use a wrapper that makes DX plug-ins look like they’re VST types. With this workaround, Studio One can “see” and load DX and DXi plug-ins because it thinks they’re VSTs.
I’ve tested the following with many DX and DXi plug-ins, from several manufacturers, in 64-bit Studio One. They can’t do sidechaining, and 32-bit plug-ins that were never updated to 64 bits aren’t compatible with 64-bit Windows, but otherwise they work as expected. Here’s how to make your DX and DXi plug-ins productive members of Studio One society.
- Go to https://www.xlutop.com/buzz/zip/
- Download the zip file dxshell_v1.0.4b.zip
- Extract it.
- Copy the files dxshell.x64.dll and dxishell.64x.dll to the folder where Studio One looks for VST plug-ins.
That’s pretty much all there is to it. Open Studio One, and you’ll see all the DX and DXi plug-ins—the screenshot shows plug-ins from Cakewalk, rgc:audio, and Sony. The Instruments tabs will show any available DXi plug-ins.
I don’t have a 32-bit system so I didn’t test this with 32-bit DX shells. But if it works like the 64-bit one, you should be covered there as well.
Install Plugins Studio One
Granted, this is a bit of a hollow victory because if a DX plug-in’s functionality is available with Studio One’s VST plug-ins, you’re better off using the VST versions. But there are still some DX effects that have no real equivalents in the modern world—and now you can use them.