I understand that there is a difference in the creation options, as you have clearly displayed (and as I clearly showed knowledge of in my first post).  However, once either is created and sits in your mixer, they are exactly the same in regards to functionality.  Have a look at my screenshot.  In it you will see a PLAY instrument I created, and then an Input and a Bus (which I titled so you can tell the difference).  Notice that the input and the bus have exactly the same settings (taking their input from the 2nd output of the PLAY instrument).  So it would seem to me, that regardless of whether I choose to insert an input or a bus, I get the same damn thing.  How am I wrong?

It most certainly is capable of that (taking an input from an instrument channel), which is why I posed my question.  Note that I am referring to VE Pro Server (v6).

I'm confused about memory usage of VE Pro and it's plugins (running as slave):

I have 48GB of RAM on a PC running Windows 7 Pro 64bit.

Currently with my template fully loaded after a fresh restart, the memory meter in Task Manager shows 27GB used. However, the "Physical Memory" box tells another story:  

Total 49111

Cached 23087

Available 21503

Free 18

(^all the above numbers adjust +/- a bit depending on what I click on).

So why does my total memory meter show only 27GB used (slightly over half), but I basically have no free memory?  Should I be concerned that I virtually zero free memory?  From what I read on general Windows forums the "Available" memory is memory that has been recently used but not "currently" in use... but it's not clear how that pertains to sample playback. 

so is that a yes?  lol

Aside from having certain settings definable upon initial selection, am I correct in the observation that inputs and busses in VE Pro (6) are exactly the same thing?  They look the same and can have the exact same settings...

Also, for what it's worth to anyone else having this issue -- I was just finally contacted by VSL support and they told me there is an additional thing you need to run called "VSL High Sierra Compatibility layer" which I can't find anywhere under my available downloads.  So you might have to request this directly from them.

2 restarts and a permissions repair evidently were required.  Plugins are found now... (sheesh)

I just installed the latest version of VE Pro 6 and the plugins are not being recognized at all by Logic.  All I see in the plugin manager is an old Vienna Instruments Pro (version 1.0.0).

In other words, the following are not recognized by Logic Pro's audio unit scan:

Vienna Ensemble Pro Audio Input.component

Vienna Ensemble Pro Event Input.component

Vienna Ensemble Pro.component

 

Resetting the audio unit cache scan does nothing.  Reinstalling VE Pro does nothing.

 

The combination of this bizarre incompatibilty with the lack of clarity on how to upgrade my existing VE Pro 5 licenses is really dissapointing guys.

Is anyone working in logic X on high sierra successfully with any version of VE Pro??

Hey I run a VE Pro server on windows 7 and I was wondering if anyone uses or specifically doesn't use indexing on their sample libraries?  Currently I have it off but I'm curious if it affects performance one way or the other with various sample libraries and instruments running in VE Pro server (namely kontakt, play, VE Instruments...)

 

Thanks!

Yes I also have this incredibly frustrating issue.  I have to force quit and restart the VE Pro PC before logic will release me from it's swirling beachball.

Am I completely missing something, or is it impossible to rename instances after they've been created?

I've found that just dragging the midi contoller from the automation list of midi ccs works just fine, fyi

any headway on this since you last posted?

Anyone here build their own PCs?  I assume it's fairly common here.  Anyway, just slapped together a 12 core Xeon Windows 7 64-bit rig and ran into the a pagefile issue (/question).  My system drive is a 128GB SSD, and I have 48GB of RAM, so after the Windows install was done I only had 30GB remaining on my system drive due to the default pagefile requirement.  I was curious if anyone knows a good setting of the pagefile size / location for a sampler rig.  From what I've read the pagefile is generally only helpful for debugging purposes (or when RAM is low), so I don't really want 48GB of my SSD being used for this purpose given both the limited size and lifespan.  As of now I've set there to be a small pagefile size on the SSD (per recommendations from other forums), and then a full size parition on another backup drive.

Curious of opinions?

Does anyone know if it's possible to run the server version of VE Pro alongside standalone instances on the same (mac) machine?

I don't have any issue using Play 3.0.15 in VEP 64-bit v4.1.8008 standalone.  I can load as much stuff as I want, and it doesn't load the samples more than once (even on re-opening of file).  It's still kinda slow, but once stuff is loaded it's fine.

running 10.6.7 on 4,1 2.66GHz Octo macpro.

sorry, I should have clarified -- I'm using it as standalone (and not using the server).  It appears as though I can just reselect the application from the start menu and it opens a new instance... i guess this is how its done?

I know how to create multiple instances on a mac, but can't seem to figure it out on a PC.  And my searches on this forum have come up dry.  I'm running windows 7 (64-bit).  Help!??

Hey,

I don't use/own VI Pro, but I DO use/own VE Pro 3 (use as 3rd party plugin host). Your most recent update (aug 27th) includes VI Pro in the startup file, and since I don't own this it has been subtracting demos from my USB key. Even when I load VE Pro from clicking a file saved without VI Pro in it, it still loads the initial startup set (master bus + VI Pro) briefly prior to opening the selected file.

The bottom line is that there was no mention of this in the update as far as I could tell, and as such I think it's VSL's responsibility to replace the demos used as a result as well as issue an update that removes VI Pro from the initial startup file. Or, alternatively, issue VE Pro 3 users a license for VI Pro.

Thanks.

From what I can tell from available online information, it is possible to run Logic 9 with a rewire app such as Ableton LIVE, as well as VE Pro standalones on the same machine (Macpro octo with 10.6).

Wondering if anyone can confirm this for me before I invest a crapload of money?