Vienna Symphonic Library Forum
Forum Statistics

194,169 users have contributed to 42,912 threads and 257,926 posts.

In the past 24 hours, we have 1 new thread(s), 12 new post(s) and 87 new user(s).

  1. Home
  2. Software
  3. Vienna MIR & Vienna Suite
  4. [VEPro] Empty VST List

  • [VEPro] Empty VST List

    G
    G

    I've just installed the new VE Pro on my host machine to give it a try.

    In the "VST Subsystem Configuration" dialog, I added the path where all my VST Plugins are located, but when I try to add a VST channel I get an empty list.

    I get:

    • a small, almost invisible square when I push the "Add VSTi" button in the bottom left corner of the interface or I select the "Channel -> Add VSTi" command from the menu. Obviously that small square is an empty submenu!
    • Nothing if I try to do the same thing by using the shortcut (CTRL+V)

    Restarting the program or the entire system doesn't solve the problem. I'm sure I'm missing something, but I don't have any idea about what it is!

    A list of plugins installed in my system: Addictive Drums, Kontakt, Lounge Lizard 3, BFD, Omnisphere, Stylus RMX, ABSynth. None of them shows up in the menu list!

    Any help is really much appreciated!

    Thanks,
    Luigi

    system configuration:
    Windows XP Pro 64 on a ASUS P5N32-e SLI motherboard with Intel Core2Duo E6600, 8 GB of RAM and a RME HDSPe AIO
  • D
    D

    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
  • G
    G

    I am so dumb! [:S]

    I've already said that I was missing something, haven't I? [:P]

    Thanks DG, as usual!
  • D
    D
    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.
  • M
    M
    last edited
    last edited

    @David Gosnell said:

    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.
  • D
    D

    I've got the same problem. I can see all my plugins in the 32bit version but exept my RMX there is noting in the 46bit version. especialy no Kontakt 3.5.025

    the fact, that I see them in the 32bit version should mean that there is nothing wrong with the dirictories - right?

    thx
  • M
    M

    As long as you have the plugins in the proper directories, with the proper architecures - VE Pro will pick them up. Apaprently you have RMX added properly. Kontakt 3.5 (x64) is seen perfectly fine here by the 64-bit version of VE Pro.
  • D
    D

    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.
  • M
    M

    If youare on Mac - there are not that many 64-bit plugins available at the moment...
  • D
    D
    last edited
    last edited

    @MS said:

    If youare on Mac - there are not that many 64-bit plugins available at the moment...

    ... but Kontakt 3.5 is - is'nt it? someone here using Kontakt 3.5 in VE Pro ON A MAC?
  • M
    M

    It is unfortunately not.
  • D
    D
    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.
  • D
    D
    last edited
    last edited

    Hey David,

    @David Gosnell said:

    I can see Kontakt 3.5. as a VSTi option in 64bit VE Pro.

    on a Mac?

    I realized that even the standalone Kontakt 3.5 does not work as a 46bit application in OSX - so I gave up...[:(]

    thx D
  • D
    D
    Sorry - should have been more specific: On a PC running 64bit Vista.
  • D
    D
    last edited
    last edited

    @David Gosnell said:

    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
  • D
    D
    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)?
  • D
    D
    last edited
    last edited

    @David Gosnell said:

    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
  • S
    S

    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.
  • D
    D
    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.
  • H
    H

     " ///" is the standard labeling of any VST3 plugin, which offers multiple ports, without the 3 lines it's a regular VST2 plugin which offers only one port.

    It's not related to 32 or 64 bits systems.

    best

    Herb