Vienna Symphonic Library Forum
Forum Statistics

194,424 users have contributed to 42,920 threads and 257,967 posts.

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

  • Thank you Paul. I will give it a shot. I have to admit MIR PRO is very very expensive to spend close to $1100 for a reverb (with room pack). Spending this much money and not using all it's features I feel is too much. For example, I don't need the networking capability.

    What I do need is:

    a. The reverb being a vst plugin.
    b. Ability to add algorithmic reverb for the tail.


    I know the answer to a. What about b.? Can I add algo reverb for the tail (mimicking hybrid reverb)?

    Thanks,

    -N.

  • last edited
    last edited

    Hi,

    b) MIRacle is the included algorithmic reverb tail, tailor-made for MIR PRO!

    and

    c) There´s always MIR PRO 24, as a less costly alternative / way to get into MIR PRO step by step.

    Best,

    Paul


    Paul Kopf Product Manager VSL
  • Thank you Paul! That's great! So the way I work with reverb in my DAW, in general, is to create one reverb bus and route all my instruments to that one single reverb instance. So if I understand correctly, I can only route 24 audio signals to MIR PRO 24, right? If not, what is the exact limitation of MIR PRO 24? Is it I can only instantiate 24 separate instances?

  • [quote=nektarios]I need to get a new reverb, and I am not sure what to choose. First of all, I use Cubase 7.5, and I need a reverb that will act as a VST plugin, and I don't plan on using Vienna Ensemble Pro.

    There are three ways MIR Pro can be run:

    1. as a VST
    2. inside VE-regular
    3. inside VE Pro
    Routing MIR's wet signal (the reverb part) separately from MIR's dry signal (where instruments have all been positioned on the stage) requires (2) or (3).

    Using the MIR Venue Presets requires (3), which requires the addition of a license for VE Pro.

  • Thank you. So effectively, as a VST, I need a separate MIR PRO instance per instrument. Which will eat up a ton of my CPU cycles... :-/ Am I right?

  • last edited
    last edited

    @nektarios said:

    Thank you. So effectively, as a VST, I need a separate MIR PRO instance per instrument. Which will eat up a ton of my CPU cycles... 😕 Am I right?

    I haven't paid attention to the CPU effects, but I doubt you're right about that, because when you run it as a VST, each MIR VST you add isn't totally separate. There's a single MIR room, which I think VSL has called the "engine", and each track where you add a VST gets a little thing added, but it's just for communicating with the single MIR room. In the end, I doubt using MIR as a VST takes any more CPU than using it in VE.

    The Plug-In (VST) manual descibes it: "the plug-in version of MIR Pro relies on two different parts, namely the actual plug-in, and a common control user interface (UI) shared by all instantiated plug-ins."

    Looking in my Win Task Manager, I see just one Win 8.1 process for the MIR engine, while I'm using multiple instruments in VST MIR.


  • Great, that is exactly what I need then. I really don't wanna change my workflow and use VE just for the reverb...

  • To use a room pack, I need VE?? If so, this is a deal breaker then for me.

  • last edited
    last edited

    @nektarios said:

    To use a room pack, I need VE??

    You don't need VE to use the room packs.


  • Ok, thanks. So I guess a venue preset is something different (which you mentioned above).

  • last edited
    last edited

    @Another User said:

    "Venue Presets are the ideal starting points for your mixes in Vienna MIR PRO / MIR PRO 24, but they will also inspire you to use recording setups of your virtual instruments and ensembles that you may not have considered previously. Each Venue Preset is built around one Main Microphone position within a chosen Vienna MIR PRO / MIR PRO 24 venue and has been specifically created for a dedicated task with individual output formats, fine-tuned main microphone and secondary microphone positions, optimized room EQ settings as well as suggested RoomTone levels. Although some Venue Presets are set up as 5.0 and 5.1 surround configurations, great care has been taken to achieve perfect stereo balance and all-embracing stereo width."

    [url]http://www.vsl.co.at/newsletter/164/newsletter164_en_ROW.htm[/url]

    Using the Venue Presets does require a license for VE Pro, and it requires you to insert VE Pro in your workflow. Without VE Pro, you still can use the three MIRx presets, or you can still set up everything manually. 


  • Great, thanks!

  • What about the reverb options available with the Vienna Suite?  For half the price of the MIR you get some really nice verbs (algorithm verbs with the Hybrid in addition to a pretty sweet convolution reverb package) along with some other nice plug ins e.g. EQ's, Compressor, Multiband Limiter, etc.  All, of course, have some very useful presets that you can use out of the box or as good starting points.

    MIR might be overkill for you--it depends on your needs--in which case the Vienna Suite is just sweet. 

    Vienna Suite also has a free demo license to give it a spin.


  • I love VEPro and MIR Pro (VSL you can put a 100 euro in my account :) )

    Getting serious my life as change since I use MIR PRO and VE PRO.


  • Lol Cyril I know what you mean, MIR sort of like the first time I used a true legato library, but the placement equivalent.  It just felt like "this is the next big thing."


  • Once they sober up from their dimension-basses celebration it would be nice if they could make this not happen anymore.

    [IMG]http://i.imgur.com/wgJRyVd.png[/IMG]


  • Please send the crash-dump mentioned in the error message to , VSL's software engineers will look into it.

    TIA,


    /Dietz - Vienna Symphonic Library
  • last edited
    last edited

    @Dietz said:

    Please send the crash-dump mentioned in the error message to , VSL's software engineers will look into it.

    TIA,

    Submitted under Case 153816, cross-referencing Case 152951, where a dump-file was generated under similar circumstances.