|
Cubase VST question
|
View this Thread in Original format
| djbruuen |
i'm using SX3 and for some reason a number of my vsts haven't loaded up in the vst part of cubase. They're all imported to the right folder. I'm wondering if theres a way to manually insert them in?
thanks |
|
|
| daeus |
So theyre not appearing in the menu that appears when you click on an empty VST slot? - Check every menu to see its not hiding under a different name.
If they are cracked VST's you might have the odd one that dosnt install properly...try installing.. |
|
|
| djbruuen |
| actually to be more specific, i'm using the novation SL61 keyboard. All of the vsts actually show up, but the novation has an automap feature which creates seperate .dll's to wrap the plugins. The odd thing is some of those appear, and some don't, but they're all in there respected folders, So i'm baffled why they wouldn't appear. |
|
|
| Eric J |
| Make sure there isn't more than one folder on your system called Vstplugins. I had two Vstplugins folders when I did my initial install and I had to remove one to get VST software to default to the correct one. |
|
|
| MERiDiAN5i2 |
Go to the Devices Menu, select "Plug-in Information".
Make sure your shared plugins folder is set properly.
Also make sure the plugins in question are enabled. If a plugin fails to load properly on startup it will be unchecked to prevent instability. This is the check mark in the first column, which enables or disables the plugin.
Sounds like the novation wrapper isn't loading properly, so the VST is unchecked and doesn't show up in the available instruments list.
Personally, I'd avoid wrappers. Interesting that the novation product uses wrappers to get the key mappings in place... Is this the Novation Remote?
I assumed they'd have used a more intelligent method of dealing with the key mappings than a wrapper, which is a sure-fire way to cause host compatibility issues if not written properly. |
|
|
| djbruuen |
| quote: | Originally posted by MERiDiAN5i2
Go to the Devices Menu, select "Plug-in Information".
Make sure your shared plugins folder is set properly.
Also make sure the plugins in question are enabled. If a plugin fails to load properly on startup it will be unchecked to prevent instability. This is the check mark in the first column, which enables or disables the plugin.
Sounds like the novation wrapper isn't loading properly, so the VST is unchecked and doesn't show up in the available instruments list.
Personally, I'd avoid wrappers. Interesting that the novation product uses wrappers to get the key mappings in place... Is this the Novation Remote?
I assumed they'd have used a more intelligent method of dealing with the key mappings than a wrapper, which is a sure-fire way to cause host compatibility issues if not written properly. |
thanks for your suggestion! i noticed for some reason a lot of the automaps were not selected in the folder you told me to go into. Now i see everything, so problem solved :)
on a side note, why are you against wraps? i've never had a problem using any of them in cubase (other than this minor issue) and it making controlling any vst a piece of cake (using my old m-audio radium to program knobs was quite frustrating in comparison) |
|
|
| MERiDiAN5i2 |
Sweet! glad that helped :)
I generally try to avoid wrappers and middleware sort of pieces because of potential instability. Novation's wrapper might be very stable, I don't know because I have no firsthand experience, but in general I try to avoid software that's not essential, especially when it comes to 3rd party code that sits between two other pieces; ie a wrapper. These can be especially troublesome if they are flaky... Realize that I'm a bit anal when it comes to this sort of thing, it goes with too many eons spent testing code. :P
It's interesting they were disabled... Cubase might have considered them unsafe or they may have simple failed to initialize the one time you opened Cubase so they were never checked again, just disabled. As long as you don't start crashing now that you've manually enabled them it's all good :)
Good deal that it makes mapping so much easier! I agree, mapping out all the MIDI CCs to the synth's knobs is not a fun task. at all. Some VSTs are more friendly than others... For example some synths allow you to right click a knob, select midi learn, twiddle the control and it's all done. I've always thought this should be standard on all VSTs :) |
|
|
| jupiterone |
It's very simple...just run the setup and enjoy...it's an air summer release.
:wtf: :p |
|
|
|
|
