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
194,560 users have contributed to 42,922 threads and 257,976 posts.
In the past 24 hours, we have 0 new thread(s), 5 new post(s) and 108 new user(s).
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,
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,
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?
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,
@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,