Note to myself: Not so fast!

I was mistaken, what I saw was not a special Vienne Ensemble VST3 dll but a none-dll that must serve some other purpose in VST 3 communication. So I'm back to square one, but I know from the picture shared by DG that what I want to see is possible. And I'm noticing some language in the Vienna Instruments manual that refers to the accompanying installation of Vienna Ensemble as VST3 compatible and makes it sound like no special installation option is needed.

So there's still something (in Cubase 7 I suspect) that is preventing things from looking my project like it does in DG's.

1. Have you uninstalled VE and re-installed?
2. Have you checked that the path to the VST3 version is contained in the list in plugin information (Devices menu in Cubase)?

DG

1. No. I'll have to do a reinstall this coming week if that's needed.

2. That's the thing. There is no evidence of a separate VST3 version for VE Standard (as opposed to VE Pro, where I read in an older thread that there is a dll file with "III" appended to the filename). VE Standard is part of the Vienna Instrument Standard installation. The manual for VI Standard specifically mentions that VE Standard supports VST3. It does not mention a separate dll file.

Hopefully I can get to all this tomorrow. Thanks again for all your help.

Okay,

I reinstalled Vienna Instruments Standard, which includes the reinstallation of Vienna Ensembe Standard. In my VST Plugins folder under VSL I now have the following files for Vienna Ensemble:

Vienna Ensemble.dll

Vienna Ensemble x64.dll

Vienna Ensemble x64.vst3

The first is the 32-bit version dll, and the second is the 64-bit version dll.

But the third is not a dll file at all. Clearly it is in some way related to VIenna Ensemble  64-bit and is connected with VST3 implementation, but what the relationship is, and what role the file plays is not explained.

When I open up the Plugin Information window the file name is listed as "Vienna Ensemble", the category is "Instrument", and SDK is "VST 3.02". Interesting that the file in my VST Plugins folder includes "x64" in the filename, but the listing here does not. Also listed as a separate file is "Vienna Ensemble x64" shown as a VST 2.4 Instrument, and this appears to be what is loading when I add instances of VE.

Anyway, when I open the VST Rack and see my options for inserting a 64-bit instance of Vienna Ensemble, all I see is "Vienna Ensemble x64," which is what I have been using all along when I insert instances of VE.

The plot thickens but still no answer.

Are you sure that the VST3 folder path is included in plugin list? By default the .dll usually goes into the Steinberg VST folder.

DG

Yes. Here's a screen print of the Plugins Information window:

Can we recap? At this point, what is your issue?

From that screeshot, the instrument you have selected on track 28 is routed to MIDI channel 10 on the second VEP port. That seems to be set-up correctly. You must be indeed using the VEP x64 VST3.

Thanks for the dialogue. I'm curious, what makes you say it is routed to the second PORT (caps for emphasis, not attitude)? From what I can tell It's routed to the second INSTANCE of VE Standard (not Pro), but there is no indication of MIDI port that I can tell.

My issue is still Cubase not presenting me with discrete MIDI ports for each instance of VE Standard.

Compare the options presented to me in the MIDI track output selection. You can see the numbers to the LEFT of Vienna Ensemble x64 representing the INSTANCE number.

With the options posted above by DG in this thread. You see the INSTANCE number to the left again, but now you see discrete PORT numbers to the RIGHT of Vienna Ensemble x64. And the instance number for each port is the same.

Here's a screen shot of the options presented to me for VSL when inserting a new VE instance into the VST rack.

First: I stand corrected. My mistake. You're indeed pointing to a second VEP instance, not a second port.

Second: That second post is exactly what I was writing you about. You see that very first VEP on the list? It seems to be non-x64. Well, it most likely is. And the infamous VST3 version you need. Try it and let know.

I'm double-guessing myself again. If it were VST3 it should have been marked up with the three slanted vertical lines, which that is not. It'd still try it to make sure though.

If you open the Steinberg tree on that VST Instrument window, do you see any instrument marked as VST3 (so with the " /// ")?

Well I tried your suggestion, and sure enough the new instance using that VE version changed my MIDI output options to include discrete MIDI ports. Thanks! I think. But that confuses me, because I know my VE installation included two versions, one 32-bit and one 64-bit. If I'm choosing the version that doesn't say "x64" doesn't that mean I'm choosing the 32-bit version? So does that mean I can not work with multiple VE MIDI ports unless I'm willing to sacrifice the advantages of 64-bit? It seems a strange choice to be confronted with. One would think x64 would be the more advanced option and not force you to lose capabilities.

You should be able to decide whether or not you connect to a 32bit instance or 64bit with the VE server Window.

DG

From what I've read I think the "three slash mark" version is only a VE Pro phenomenon.

I had actually mentioned all this in my very first post in this thread, which referenced to the very same process I'd just gone through...

http://community.vsl.co.at/forums/p/34384/217227.aspx#217227

I get the impression that is indeed a x64, just not clearly tagged. But as Daryl just mentioned, what really matters is that the VEP server you're using is the x64 version, and the VEP mframes hosted on it are x64. The plug-in on Cubase I view as more of a connector to pass MIDI and Audio data back and forth, probably not needing to handle any true 64bit operation. This all in rough terms. Hope it makes sense.

Okay then! My problem appears to be solved thanks to you fine gentlemen! I checked the server window and it indeed says 64-bit for the instance I just created. So it appears that the real problem so far as I was concerned was my confusion caused by the VE version naming convention adopted by VSL.

Thanks both of you for your patience and perseverance in leading me to a solution. And thanks to any other commenters in this thread.

Sorry that I didn't track you back then. I could have saved all of us a lot of trouble.