Vienna Symphonic Library Forum
Forum Statistics

182,255 users have contributed to 42,214 threads and 254,732 posts.

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

  • VEP7 crashing when MIRPro is loaded

    Hello,

    I recently upgraded to new PCs and cannot use MIRPro without crashing my slave system.  Opening MIR is causing a bluescreen/restart.  These are the settings I have:

    • Master / MOTU PCI ASIO > Samples per buffer: 512
    • Slave / Preferences > Server > Multiprocessing 10 threads
    • Slave / Preferences > Vienna MIR Pro > Latency: 1024
    • Slave / Preferences > Vienna MIR Pro > Impulse Response Cache Size (GB): 4.0

    I am in quite a bind because after a couple of weeks of work I cannot even open my projects without crashing.  When I first set up my system, I was having this issue with MIR; I thought it was corrected after talking to VSL and manufacturer by changing latency settings (above).  Things had been stable for ~2 weeks.

    Now, with no changes to the system, suddenly I cannot open my work that contains MIR.

    I have narrowed this down to MIRPro with an empty project, with 1 track, will crash within a few moments (or sometimes immediately) of MIRPro being added either to VIPro or Kontakt in VEP.

    Has anyone else experienced this, or have suggestions?

    Is there a way to disable MIR from opening in VEP (without unistalling)?

    Slave

    • Windows 10
    • Intel Core i9-10900X 3.7 GHz
    • 128 GB RAM
    • VEP 7.0.1048

    Master

    • Windows 10
    • Intel Core i9-10900X 3.7 GHz
    • 128 GB RAM
    • Cubase 10.5.12
    • MOTU 2408MK3


  • By chance, are accessing the slave system using Microsoft RDP? There is a known issue with RDP/OpenGL and MirPro that crashes the system. I was also having issues, and I had to switch to VNC for remote access to the slave. My problems went away entirely after that. Good luck.

    Regards,
    Jason Todd Shannon


  • Hi Jason - thanks for the reply.  No, I have the slave with a monitor, etc to access directly.


  • last edited
    last edited

    @iainkelso said:

    Opening MIR is causing a bluescreen/restart.

    This usually indicates a hardware / BIOS / driver error. My guess is that the AVX-512 code used in MIR triggers it - Intel has had several issues related to this lately.

    To be able to tell more, please provide a minidump from the BSOD event.

    https://answers.microsoft.com/en-us/windows/forum/windows_10-update/bsod-finding-and-fixing-them/1939df35-283f-4830-a4dd-e95ee5d8669d

    Thanks,


  • Does anyone know if there is a way to disable the integrated MIR in VEP 7?


  • Hi, 

    If the license is not available, MIR Pro will not be shown. 

    Best,
    Paul


    Paul Kopf Product Manager VSL