Hey, Studio One is blacklisting over half of my plugins.
Everything is fine in Cubase, using most of these plugins since C5, all fine in FL and Ableton.

Just to name a few, reFX Nexus 2.2, Edirol Orchestral, KORG Legacy and Digitial Editions, Several D-16 Group plugins, Linplug Octopus, several Rob Papen plugins, Sylenth1...

arent they using the standard VST protocol? Any way to cheat myself to have them working?

 

Are you using the 64 or 32 bit Studio one? I have all those plugs and work fine in Studio one V3. If your running 64bit make sure your plugs are 64bit if they are 32bit you gotta bridge them with Jbridge.

 

how many Studio One threads you needs to make ?

maybe read the manual before ?

 

Latest Cubase versions features internal bridge between 32 an 64 bit plugins/instruments. In StudioOne3 it doesn't work like that..

 

What Evorax said. The way to use 32 bit plugins/instruments in Studio One is to either use the 32 bit version or use jBridge with the 64 bit version. Another possibility to why some of your plugins are being blacklisted is that they are causing problems. If a plugin crashes, Studio One will blacklist them so that the plugin doesn't crash the DAW. I doubt that that is the case here 'cause so many plugins aren't working. It's most likely that they're 32 bit and you're using the 64 bit version.

 

Yup. Gotta use Jbridge. I used a jbridge plugin with no issue 5min ago.

 

thanks guys.

 

which is the main reason i didn't like studio one. i forgot why i stopped using it and went to sonar. now i remember. total pain having to use bridging software in 2015. kinda shocked that presonus didn't fix that in version 3.

 

By mentioning "2015", maybe kind of shoking that plugins devs didn't made 32bit versions obsolete.
By "Jbridge", i have no problems whatsoever. Also, the 32bit plugs i use are like 2% out of all my plugins which are mostly 64bit.
Also, internal bridge in a daw may not work that well, even for a DAW like Cubase. Maybe that's the reason Presonus didn't implemented it in this new version, they relied on the fact that 32bit will become obsolete or that the users won't complain that some 32bit plugs didn't internally bridged well on the S1 x64 version and vice-versa. jbridge does a great job for the 2% of my 32bit plugins i own, so imo, why Presonus should've implemented a bridge which *for me* would've been only 2% handy? There are different opinions about it, but in the end we use what suits us best.

Have a great day and happy productions!

Evo

 

Maybe so, but why not install the 64 bit version of the plugin? I mean if you run a 64 daw, you have to run a 64 bit os so anyways you have reinstall everything. Why not do it right the first time?

 

Ah, I deleted the whole post anyway. Forget it... personally I use both, according to needs. I don't let the newest fad guide me, but needs. There's far too much fad in the world and too many people just following like blind and deaf sheep, so somebody has to say "fuck it" and "wake the fuck up" sometime. People here would be really surprised what professionals use to make music. Usually far more conservative than you think they use... it's not a priority of the newest and latest, but a priority of what works best.

 

I don't get your point. Using 64 bit software on a 64 bit os is the latest fad? It just appears like simple logic to me.

 

Yes, of course it's preferable to use x64 plugins in a x64 DAW in a X64 OS, of course. That means less problems. *yes*

But I still say if you don't *really* need it, better to avoid it. All this x64 fad has made a lot of people miserable. x64 systems are more unstable, in my experience. Could be due to W7x64 probably. I'm only referring to DAW systems, of course. Browsing and editing pictures and documents is of no interest to me. I use Linux for that anyway and so are majority of my clients, instead of VirtualBox browsing that I made them use a decade or so ago, since I simply refuse to install a bloody stupid AV on a DAW.

Nevermind, my mind works in mysterious ways.

 

Not every plugins is ported for 64 bit there is thousands of plugins that is only 32 bit especially old plugins

 

Hi Sinewave!

64bit may not be for anyone.. depending now on what plugins they use and if they didn't decide im the last years/months to switch everything to the x64 side. I know that some of them might concern about not being able to reopen old projects anymore, but at least they could've take an entire week to bounce all the old projects's stems and "preserve" them somehow and just move on to x64. There's a lot of legit users who afford all the 64bit versions of their plugins so basically there's no problems or too much "architecture mix" in their computer..
I know there's some discontinued 32bit loved plugs, but that's not a majority in this case.
Also... why all the 32GB of ram if we run a 32bit DAW into a 64bit O.S.? The only benefit of the whole ram would be that you could make music and keep other big programs opened simultaneously in the background or whatever in order to justify all the RAM capacity. I really have nothing against about musicians who still work in a 32bit daw with 32bit plugs as long as they keep making music and enjoy the process at the same time, but as we know everything just keeps moving forward, especially time and technology and we can't do nothing about it..

 

If you have both 32 bit and 64 bit plugins you should make a vst folder which ONLY have 64 bit plugins and one for ONLY 32 bit plugins you should also if possible install both version of the DAW in case of S1 i have both the 32 bit and the 64 bit installed

In the register you can edit the vst path so when a DAW search for installed Vst2 plugins they want find any.

In win 7 x64 you open run type regedit it will open register editor

HKEY_LOCAL_MACHINE/Software/VST = thats where the 64 bit default path key is located named VstPluginPath double click on that and you will see your default plugin folder path..

Now change that to anything you like that is NOT having any plugins installed
Now do the same for 32 bit it is located just above the VST in the folder called Wow6432Node/VST
I choosed C:/Program Files/VST but you can called a**hole if you like and on any drive you like (b.t.w i have all my vst2:s on a different hd aswell no need to fill up my system disc with vst plugins)..

But DONT do what i did the first time i tried that "trick" i left the location path empty in both Wow6432Node and VST in the registry so when i then open the DAW it searched my C: system disc for every bloody dll file
So be sure to make a fake location like i mention above.

Now when ANY DAW is opening it only scans for Vst3 then in your DAW preferences change to where you have installed your Vst plugins
Also BEWARE if you do that "trick" from now on when you now installing Vst the installer will in most cases go for the fake deafualt folder so if you click next next next without looking most plugins will be installed in the fake deafult location so ALWAYS look which FOLDER the installer is POINTING to it doenst take any more time than quickly click next next next like so many do nowadays

 

I can say that plugins is blacklisted in S1 doenst matter if it is 32 bit or 64 bit or even legit ones its almost Ableton Live warning when it comes to "working plugins" in S1.

 

what?

 

Depends now if the OP trully meant the "blacklisting" thing of studioone, which keeps the daw away from the crashing ones or... maybe if he meant about just the fact that he can't find in StudioOne any of the plugins mentioned, which is pro'ly a bridge-related issue.