Have you tried both the 32bit and the 64bit servers? The 32bit plugs won't show up in the 64bit server, so unless you have 64bit versions of all the above (most of which probably don't exist) you can only load them in the 32bit version.
DG
-
On a similar subject, I can see all my VST2 plug ins on the 32 Bit version, but can't see the 64Bit Kontakt 3.5 in the 64Bit version - all I can see is 64Bit VI. Do we know if Kontakt 3.5 64 is compatible? David.
-
On a similar subject, I can see all my VST2 plug ins on the 32 Bit version, but can't see the 64Bit Kontakt 3.5 in the 64Bit version - all I can see is 64Bit VI. Do we know if Kontakt 3.5 64 is compatible? David.
It is compatible and works fine. Please make sure you have assigned your VST directories properly in Preferences.
-
kontakt 3.5 (from 09.july.09) is in the same folder like the working RMX. its the component folder. but its installed in the vst folder as well.
actually - I can't see wether its a VST or a AU right? i supposed to find two folders for the two formats but there are'nt - right?
I reinstalled and updated Kontakt today - still the same.
-
Hi, Not quite sure why it worked, but I reinstalled everything and set up the folders from scratch (just the same) and now it works - I can see Kontakt 3.5. as a VSTi option in 64bit VE Pro. Happy to resubmit my next query as a new topic if it is too far from this subject, but... Assuming I add an instance of Kontakt (in Cubase 5) I will still just see VE Pro as my output option for a midi track - which gives me 16 channels to choose from. Within VE Pro I can have 8 or more midi 'plug ins' each presumably with 16 channels. As during playback it is Cubase generating the midi signals I can't really see a way that I can use any more than 16 instruments for each instance of VE Pro as there's no direct integration between Cubase and VE Pro that allows it to select between 'plug ins'. Is this an accurate understanding of the functionality? Thanks, David.
-
-
Hi, Not quite sure why it worked, but I reinstalled everything and set up the folders from scratch (just the same) and now it works - I can see Kontakt 3.5. as a VSTi option in 64bit VE Pro. Happy to resubmit my next query as a new topic if it is too far from this subject, but... Assuming I add an instance of Kontakt (in Cubase 5) I will still just see VE Pro as my output option for a midi track - which gives me 16 channels to choose from. Within VE Pro I can have 8 or more midi 'plug ins' each presumably with 16 channels. As during playback it is Cubase generating the midi signals I can't really see a way that I can use any more than 16 instruments for each instance of VE Pro as there's no direct integration between Cubase and VE Pro that allows it to select between 'plug ins'. Is this an accurate understanding of the functionality? Thanks, David.
For each MIDI port you have 16 MIDI channels. You can set up which MIDI port to use in the Inspector in Cubase. Assuming the you have told the server that you want more than 1 MIDI port (and you are using he VST3 version of VE Pro ///) they each have a number in the Inspector.
DG
-
It seems that I only have the midi channels available when I select '/// Vienna Ensemble Pro' and not when I select 'Vienna Ensemble pro x64' Does that mean I'm running VE Pro in 32bit to be able to have the midi channels (I have the 64 bit server running)?
-
It seems that I only have the midi channels available when I select '/// Vienna Ensemble Pro' and not when I select 'Vienna Ensemble pro x64' Does that mean I'm running VE Pro in 32bit to be able to have the midi channels (I have the 64 bit server running)?
When you say "have the MIDI channels" are you talking about the extra MIDI ports? If so, that is a feature of VST3, which is denoted by ///. It has nothing to do with 64bit vs 32bit.
DG
-
Don't want to make a confusing situation worse. But it seems when David isn't 'getting any midi channels' he is referring to when he uses the Vienna Ensemble Pro x64 standalone not the plugin. Which in that case, David, you wouldn't. You would have to use ipmidi or MOL to talk to it from Cubase.
And DG is correct, if you use the VST3 plugin inside of Cubase it defaults to 8 midi ports with 16 channels each.
-
OK - I'll try to clarify. When I choose a VSTi within a Cubase project (not stand alone) to add to a project, my installation of VE Pro gives me two potentials to choose from; '/// Vienna Ensemble Pro' and 'Vienna Ensemble pro x64'. If I choose the former I get however many midi ports I specified in the preferences of VE Pro server. If I choose the latter I just get 1 midi port (irrespective of the preference settings in VE Pro Server). My 32bit / 64bit question was prompted by, if the latter is called 'x64' - does that mean the former is not 64bit; and thus will that restrict the amount of memory available to me? - or is the memory purely handled by the VI and VSTi instances loaded within VE Pro and I should just use the '/// Vienna Ensemble Pro' one and stop worrying about it? I guess I just want to know the difference between the two versions of VE Pro Cubase is asking me to select between... Cheers, David.
-
OK, thanks Herb & DG - got it! (the x64 VST2 is the alternative because I've loaded CB5 64 - if I loaded CB5 32 I would get the 32bit VST2 as alternative - '///' VST3 will appear in both. (based on the VST folders I ask the two different Cubase versions to look in). I guess the alternative (64 & 32) versions are provided for users of pre VST3 versions of Cubase. Doh! David.