Vienna Symphonic Library Forum
Forum Statistics

194,682 users have contributed to 42,929 threads and 257,995 posts.

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

  • MIR Pro licenses

    Hi,

    up to this point I've been using only one Mac Pro for working with Vienna but now I'm thinking of expanding my setup with a Macbook Pro laptop. This is a new and unfamiliar world to me, so if I want to split my VE Pro (with MIR Pro) instances of my projects between two computers, do I have to buy MIR Pro a second time? I know VE Pro has more than one license automatically, so that's not a problem but do I have to install MIR Pro to both computers with individual licenses or can I somehow use my one MIR Pro license on both computers through LAN?


  • last edited
    last edited

    Hello Sami,

    MIR PRO comes with one license, so you´d need to get a second license for MIR PRO, or maybe get MIR PRO 24, which was created exactly for such scenarios.

    Remember: If you want to work in the same venues on both computers, the settings should be identical (there´s no automatic synchronization).

    Best,

    Paul


    Paul Kopf Product Manager VSL
  • So does the second license cost the full price of MIR Pro or is there a price for an extra license because I've already bought the plugin?


  • Hello Sami, 

    The prices stay the same, and MIR PRO 24 is half the price of MIR PRO, which makes it a great alternative for a second computer in our eyes. 

    Best, 

    Paul


    Paul Kopf Product Manager VSL
  • What's the price of upgrading MIR PRO 24 to MIR PRO?


  • last edited
    last edited

    Hi Sami,

    Here is the link to the MIR PRO Upgrade Information.

    Best,

    Paul


    Paul Kopf Product Manager VSL
  • Thank you Paul.


  • I hope I'm not ruining a good thing here, but it seems like you save thirty Euros by buying MIR24 and upgrading to MIR Pro over just buying MIR Pro.  Is that right?


  • Thank you for pointing us to this glitch in our price sheet, it has been fixed. 

    Cheers, Martin