-
MIR Not Responding when closing DAW
Ever since I upgraded to the latest version MIR Pro will not close when I close the DAW. It goes into not responding mode. Which means I have to "force quit" the application. I can confirm this on Cubase 7, Digital Performer 8 and Pro Tools 10. Anyone else having this issue? Galen
-
That setting was already checked. It crashes repeatedly, in fact since I updated to the most recent version performance has been terrible. If I click on the Audio setting page in DP ...the program hangs until I force quit MIR. Is the idea that we should print the tracks first and then use MIR just on the audio. I have the latest Mac Pro with 32 gigs of ram and a very fast PC with 64 gigs of ram (all SSD drives) and DS string with Orchestral Violas, Cellos and Bass can not really run with Mir Pro with the midi tracks. Galen
-
Same problem here, but still I'll have to check out some settings before I start to contact vsl support.
Frank
-
Hi Galen Weston,
sorry to hear about your problems. Let's go through them step-by-step, to make sure I understand you correctly.
First of all - I still don't know exactly whether you're talking about Vienna MIR Pro used as part of Vienna Ensemble Pro, or the plug-in version of MIR Pro. I assume it's the latter.
Furthermore, please tell us what OS-version you're using (you wrote that you're using a Windows-system as well as a Mac), and whether it's 32 bit or 64bit. Knowing your audio system could help, too.
I have the latest Mac Pro with 32 gigs of ram and a very fast PC with 64 gigs of ram (all SSD drives) and DS string with Orchestral Violas, Cellos and Bass can not really run with Mir Pro with the midi tracks. Galen
If the problem persists, please send a mail to to make sure that the issue gets the full attention of VSL's support team (the forum is mainly meant as a communication platform, not as an official technical support channel).
Kind regards,
/Dietz - Vienna Symphonic Library -
I am referring to the plugin version of MIR Pro.<> MAC OS is Mountain Lion 10.8.4 32 Gigs of Ram Windows is Windows 7 64bit. 64 gigs of ram all SSD Drives. I7 3930k My audio system has been Avid HD Madi with a System 5 setup. So Euphonix Madi AD DA converters. But Avid is garbage for running in systems other then pro tools. So I have most recently (as in the last 3 days) been using a simple RME Babyface. This has made DP more stable but no change in the MIR performance. Elincenser version is 6.5.4.2125. I am upgrading to the version that came out yesterday. They update this almost daily. DP version is 8.04 57602. I have just started using DP trying to get better performance because Cubase was chocking with Mir Pro as well but it is the same but I quite like DP. In a prior version of MIr Pro the program would close itself with out needing a force quit. The act of navigating to the Audio setting page in DP crashes Mir Pro. I then force quit Mir Pro and the audio settings page opens. I can not confirm that the previous version of MIR pro would close itself in DP because I just started to use DP. However previously it did close in Cubase 7 and after the upgrade it will not close in Cubase 7. So I can only assume the same behaviour in DP 8. The performance meter is near max in DP when MIR PRo is running drops to about 50 percent. If I remove it.
-
One more update.
I was running DP @ 96k. After all if I spent all this money to have 192 then why run at 48k?
That seems to have been the issue.
MIR Pro just closed itself when I shut DP. Performance meter is way down.
When I click on the Audio setting page it does not crash it just takes a while because I soon as the audio setting window opens. MIR PRO and VEpro close all the instances and re-opens them...that is probably a bug.
Any thoughts about the 96K? Should I not be able to run at that level?
Galen
-
I was about to write another answer (mainly asking about your latency settings), but I just saw your second message before I posted it.
I'll give it a try @ 96 kHz now. I can't test 192 kHz at the moment, though.
Thanks for your patience, I'll be back in a few minutes.
/Dietz - Vienna Symphonic Library -
I recently worked with 96 Hz too; it needs lot of more CPU power than at 44,1 kHz or even 48 kHz. Only 4 Audio instances at 96 kHz have a usage of 30% - 40% (X58, 12 core, HT on, Win7, using motu4pre interface).
But I think it's normal. I suppose the other problems with some crashs of MIR right now are related to huge projects; only some crashs on trying to delete a channel are weird, even some crashs on closing a project, mostly after changes of buffer settings during the work.
kind regards
Frank
-
It's true that 96 kHz is twice as demanding as 48 kHz. Still there should be _plenty_ of power on the systems mentioned in this thread.
I made a quick test with the sampling rate set to 96 kHz just a few minutes ago. I've been using OSX 10.8.4, Nuendo 5.5, RME HDSPe on an i7-3930K (3.2 GHz) with 32 GB RAM (1600). Graphics card is NVDIA GeForce 640. Both the system's and MIR Pro's latency were set to 1024 samples. I could easily run 32 instances of MIR Pro, with the VST Performance staying solid below 70%.
Click on the thumbnail to see the screenshot (then click a second time for full resolution):
[url=http://postimg.org/image/rxz5r7j5x/][img]http://s18.postimg.org/rxz5r7j5x/32_channels_of_MIR_Pro_96_k_Hz.jpg[/img][/url]
BTW - Nuendo closed without any issues, and so did MIR Pro.
Right now I can't see any problems related to MIR Pro, sorry to say so. Are there any other peculiarities we have to take into account? Other applications running simultaneously, network activity, etc. ...?
Kind regards,
/Dietz - Vienna Symphonic Library -
[...]
Any thoughts about the 96K? Should I not be able to run at that level?
FWIW: Personally, I think it doesn't make much sense to use 96 kHz for anything than delicate recordings of acoustic instruments with lots of harmonics above 20 kHz. If you ask me, I would use 48 or even 44.1 kHz day in, day out when working with virtual instruments. The processing power gained is worth it.
... yes, there _is_ a difference, and I can hear it, but (after over 25 years of audio engineering) the difference for me is always less than _one_ move of an EQ on a single channel could provoke.
Just my 0.02 € ... 😉
Best,
/Dietz - Vienna Symphonic Library -
Forum Statistics
195,367 users have contributed to 42,980 threads and 258,219 posts.
In the past 24 hours, we have 3 new thread(s), 14 new post(s) and 52 new user(s).