henr1e44a.netlify.app

I have been trying to get some VSTs working, but nothing I've done seems to work. I've put the VSTs in every folder from C:Program Files (x86)Steinbergvstplugins, C:Program Files (x86)Vstplugins, C:Program FilesSteinbergvstplugins, C:Program FilesVstplugins, etc. I have Studio One looking for VSTs in all of those files, but it won't show them. When I go directly to it in the browser and try to place it on the track, it won't place it. Studio One is able to read and open the following .dll files: Sonatina Timpani, REAPER (yes the DAW), and MPC Essentials (another DAW). Can someone help me?
BTW I am currently running Windows 10. I put Studio One in Windows 8 compatibility mode and run it as an administrator (did this whist trying to fix this).

What's your version (Pro or Artist)?

niles wroteWhat's your version (Pro or Artist)?

Pro.
I also installed the free version of Kontakt 5. That one appears in my 'browse' section.

So the location in Studio One > Options > Locations > VST Plug-ins contain the correct path(s) to where the plugins are installed?
Have you tried resetting the blacklist?

Yes and yes.

So to summarize: Kontakt, Sonatina Timpani, Reaper and MPC Essentials all show up under the Instruments Tab in the Studio One browser, but other VST's residing in the same directories don't show up under Instruments or Effects?
Do the stock Instrument (e.g Mai Tai) and effects (e.g. Mixtool) work as expected?

Yes and the stock stuff works fine.

Have you tried temporarily renaming %USERPROFILE%AppDataRoamingPreSonusStudio One 3 to 'Studio One 3 OFF' (when Studio One is closed).
This way Studio One will start with default settings.
What happens when you add the folder containing your VST's to the VST Plug-in location then?

I have not. I have to rename the 'Studio One 3' folder to 'Studio One 3 OFF'?

lild0za wroteI have not. I have to rename the 'Studio One 3' folder to 'Studio One 3 OFF'?

Yes the one in Roaming (when Studio One is closed).
If it doesn't solve it you can throw away the new Studio One 3 folder and rename the Studio One 3 OFF back again (when Studio One is closed) to revert to your current settings.

Didn't work. I noticed that the VSTs that do show up appear to be VST2. Do you think that may be it? Would its version (x64 and x86) matter?

lild0za wroteDidn't work. I noticed that the VSTs that do show up appear to be VST2. Do you think that may be it? Would its version (x64 and x86) matter?

