Vienna Symphonic Library Forum
Forum Statistics

180,757 users have contributed to 42,140 threads and 254,362 posts.

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

  • Why VE PRO?

    Hi,

    I've read the list of differences between VE and VE PRO. However, I'm not sure I understand if VE PRO is only needed by people using a slave computer, or can be useful for people using a single machine. Support for third-party instruments, surround output, freeze channel (unloading instruments), full parameter automation – are these things necessary when working on a single machine, or in general in the everyday use?

    Paolo


  • Loading thirdparty instruments is of course great if you want to use them like your VSL-instruments in MIR. Yes you can also root their signal from outside into VE and MIR with it, but it is of course much easier to handle all instruments in the same way inside VE.


  • last edited
    last edited

    @PaoloT said:

    Hi,

    I've read the list of differences between VE and VE PRO. However, I'm not sure I understand if VE PRO is only needed by people using a slave computer, or can be useful for people using a single machine. Support for third-party instruments, surround output, freeze channel (unloading instruments), full parameter automation – are these things necessary when working on a single machine, or in general in the everyday use?

    Paolo

    Ciao Paolo,

    I'm almost always using a single machine, so I can share my experience and my reasons for using VE Pro, that is the perfect and effective integration of MIR Pro and other libraries in my set-up:

    - sometime I can create in my DAW (e.g. Cubase) set up mixing VSL and other virtual instruments, and still I can mix them in MIR Pro using the MIR Pro VST send plug-in. But then I'm linked to the project, and to the file format of the DAW.

    - In other situations, I find very convenient instead, creating the templates into VE Pro (with VSL, Kontakt and SWAM instruments) and integrating into VE Pro project the corresponding MIR Pro mix. That way one can send midi data from whatever application (Finale, Dorico, Logic, Cubase, Overture etc.) and have always the same sonic result, because you always send to the same virtual ensamble, saving the time of replicating the set-up in every application. 

    I also had the feeling that this second workflow is more CPU effective (maybe due to less VST audio and midi inter-application traffic) but I'm not 100% sure about it.


  • Thank you very much for your insights and suggestions!

    Paolo