Vienna Symphonic Library Forum
Forum Statistics

194,720 users have contributed to 42,932 threads and 258,000 posts.

In the past 24 hours, we have 7 new thread(s), 18 new post(s) and 110 new user(s).

  1. Home
  2. Software
  3. Vienna MIR & Vienna Suite
  4. VE PRO loopback workflow

  • VE PRO loopback workflow

    A
    A

    How do I run VE PRO on the same computer (Mac Pro) as DAW (Nuendo)?

    Should I use the standalone version or the server?

    what software is recommended for midi and audio loopback?

    should I run a 32 or 64-bit version under Leopard (10.5)?
  • D
    D

    You don't need to run the standalone. The plugin will work fine. You don't need any MIDI or audio loopbacks. that's the beauty of VE Pro. You just need to make sure that the "advertise on local network" box is checked.

    DG
  • A
    A

    thanks, I got it working. Still not sure about the 32 vs. 64-bit version with Leopard. Both seem to work...
  • D
    D

    The 32bit server is for 32bit VSTi. The 64bit server is for 64bit VSTi,

    DG
  • A
    A

    will I be able to use 16GB of memory using the 64-bit VE PRO under Leopard (10.5)?

    what happens if I use a 32-bit EQ on the 64-bit server (with 64-bit instruments)
  • D
    D
    last edited
    last edited

    @Another User said:

    what happens if I use a 32-bit EQ on the 64-bit server (with 64-bit instruments)

     

    You can't do this.

    DG
  • R
    R

    Is Standalone even possible (audio wise) on the same machine as the sequencer? I've opened it standalone. Then opened DP. But audio wise I don't see a way to connect them, unless I missed something. VEPro doesn't show any hardware audio outs. Ordinarily I loop a standalone instrument physically back into DP via adat/2408 banks B and C, but I can't see that I can do that with VEPro, and also that would further limit it over even the AU plug in version for DP. 

    (Advantage of standalone would be many more midi options, a much neater user interface with all the instruments in one VEPro mixer window etc, I use DP so the plug in is AU limiting it to 1 midi port per instance).

    So when using it on the same machine as the sequencer, it seems it's simply designed to be used as a PLUG IN. But with only 1 port (16 midi channels) per plug-in instance in the case of AU. (Another thread mentions VST and RTAS allows more).
  • C
    C

    Hi Rob,

    You can set the Audio Driver in the Preference menu. You´ll find how to proceed on page 9 in the VE Pro manual.

    Next to the Driver settings you´ll find a Tab called "Audio Routing". Go there and choose as many Outs as you want to loopback from VE Pro into DP.

    By clicking on the "Device Port" Tab all possible outs on your system appear. You can configure all Outs and also all Ins to your liking with naming, order and so on...

    VE Pro supports 256 Audiochannels at the moment. I use it with a SSL Dualhead madicard to loopback one madihead directly into Logic.

    So I have 64 outs from a VE Pro Standalone into Logic.

    best

    christianK
  • A
    A

    Rob and Christian,

    you don't have to use any loopback at all to use it on the same computer. Just open VE PRO Server first, then your sequencer (DP or whatever), in your sequencer load VE PRO Interface (as an instrument), click connect, select localhost and you're done.

    You don't need to use ANY channels on your card, it all happens in the box. 

    It is described in the manual as well.
  • C
    C

    Hi Abel,

    Thanks for you enthusiasm![:D]

    I am in the development team, so I already know about our software ;-)

    We offer the stanadlone version just because of what Rob said about the midichannels in AU plugins.

    It is really comfortable to have just one VE Pro standalone instance opened and have all instruments lined up like in a real written score. From Piccolo down to Doublebasses.

    So you dont have to open several instances with just 16 midichannels each.

    This has changed with VST3 but unfortunatelly not with AU yet.

    regards

    christianK
  • R
    R

    Thanks Christian. I had seen that in the manual at one point but couldn't access it in the actual software. I've now figured out that this was because at the time I had the instance (which I thought was standalone) operating under the server. My mistake, the options are clearly there when you open the standalone version! 

    I do understand about using it as a plugin absolutely requires no loop-back, its a wonderful thing!!. But as mentioned above, there is a use to have standalone as a handy option (my case as an example). Thanks!
  • S
    S
    How are you sending MIDI in this sort of setup?
  • D
    D
    last edited
    last edited

    @awarzocha said:

    This would allow you to run VEPro standalone and send back the audio to Logic/Cubase.  No other hardware has this function; not yet at least.

     

    Cubase doesn't need this workaround, as it can use VST3.

    DG
  • R
    R
    last edited
    last edited

    @skatz said:

    How are you sending MIDI in this sort of setup?

    Good question. I'm using DP's "interapplication midi feature". Go to "Set up" in DP, then "Interapplication Midi" and a window comes up where you can add DP MIDI OUTPUTS. I have about 8 ports created in there. Then these will appear in the standalone instance of VEPro. Works like a charm.

    (I'm very excited because I have now replaced 7 gigastudio machines and an older Mac, with just ONE 8-core mac doing it all. There is a bidule setup running under ReWire also (because I'm under deadline and that layout was already set up when VEPro arrived), and the standalone VEPro is running VI Strings, WW and brass. Altiverbs in DP everywhere etc etc, Recording 9 stereo tracks at once with video, CPU meters at around 1/4 to 1/3rd max, 10 gigs used out of 16, it's amazing).