Vienna Symphonic Library Forum
Forum Statistics

180,801 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 76 new user(s).

  • 5.0 Surround issue with 5.0 standard under MIR build 1719

    last edited
    last edited

    Hello

    MIR crashes when i choose it in the menu ouput and the software closes.

    Win7, QUad 3Ghz, 16Go, RME 96/32 + HDSPe AIO


  • Hi, this seems to be a problem, because I have the same effect. Any statements from Vienna Team?

  • Welcome and thanks for reporting, xiantropist ! We will look into it ASAP, of course.

    Which build of the MIR engine are you using? What's the OS? Please supply us with some details! :-)


    /Dietz - Vienna Symphonic Library
  • I'm using Windows 7 64-bit (as required ;-), but have to admit that I use an AMD 6 core processor, which doesn't meet the requirements. The Build is 1719. Besides I experience a lot of crashes with MIR - surround is just one trigger. Saving files causes crashes almost periodically. Is it possible that this is related to the AMD? If so that this problem will be temporarily, because I already build up a dual 6 core Intel based system. Maybe my problems will then belong to the past...

  • Yes, its very likely that your problems partly come from the fact that AMD processors are not actively supported by MIR. As you mentioned yourself, this is also explained in the system requirements ( -> [URL]http://vsl.co.at/en/211/497/1687/455/1666/1328.htm[/URL]). 

    Still it takes me wonder that you see crashes while saving, as this shouldn't be part of the issue - in fact we know about a few users that use AMD-equipped machines for MIR, without basic problems like the ones you describe. 

    Do you see any kind of error messages? If so, please just press Ctrl-C when the message window is on top, paste it and send us the text.

    Kind regards,


    /Dietz - Vienna Symphonic Library
  • Yes, you're right - these crashes have nothing to do with the subject. Sorry. But to answer your question: I only get a windows error message that MIR doesn't work anymore. No MIR generated message. The reason why I mixed up the subjects is that MIR shuts down this way when I try to use the 5.0 standard MIC as well... Kind regards, Oli

  • Sorry - maybe I wasn't clear enough about that: Of course, we look into those surround-setup related crashes, too.


    /Dietz - Vienna Symphonic Library
  • I tested the surround-setups that come with MIR (as well as a few hand-built ones) on my system and can't reproduce any crashes, or any other kinds of strange issues. Do you have some more details for me to look into?

    Thanks in advance,


    /Dietz - Vienna Symphonic Library
  • Unfortunately, I don't have any further details on that - sorry. MIR simply crashes. Now I have a new machine - 2 x Intel XEON L5640 - and experience same behavior, I'm afraid. When I just change the output MIC to Surround standard, MIR crashes imediately. No error message, no information. I know, this doesn't help, but I have nothing else, I could report. Hopefully, MIR 1.2 doesn't have this problem anymore ;-)

  • Hmmm ... :-/ ... just a wild guess: Does this happen with _all_ 5.0 Output Formats when you switch from stereo to surround? Could it be that you run out of RAM, as 5.0 needs almost 3 times as much RAM for IRs than stereo ...?


    /Dietz - Vienna Symphonic Library
  • No, I don't think so. I have 32 GByte of RAM. Should be enough, I guess ;-) But I tried around a little and found out that it depends on the setup. When I load an arrangement with only 9 instruments, ALL surround MICs work fine. When I load an orchestra setup with 35 instruments my system crashes with ALL MICs. But even with the big arrangement, my system tells me that I have more than 20 GByte RAM left. I hope this helps... :-/

  • Yes, that helps .... 32 GB is most certainly enough for even big arrangements.

    I _really_ tried to crash MIR with many output format changes (stereo > surround > stereo > surround) and can't reproduce the error. :-/ I had around 15-20 Instruments loaded on a 12 GB system, so in relation the load should be comparable to your case.

    For now, I suggest to upgrade to the new version 1.2 of Vienna MIR which will be available in a few days (maybe already tomorrow). If this doesn't help, I will ask our developers to get in contact with you directly.

    Thanks for your patience,


    /Dietz - Vienna Symphonic Library
  • Not to hijack the thread, but I noticed crash on save being mentioned and thought I would chip in with my observations.

    I'm using MIRse on a 920 i7 PC and periodically experience crashes when saving sessions (no matter size of session). Upon loading back up again I've noticed that sometimes MIRse would "corrupt" an instrument in the session, usually this being Kontakt4 (3rd party). The instrument is impossible to access/open and the only work around is to delete the instrument and make a new one + load the samples again.


  • Vagn Luv, thanks for reporting. Sorry to hear about that unpleasant issue.

    We can't really reproduce that problem here, but I just received a message from one of our developers that he has an idea what's causing it. I'll keep you posted.

    BTW - does this happen with MIR 1.2, too?


    /Dietz - Vienna Symphonic Library
  • Hi Dietz, regardless this thread is going a bit off topic - anyway, I have the absolutly same issue like Vagn Luv, since starting work with MIR in august. I reported it to vsl-support three weeks ago, but did'nt get back any message yet - maybe because the issue is a bit random. In my experience mostly the crashes on saving happens with using instrument- b a n k s inside kontakt, mostly after edit-changes of mic-position, volume-changes etc. - assuming it is a problem of kontakt 4 inside MIR. It is not so often or never happen with a single instrument in a kontakt instance. From the last crash I have a copy of crash report, regardless of this, in the WER-folder of Windows should be find any hang & crash reports, so if it helps for the developer, who has the genial idea, how to resolve the issue. I'm so hoping he an find the culprit! If it has to do with the setup - I'm on a Intel 1366 i7-980X@ 6x4GHz (Hyperthreading on), ATI-Grafikkarte, 24 GB, System on 750 GB Samsung HD (7200RPM) HD 2 & 3 SSD 256 GB 2.5", Windows 7 prof. I'm on MIR 1.2. since yesterday - same issue. double attack

  • Welcome Doubleattack,

    thanks for the report (I know, there are better reasons for writing a first message in a forum ... sigh).

    The observation that the crashes you and your fellow users experience could be related to the use of Kontakt 4 banks is indeed an important one - it could very well be that only single instruments were used by those who don't see this problem. Please send your crash-log to , with the subject MIR Crash Log for Dietz.

    We will investigate the case, that's for sure.

    Kind regards,


    /Dietz - Vienna Symphonic Library
  • Hallo Dietz, thank you very much for kindly welcome and instantly support! So I sent the reports to you. Hope they want help to find the reason for the issues. Kind regards, Frank

  • Just an update for the original topic ;-) I found out that my problems seems to depend on the venue I used. Mozartsaal crashes all the time, when I want to turn to the Surround MIC. If I take for instance ORF Studio 1 first, I can swith the MICs. After that I can even switch the venue back to Mozartsaal. And my setup uses 8 Gigayte of RAM. So RAM is not the issue here. Maybe this helps for the next step?

  • And yet another update. I tried different rooms and get fuzzy artifacts. I don't know how ro deal with them. Can I send an audio example to you in order to demonstrate the issue?

  • last edited
    last edited

    @xiantropist said:

    And yet another update. I tried different rooms and get fuzzy artifacts. I don't know how ro deal with them. Can I send an audio example to you in order to demonstrate the issue?

    Yes, of course - the best way to do this is www.yousendit.com . Make sure you upload an uncompressed audio-file (ideally 24 bit, ZIPed), not an mp3, as this would most likely confuse the artifacts you're experiencing with the format-inherent ones. 8-)

    Kind regards,


    /Dietz - Vienna Symphonic Library