Vienna Symphonic Library Forum
Forum Statistics

181,827 users have contributed to 42,187 threads and 254,606 posts.

In the past 24 hours, we have 4 new thread(s), 27 new post(s) and 46 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Routing different instances to a new one for mastering

  • Routing different instances to a new one for mastering

    M
    M
    Hi Is it possible to route the output channels ( masterbus ) to a new instance for mastering. In this way you don’t use the DAW. In my case Logic x I use a few instances. Thank you Mig
  • PaulP
    VSL Team
    PaulP

    Hi Mig,

    I assume you are referring to Vienna Ensemble Pro, and I'm afraid it's not possible for VE PRO instances to communicate directly with each other. You might want to set up your routing within your instances according to your wishes. 

    Best,
    Paul

    Paul Kopf Product Manager VSL
  • M
    M

    Thank you Paul

    I'm trying to use my cores optimal

    Mig
  • C
    C

    You can route it thru your DAW sequencer, set up a send from a VEP instrument channel to FX = Vienna Ensemble Pro Audio Input and send it. Doubtful this is a significantly better use of CPU if not the opposite but for certain things like an amp room I do this way. 

     

    I think optimal use of cores, if that's the goal a single instance is the better use case.
  • M
    M
    Thanks I will try! Mig
  • Dewdman42D
    Dewdman42D

    why do you need to send it to a different instance?
  • M
    M
    To group instances to the same output for example using limiters and compressors once
  • C
    C



    Me, I had reasons. First, organization; 1) the automation parameters in the VEP 6 paradigm for the instance essentially considered an external rack, were relatively few and appeared right at the top rather than where they will have in my ad hoc addition of things somewhere harder to locate.

    This is more or less obviated now in VEP 7 as the names for things appears in Cubendo instead of the parameter number, so I feel freer to put them in the order of appearance left to right. 

    2) the send levels then for a send to the instance were the objective '-inf' to the chosen Cubendo max, for me it appears as 6.02 (dB); vs for VEP 6 sends inside an instance, "0dB" was displaying as somewhere between .7 and .71 (ie., type .706 for 0dB) & everything relating to 0 to 1; and It was that different a look for me.

    This too is obviated by VEP 7 where most of it is now the objective values, it's the exact same look (except for a chinese-looking graphic for -inf now)

    and iirc copying a range of values from one to the other was not right.


    I should note that if you're going to do this, to print the result at all means this is an external instrument or effect to the host and it means Export in Realtime or you have nothing but an empty file, or if it's just a two-file that information is missing.
  • Dewdman42D
    Dewdman42D
    last edited
    last edited

    @Mig said:

    To group instances to the same output for example using limiters and compressors once

    But you don't need to put those into seperate instances for that.  
  • C
    C

    You can group channels, you can have a bus for parallel compression and send to it, you can establish a compression bus and place the channels you want effected in that bus...

     

    If you want to do as a DAW group does, do the latter but eg., the bus the group all resides in is just for a group send and send to the compression bus as a group if you want varying levels, ie., send behavior. There is really no reason to route it to and then from the DAW just for that.