Vienna Symphonic Library Forum
Forum Statistics

200,424 users have contributed to 43,198 threads and 259,083 posts.

In the past 24 hours, we have 3 new thread(s), 11 new post(s) and 82 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro (legacy)
  4. VE Pro Feature Request: Server Auto-Connect to Persistent Instances

  • VE Pro Feature Request: Server Auto-Connect to Persistent Instances

    O
    O
    It would be useful to have a tickbox in the Server plugin window (where you connect to instances) that lets you "Auto Connect" when the instance becomes available. As in, it continually searches the network, and when it finds the particular instance it's looking for, it automatically connects to it.

    Currently, when you load up a project file in your sequencer and you are using external persistent VE server instances, those external templates must be loaded before you open your sequence. Yes, you can load your sequence then manually connect to them but that can be very annoying and time-consuming when you use many VE connections.

    Say your external templates aren't loaded and you aren't aware of this, and then you open up a sequence file (which takes several minutes). Now once those external templates are loaded, in order to connect to their VE instances you have to manually connect each one - OR - reload your sequence. Both of which are frustrating and often time-consuming, especially for those of us with a dozen or more VE server plugins in a sequence spread across no less than five machines.

    My suggestion is: add the ability for a VE server plugin to automatically connect to the instance as soon as the instance appears on the network. This way, a sequence can be open, and VE's operation is much more elegant because you have the option of loading up your template and not having to worry about manually reconnecting it.
  • J
    J

    Logic user, yes?

    That's the problem... in VST3 or RTAS, we have multi-port VE Pro instances. So we can use 1 instance to achieve many, many, MANY ports of 16 channels each... it's one or 2 clicks per-server. Not an issue for RTAS or VST3 hosts.

    The idea of continually polling the network to me does not feel right...

    I think you are looking for some kind of "VE Pro server manager" that can auto-connect to all registered servers and instances, per host file, yes?

    Not knowing the Logic workflow of using many instances, maybe it's best to constrain this discussion to non-VST3 and non-RTAS hosts, since these formats really do not present this challenge??
  • O
    O
    I use Cubase.

    On the topic of a server manager, yes that would be great but I haven't gone as fas as requesting something like that. I'm just asking for an auto-connect feature. The VE plugins already auto-poll the network, it would be a very simple step to get them to just reconnect to their associated instance.
  • J
    J
    last edited
    last edited

    @Steffan Andrews said:

    it would be a very simple step to get them to just reconnect to their associated instance.

    Ah! But how does the host know which instance is which?

    There is a fundamental issue in how VEPro sees and connects to instances that must be addressed --- this is somewhat related to the couple/uncouple issue -- in my opinion, VE Pro needs to reinvent how it handles data management... for exactly the reasons you discussed in post #1. Check out this thread -- 

    http://community.vsl.co.at/forums/t/26431.aspx

    If you skip down to my posts maybe 3 or 5 down -- discussing file management questions...
  • O
    O
    It would be using the same identification it uses to auto-connect upon session open. Nothing there would change. My issue is that once the VE plugin is open, if it failed to find the instance that it usually connects to upon session open, it just sits there. What I'm asking for is "magnetic" association.

    If you let a dormant VE Pro plugin just sit open and watch the list of available network instances, you see it's constantly updated when there are changes on the network of VE servers. The network polling I'm talking about is ALREADY HAPPENING. So to take it one step further and auto-connect to its associated instance is a VERY simple feature addition imho.