Crystal Vst Plugin Not Working

Page 1 of 1

First, find the location of the plugin file on your hard drive. Plugin companies usually ask where you want to save the plugin (.dll,.vst, component) in the beginning of their installer. If you’re not sure where it saved to, try searching these locations below plugins often default to saving in these locations. PC: C: Program Files VSTPlugins. Load the VST plugin in FL Studio 20 Finally, you need to load the plugin in FL Studio to actually begin using it in your tracks. Navigate back up to the “ Add ” section of the menu bar. Within the drop-down list of plugins, you should now see your chosen plugin. These are VST / AU plugins with known problems in FL Studio, and the solution(s). The list is not complete, but we add problem plugins as we find them. If you have a plugin that you fixed a problem for, that isn't currently listed here, please report it in the Technical Support Forum and inform us about the issue so that we can add it to the KB.

  • Posts: 9
  • Offline
    • Posts : 9
    • Joined : Sat Apr 02, 2016 2:46 am
    • Has thanked:1 time
    • Been thanked: 0 time
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).
  • Posts: 3138
  • Offline
    • Posts : 3138
    • Joined : Tue Jun 09, 2015 12:21 pm
    • Has thanked:213 times
    • Been thanked:608 times
What's your version (Pro or Artist)?
OS: Windows 10 Pro | HW: P9X79 • i7 3930K • 16GB • 3x EVO 860 • NVIDIA GT1030 (@WQHD) • RME AIO
  • Posts: 9
  • Offline
    • Posts : 9
    • Joined : Sat Apr 02, 2016 2:46 am
    • Has thanked:1 time
    • Been thanked: 0 time
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.
  • Posts: 3138
  • Offline
    • Posts : 3138
    • Joined : Tue Jun 09, 2015 12:21 pm
    • Has thanked:213 times
    • Been thanked:608 times
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?
OS: Windows 10 Pro | HW: P9X79 • i7 3930K • 16GB • 3x EVO 860 • NVIDIA GT1030 (@WQHD) • RME AIO
  • Posts: 9
  • Offline
    • Posts : 9
    • Joined : Sat Apr 02, 2016 2:46 am
    • Has thanked:1 time
    • Been thanked: 0 time
Yes and yes.
  • Posts: 3138
  • Offline
    • Posts : 3138
    • Joined : Tue Jun 09, 2015 12:21 pm
    • Has thanked:213 times
    • Been thanked:608 times
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?
OS: Windows 10 Pro | HW: P9X79 • i7 3930K • 16GB • 3x EVO 860 • NVIDIA GT1030 (@WQHD) • RME AIO
  • Posts: 9
  • Offline
    • Posts : 9
    • Joined : Sat Apr 02, 2016 2:46 am
    • Has thanked:1 time
    • Been thanked: 0 time
Yes and the stock stuff works fine.
  • Posts: 3138
  • Offline
    • Posts : 3138
    • Joined : Tue Jun 09, 2015 12:21 pm
    • Has thanked:213 times
    • Been thanked:608 times
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?
OS: Windows 10 Pro | HW: P9X79 • i7 3930K • 16GB • 3x EVO 860 • NVIDIA GT1030 (@WQHD) • RME AIO

Crystal Vst Plugin Not Working Windows 10

  • Posts: 9
  • Offline
    • Posts : 9
    • Joined : Sat Apr 02, 2016 2:46 am
    • Has thanked:1 time
    • Been thanked: 0 time
I have not. I have to rename the 'Studio One 3' folder to 'Studio One 3 OFF'?
  • Posts: 3138
  • Offline
    • Posts : 3138
    • Joined : Tue Jun 09, 2015 12:21 pm
    • Has thanked:213 times
    • Been thanked:608 times
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.
OS: Windows 10 Pro | HW: P9X79 • i7 3930K • 16GB • 3x EVO 860 • NVIDIA GT1030 (@WQHD) • RME AIO
Crystal Vst Plugin Not WorkingCrystal
  • Posts: 9
  • Offline
    • Posts : 9
    • Joined : Sat Apr 02, 2016 2:46 am
    • Has thanked:1 time
    • Been thanked: 0 time
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?
Crystal Vst Plugin Not Working
  • Posts: 3138
  • Offline
    • Posts : 3138
    • Joined : Tue Jun 09, 2015 12:21 pm
    • Has thanked:213 times
    • Been thanked:608 times
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?
OS: Windows 10 Pro | HW: P9X79 • i7 3930K • 16GB • 3x EVO 860 • NVIDIA GT1030 (@WQHD) • RME AIO
  • Posts: 9
  • Offline
    • Posts : 9
    • Joined : Sat Apr 02, 2016 2:46 am
    • Has thanked:1 time
    • Been thanked: 0 time
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?
  • Posts: 3138
  • Offline
    • Posts : 3138
    • Joined : Tue Jun 09, 2015 12:21 pm
    • Has thanked:213 times
    • Been thanked:608 times
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.
OS: Windows 10 Pro | HW: P9X79 • i7 3930K • 16GB • 3x EVO 860 • NVIDIA GT1030 (@WQHD) • RME AIO

Crystal Vst Plugin Not Working Free

  • Posts: 9
  • Offline
    • Posts : 9
    • Joined : Sat Apr 02, 2016 2:46 am
    • Has thanked:1 time
    • Been thanked: 0 time
Ok thanks. I'm gonna download a x64 VST to see if my theory is correct. I'll post when I get a result.

Crystal Vst Plugin Not Working Today

  • Posts: 9
  • Offline
    • Posts : 9
    • Joined : Sat Apr 02, 2016 2:46 am
    • Has thanked:1 time
    • Been thanked: 0 time
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!

Crystal Vst Plugin Not Working 2019

Page 1 of 1

Who is online

Users browsing this forum: No registered users and 29 guests