Vienna Symphonic Library Forum
Forum Statistics

191,218 users have contributed to 42,789 threads and 257,330 posts.

In the past 24 hours, we have 2 new thread(s), 8 new post(s) and 42 new user(s).

  • The splash-screen can be opened from the command dialogue in MIR Pro's Main Window.

    Regarding the problem you're describing, it would be helpful to get a bit more information (OS, DAW Version, hardware etc.). In the meantime, please check if you see "Incoming Data" indicated in MIR Pro's Main Window when loading a project (i.e. the yellow arrow icon flashing at the top of MIR Pro's Main Window). This could solve your problem. :-)

    Kind regards,


    /Dietz - Vienna Symphonic Library
  • last edited
    last edited

    @Dietz said:

    it would be helpful to get a bit more information (OS, DAW Version, hardware etc.)

    I thought that was what signatures were for 😊 — EDIT: Oops, my bad, OSX version wasn't updated but now is...

    Thank you Dietz, I'll have a look at the main window and let you know what I see.


  • Ha, sorry about your signature - we don't see them when writing a reply (one of the peculiarities of VSL's forum engine ;-) ...). 


    /Dietz - Vienna Symphonic Library
  • last edited
    last edited

    @Talino said:

    Thank you Dietz, I'll have a look at the main window and let you know what I see.

    It's in the Options-pull down.


    /Dietz - Vienna Symphonic Library
  • last edited
    last edited

    @Talino said:

    EDIT: Oops, my bad, OSX version wasn't updated but now is...

    If the problem continues to bother you, I would kindly ask you to get in contact with support@vsl.co.at, as I have no machine with OSX 10.11 yet to reproduce your setup.

    Kind regards,


    /Dietz - Vienna Symphonic Library
  • OK, no problem. 

    Thanks a lot for your help (yet again...).


  • I get this in Console when my template loads, maybe it's related?

    15/02/16 22:17:49,739 Vienna MIR Pro[11272]: WARNING: The Gestalt selector gestaltSystemVersion is returning 10.9.2 instead of 10.11.2. This is not a bug in Gestalt -- it is a documented limitation. Use NSProcessInfo's operatingSystemVersion property to get correct system version number.

    Call location:

    15/02/16 22:17:49,739 Vienna MIR Pro[11272]: 0   CarbonCore                          0x00007fff93fa2c9b ___Gestalt_SystemVersion_block_invoke + 113

    15/02/16 22:17:49,739 Vienna MIR Pro[11272]: 1   libdispatch.dylib                   0x00007fff8747733f _dispatch_client_callout + 8

    15/02/16 22:17:49,739 Vienna MIR Pro[11272]: 2   libdispatch.dylib                   0x00007fff87477237 dispatch_once_f + 67

    15/02/16 22:17:49,739 Vienna MIR Pro[11272]: 3   CarbonCore                          0x00007fff93f2eb47 _Gestalt_SystemVersion + 987

    15/02/16 22:17:49,739 Vienna MIR Pro[11272]: 4   CarbonCore                          0x00007fff93f2dddb Gestalt + 139

    15/02/16 22:17:49,739 Vienna MIR Pro[11272]: 5   QtCore                              0x0000000100eebbd5 _ZN19QProcessEnvironment17systemEnvironmentEv + 34293

    15/02/16 22:17:49,740 Vienna MIR Pro[11272]: 6   QtCore                              0x0000000100ec0995 _ZN9QSettingsC2ERK7QStringS2_P7QObject + 37


  • Hi Talino, 

    I checked with our developers, the Gestalt message comes from OSX,  it should not cause any issues beyond the message.

     

    The issue you´re having with project loading is a different one - it would require reproduction. Please send your files as zip files to support@vsl.co.at, we´ll take a look asap. 

    Best, 
    Paul


    Paul Kopf Product Manager VSL
  • Thanks Paul. I'm waiting to be able to reproduce this myself before I send you the project, since it seems to be totally random for the time being. The only thing that's consistent is that when it happens, closing the project and reopening it immediately (without restarting Cubase) always fixes the problem. Maybe this happens on the first launch of MIR from within Cubase, but I'm not sure.

    If MIR keeps log files of what launched it and what it sent to it from the plugin perhaps I could have a look. As it is, when it happens I never see anything, I only see and empty venue.

    EDIT: P.S. This is only hapenning since my fresh install of El Capitan, never had this under Yosemite and have been using MIR for a long time before.


  • I am seeing the exact same issue with ProTools HD 12.4 on Mac (OS 10.9.5).

    Yesterday after installing the Mir update, my first session load in ProTools loaded Mir, but with an empty venue and no instruments loaded.   I had to restart ProTools and forceibly shutdown Mir and second time it loaded correctly.

    This morning I'm seeing the exact same problem - first load of my template in ProTools and Mir appears but the venue is empty and no instruments are showing.  I'm currently trying again to see if it loads second time.  This will become an issue if it happens all the time.

    Let me know what information I can provide to help resolve.

    Jules

    EDIT: Again, it loaded correctly on the second attempt.

    PS. This has only started happening since I updated Mir and VE Pro to latest builds yesterday.


  • last edited
    last edited

    @Trailerman said:

    This has only started happening since I updated Mir and VE Pro to latest builds yesterday.

    Yes, as I mentioned in my original post, this has happened since the MIR update, my fresh El Capitan install *and* the Cubase 8.0.35 updates, so I wasn't sure which was the culprit. Apparently you're using neither El Capitan nor Cubase so that rules out these two 😊


  • It's definitely Mir related.  Nothing else has changed on my system.

    Seeing the exact same issue today: first load of ProTools session, Mir loads but does not load a venue or any instruments.  Shut down ProTools, Force Quit Mir, reload ProTools and load session, and second time everything loads correctly.


  • Happened a few times more since yesterday, especially after fresh system restart. It happens not only when I load a Cubase template, but also when I open a work-in-progress project. For some reason the plugins don't send the proper info to MIR the first time. Closing and reopening the Cubase project always sorts this out.


  • last edited
    last edited

    Hi Talino,

    in case you didn't do so already, please take a look into this:

    @Dietz said:

    [....] please check if you see "Incoming Data" indicated in MIR Pro's Main Window when loading a project (i.e. the yellow arrow icon flashing at the top of MIR Pro's Main Window). 

    ... this would make clear whether MIR Pro is actually receiving (new) data from your host or not.

    Kind regards,


    /Dietz - Vienna Symphonic Library
  • Hi Dietz. Well, you've asked me this before and I didn't answer because I've looked everywhere for a yellow arrow in the main MIR window and couldn't find one... Most of the time I just get a white rotating "loading" icon at the upper left (the standard OSX "wait" icon), while the left side of the interface gets progressively populated with all the instruments.

    When the issue I have is happening, I don't get anything. Just a blank MIR window showing "Select a venue".


  • So you don't see this:

    Image


    /Dietz - Vienna Symphonic Library
  • Ah, definitely not. I just checked by switching as fast as possible to MIR (which loaded correctly). I've got the five static icons but not the yellow arrow. I don't even have the gray arrow, the last icon I have is "MIRx Mode". Probably a Mac thing, we don't like arrows as much as you Windows people :)


  • This icon should be visible whenever an existing instance of MIR Pro receives new "Engine Project" data (even on a Mac ;-) ...).  


    /Dietz - Vienna Symphonic Library
  • I trust you when you say that it *should* be visible. I don't think I ever noticed it, even before the last update, so I don't know if it *was* there before, but it certainly *isn't* there now...


  • I can confirm this has been happening regularly after every system restart (in the morning), probably also after a Cubase restart later. Further loading of projects while Cubase is running is working as expected.