x86 VST's don't work in x64 (and vice versa) without a bridge (Studio One doesn't have a native bit bridge).
Just to be sure it's not related to a service. Is the VST3 Plug-in Support service enabled in: Studio One > Options > Advanced > Services > I'll be carefull, I'll promise?

niles wrote

lild0za wroteDidn't work. I noticed that the VSTs that do show up appear to be VST2. Do you think that may be it? Would its version (x64 and x86) matter?

x86 VST's don't work in x64 (and vice versa) without a bridge (Studio One doesn't have a native bit bridge).
Just to be sure it's not related to a service. Is the VST3 Plug-in Support service enabled in: Studio One > Options > Advanced > Services > I'll be carefull, I'll promise?

It's all enabled.
I think the problem may be that the VSTs may be x86, as I'm running x32 Studio One. If that's the case, would I have to download a x86 version of Studio One (if one exists), download one of those 'bridges' you mentioned, or actively search for x64 VSTs exclusively?

32 bit (x86) or 64 bit (x64) is hard to say, because it a personal consideration.
If you are planning to use a lot of memory intensive VST's (libraries, sample players) now or in the future, it's always good to go x64 all the way because you'll need the memory.
Working with a bridge (like e.g. jBridge) is only recommended when there's absolutely no x64 alternative available for the VST you want to use.

Ok thanks. I'm gonna download a x64 VST to see if my theory is correct. I'll post when I get a result.

niles wrote32 bit (x86) or 64 bit (x64) is hard to say, because it a personal consideration.
If you are planning to use a lot of memory intensive VST's (libraries, sample players) now or in the future, it's always good to go x64 all the way because you'll need the memory.
Working with a bridge (like e.g. jBridge) is only recommended when there's absolutely no x64 alternative available for the VST you want to use.

I was downloading the wrong bit versions of VSTs. Although its a little annoying to go out of my way to find x64 VSTs, this has helped tremendously. Thank you for your patience with me!

I have been trying to get some VSTs working, but nothing I've done seems to work. I've put the VSTs in every folder from C:Program Files (x86)Steinbergvstplugins, C:Program Files (x86)Vstplugins, C:Program FilesSteinbergvstplugins, C:Program FilesVstplugins, etc. I have Studio One looking for VSTs in all of those files, but it won't show them. When I go directly to it in the browser and try to place it on the track, it won't place it. Studio One is able to read and open the following .dll files: Sonatina Timpani, REAPER (yes the DAW), and MPC Essentials (another DAW). Can someone help me?
BTW I am currently running Windows 10. I put Studio One in Windows 8 compatibility mode and run it as an administrator (did this whist trying to fix this).

What's your version (Pro or Artist)?

niles wroteWhat's your version (Pro or Artist)?

Pro.
I also installed the free version of Kontakt 5. That one appears in my 'browse' section.

So the location in Studio One > Options > Locations > VST Plug-ins contain the correct path(s) to where the plugins are installed?
Have you tried resetting the blacklist?

Yes and yes.

So to summarize: Kontakt, Sonatina Timpani, Reaper and MPC Essentials all show up under the Instruments Tab in the Studio One browser, but other VST's residing in the same directories don't show up under Instruments or Effects?
Do the stock Instrument (e.g Mai Tai) and effects (e.g. Mixtool) work as expected?

Yes and the stock stuff works fine.

Have you tried temporarily renaming %USERPROFILE%AppDataRoamingPreSonusStudio One 3 to 'Studio One 3 OFF' (when Studio One is closed).
This way Studio One will start with default settings.
What happens when you add the folder containing your VST's to the VST Plug-in location then?

I have not. I have to rename the 'Studio One 3' folder to 'Studio One 3 OFF'?

lild0za wroteI have not. I have to rename the 'Studio One 3' folder to 'Studio One 3 OFF'?

Yes the one in Roaming (when Studio One is closed).
If it doesn't solve it you can throw away the new Studio One 3 folder and rename the Studio One 3 OFF back again (when Studio One is closed) to revert to your current settings.

Didn't work. I noticed that the VSTs that do show up appear to be VST2. Do you think that may be it? Would its version (x64 and x86) matter?

lild0za wroteDidn't work. I noticed that the VSTs that do show up appear to be VST2. Do you think that may be it? Would its version (x64 and x86) matter?

x86 VST's don't work in x64 (and vice versa) without a bridge (Studio One doesn't have a native bit bridge).
Just to be sure it's not related to a service. Is the VST3 Plug-in Support service enabled in: Studio One > Options > Advanced > Services > I'll be carefull, I'll promise?

niles wrote

lild0za wroteDidn't work. I noticed that the VSTs that do show up appear to be VST2. Do you think that may be it? Would its version (x64 and x86) matter?

x86 VST's don't work in x64 (and vice versa) without a bridge (Studio One doesn't have a native bit bridge).
Just to be sure it's not related to a service. Is the VST3 Plug-in Support service enabled in: Studio One > Options > Advanced > Services > I'll be carefull, I'll promise?

It's all enabled.
I think the problem may be that the VSTs may be x86, as I'm running x32 Studio One. If that's the case, would I have to download a x86 version of Studio One (if one exists), download one of those 'bridges' you mentioned, or actively search for x64 VSTs exclusively?

32 bit (x86) or 64 bit (x64) is hard to say, because it a personal consideration.
If you are planning to use a lot of memory intensive VST's (libraries, sample players) now or in the future, it's always good to go x64 all the way because you'll need the memory.
Working with a bridge (like e.g. jBridge) is only recommended when there's absolutely no x64 alternative available for the VST you want to use.

Ok thanks. I'm gonna download a x64 VST to see if my theory is correct. I'll post when I get a result.

niles wrote32 bit (x86) or 64 bit (x64) is hard to say, because it a personal consideration.
If you are planning to use a lot of memory intensive VST's (libraries, sample players) now or in the future, it's always good to go x64 all the way because you'll need the memory.
Working with a bridge (like e.g. jBridge) is only recommended when there's absolutely no x64 alternative available for the VST you want to use.

I was downloading the wrong bit versions of VSTs. Although its a little annoying to go out of my way to find x64 VSTs, this has helped tremendously. Thank you for your patience with me!