Vienna Symphonic Library Forum
Forum Statistics

180,802 users have contributed to 42,141 threads and 254,364 posts.

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

  • MIR Pro crashes Logic X

    Hi

    I'm on 10.15.5 and latest Logic

    When I use MIR it kills the logic session but MIR remains open. I can load a venue, but shortly aferwards it dies.

    Btw MIR always reports Software 6.5 build 18926 is available. I download & install it. Still reports the same?

    Error on crash:

    Process:               Logic Pro X [1094]

    Path:                  /Applications/Logic Pro X.app/Contents/MacOS/Logic Pro X

    Identifier:            com.apple.logic10

    Version:               10.5.0 (5283)

    Build Info:            MALogic-5283000000000000~2 (10T144)

    App Item ID:           634148309

    App External ID:       835637741

    Code Type:             X86-64 (Native)

    Parent Process:        ??? [1]

    Responsible:           Logic Pro X [1094]

    User ID:               502

    PlugIn Path:             /Library/Audio/Plug-Ins/Components/Vienna MIR Pro.component/Contents/MacOS/Vienna MIR Pro

    PlugIn Identifier:       at.co.vsl.audiounit.viennamirpro

    PlugIn Version:          5.4.16751 (5.4.16751)

    Date/Time:             2020-06-02 14:07:05.962 +0100

    OS Version:            Mac OS X 10.15.5 (19F96)

    Report Version:        12


  • Just tried using it through Maschine, using VST's and no issues. Even put a drum kit through it.


  • Hey James

    I had the same problem with MIR pro and Logic 10.5, it crashed constantly. To regain my workflow, I was forced to go back to Logic 10.4.8. It works fine now. I'm hoping for an update to fix this bug, either from Apple's or VSL's side (looking at you, long-awaited-and-for-2020-announced-major-MIRpro-update!).


  • Hey

    Thanks for the update, really appreciate it man. Saves me troubleshooting it any further.

    @VSL do you have a time frame on this potential fix?


  • FWIW  - MirPro seems to work fine for me using LogicPro 10.5 on Mojave.  So maybe this is a Catalina issue?


  • last edited
    last edited

    Could be! Maschine works though... I ain't got a clue to be honest 😶

    I'll retrieve a backup of Logic 10.4 and see how that floats for now.


  • Yes, used 10.4 and no crash. Save the project, opened again with no issues.

    Opened with 10.5 and bang within seconds


  • Hi James,

    sorry to hear that you're facing problems. I don't run Catalina on my machines, so I can't give it a try myself. Please get in contact with supportATvsl.co.at with a reference to this thread. VSL's Logic specialist Marnix Veenebos will look into it ASAP.

    Thanks for your patience!


    /Dietz - Vienna Symphonic Library
  • last edited
    last edited

    @Dietz said:

    Hi James,

    sorry to hear that you're facing problems. I don't run Catalina on my machines, so I can't give it a try myself. Please get in contact with supportATvsl.co.at with a reference to this thread. VSL's Logic specialist Marnix Veenebos will look into it ASAP.

    Thanks for your patience!

    Awesome mate, will do!


  • last edited
    last edited

    Quick update.

    Sent logs etc to support. I did find when/where this exactly happens, as it seemed random at first. It is as soon as you press play (spacebar) when the main MIR window is in focus. I even loaded an empty software track - loaded MIR plugin - raised the window - press play = crash.

    So, as long as you don't press play with that main window is open it's fine. I could add tracks etc. Even open the main GUI and move instruments, settings etc. Close the window. Press play and all fine. It's something when the GUI is open and you hit spacebar.

    See what they come back with. 👍

    edit: couldn't get this to crash on 10.4 using the above method. Every time under 10.5


  • I ran your test, also hitting play.....using 10.5 on mavericks...and it does not crash.

    I'm not meaning to challenge your assertion by the way, clearly something is broken, just trying to provide information that may help.  

    The OSX and LogicPro universe is complex with lots of different things going on..it could very well be that this only happens when using LogicPro 10.5 and only on Catalina, because the 10.5 version of LogicPro may be using something under the covers when run under Catalina (that its not using when run under Mojave) which is incompatible with MirPro.  If I had to guess it would be Metal vs OpenGL related, but that is a wild guess.


  • Yeah defo mate, I totally agree. I do agree that it looks like a Metal vs OpenGL related issue. Just weird how it works under 10.4... and under 10.5 as long as you don't have that window open and hit space!

    At least I can continue using it now albeit under caution.


  • Hi JamesH,

    This problem is currently under investigation - thanks for your patience!

    Best, Marnix


  • Hi everyone,

    Just wanted to mention that the newest Logic Update 10.5.1 didn't solve this problem.


  • Hey folks,

    Having the same issue. Running Logic Pro X 10.5.1 on an iMac with OS Catalina 10.15.5, and with Vienna MIR Pro 24 loaded into several plug in slots, Logic crashes immediately whenever I hit the space bar. MIR Pro stays open, but Logic just vanishes. Any sense of when this will be resolved. I'm a new VSL user; bought MIR Pro yesterday, so this is quite a disappointment. It has completely stopped my workflow. Thanks for any input or clarification of how to proceed!

    RWH


  • Just updated to Logic 10.5.1 on Catalina 10.15.4 and yes, opening MIR Pro will crash LOGIC within seconds. 

     

    - JM


  • So, I got a message from VSL confirming that they're aware of the Logic Pro 10.5 crash glitch. They didn't say when it would be sorted out, but apparently they're working on it now. 

    In the meantime, I did find a workaround because downgrading to previous versions of Logic wasn't possible for me (doing so deleted Melodyne ARA data). The trick is: I NEVER USE THE KEYBOARD FOR LOGIC COMMANDS WHILE THE MIR WINDOW IS SELECTED. I found that if I select the Logic Pro X window BEFORE USING KEY COMMANDS IN LOGIC, like for example, hitting the space bar to play the song, then there's no crash. I can then RESELECT the MIR window and do anything I want within it while the song plays. Then, BEFORE STOPPING playback, I RESELECT THE LOGIC PRO X WINDOW or else the application crashes. It's a pain, and I've made a misstep here and there, but I've found it workable in the short term. Can't wait for VSL to get this sorted, but hope this is helpful to people in the meantime.


  • last edited
    last edited

    @rwholloway said:

    So, I got a message from VSL confirming that they're aware of the Logic Pro 10.5 crash glitch. They didn't say when it would be sorted out, but apparently they're working on it now. 

    In the meantime, I did find a workaround because downgrading to previous versions of Logic wasn't possible for me (doing so deleted Melodyne ARA data). The trick is: I NEVER USE THE KEYBOARD FOR LOGIC COMMANDS WHILE THE MIR WINDOW IS SELECTED. I found that if I select the Logic Pro X window BEFORE USING KEY COMMANDS IN LOGIC, like for example, hitting the space bar to play the song, then there's no crash. I can then RESELECT the MIR window and do anything I want within it while the song plays. Then, BEFORE STOPPING playback, I RESELECT THE LOGIC PRO X WINDOW or else the application crashes. It's a pain, and I've made a misstep here and there, but I've found it workable in the short term. Can't wait for VSL to get this sorted, but hope this is helpful to people in the meantime.

     

    Thanks for this tip, rwholloway. I've decided to come back to Logic 10.4.8, it wasn't a big problem to me. Can't wait to get it sorted as well, I've put off Logic update until I could finish some projects, I guess it will take even longer before I get my hands on 10.5.1!  :)

    - JM


  • Cool! Thanks for posting this workaround. You're a lifesaver.

    VSL : PLEASE GET ON THIS!!

    Steve


  • VSL any update on this? It's been a few months now. I'm back on Mojave as there's no resolution, but I'd rather upgrade (I'll be 2 OS behind shortly). If there's no fix or plans to that's fine, at least I can either stay or move on and delete MIR. Thanks