194,108 users have contributed to 42,911 threads and 257,916 posts.
In the past 24 hours, we have 5 new thread(s), 16 new post(s) and 81 new user(s).
Thanks, works for me. It is of course worse to handle compared to a plug-in, because there is no total recall (you need to load the song in the host and the set-up in MIR parallely) and you need two third-party products to get it to work (a virtual MIDI cable and a mixing software of the soundcard vendor to loop back the audio).
Anyway, though, MIR crashes always the first time when I open it after having started the computer. After this, it starts without problems every time (until shut-down).
@am_wagner2000_25428 said:
[...] MIR crashes always the first time when I open it after having started the computer. After this, it starts without problems every time (until shut-down).
This is not the way it should be, of course. Do you see any error-messages?
@am_wagner2000_25428 said:
No, it just crashes during initialization.
Can you please have a look at the status messages of the splash screen and try to see what it says before the crash happens?
Or does it crash after the splash screen is gone and the MIR window already showed up?
Thank you, Florian
It crashes while the splash screen is there - it says "Loading default project..."
I tried to use the ReaRoute ASIO driver (from Reaper, both x32 and x64 installed) to route the audio data directly to Reaper, but MIR does not show the ReaRoute ASIO driver in the ASIO menu (in contrast to all other stand-alone applications that are available, like NI stand-alone synthesizers and so on, which show ReaRoute in the ASIO driver selection). It shows only RME Hammerfall ASIO and the Generic Low Latency ASIO driver...
MIR still crashes the first time I load it after start-up.
Further, it crashes everytime when I start MIR **AFTER** I have started Reaper. It works when I start MIR **BEFORE** I start Reaper.
Further, it crashes everytime when I start MIR **AFTER** I have started Reaper. It works when I start MIR **BEFORE** I start Reaper.
Which audio interface do you use for Reaper in this case? If it's the same interface as for MIR - did you select different channels for both applications?
Florian
Yes, I only use the Hammerfall driver. Reaper uses only 2 output channels of the Hammerfall ASIO driver (ADAT 1+2) and 6 input channels. MIR uses 2 different output channels of the Hammerfall ASIO driver (SPDIF 1+2) which are then loop-backed through the Hammerfall HDSP mixer to 2 of the Reaper input channels.
@am_wagner2000_25428 said:
Yes, I only use the Hammerfall driver. Reaper uses only 2 output channels of the Hammerfall ASIO driver (ADAT 1+2) and 6 input channels. MIR uses 2 different output channels of the Hammerfall ASIO driver (SPDIF 1+2) which are then loop-backed through the Hammerfall HDSP mixer to 2 of the Reaper input channels.
Thanks you for these details!
I'll set up a similar setup and try to figure out what's going on (please don't expect any results before beginning of next week).
Florian
Oh, things are getting weirder. I swear I have not changed ANYTHING in my setup, but now MIR crashes everytime I load it, during "Loading Default Project". I tried to install the latest version (which is newer than the first MIR version which I was loading), and now I even cannot start MIR because I am using 16 bit color depth - WHICH HAS ALWAYS WORKED WITH THE OLD MIR VERSION!!! But I ***HAVE*** to use 16 bit color depth because otherwise I will not see the GUI of any of my Waves plug-ins, which, for some reason, do not show up in a 32 bit color depth environment (some problem with the matrox driver or Windows 7 or whatever).
So I installed the old MIR version and it has the same error as described before, although it has always worked in the past (apart from the "crash upon first start" problem).
This is really annoying if you have only small time windows to work on your music.
@am_wagner2000_25428 said:
now MIR crashes everytime I load it, during "Loading Default Project".
This might be caused by an inappropriate audio driver setting. The crash was fixed with the latest build, but you can also "repair" older versions by removing "C:\ProgramData\VSL\Vienna MIR.ini". Then MIR should ask you for the desired audio driver and its settings before the next start.
Hmm, you're the first reporting this.
We had very bad crashes with MIR using 16 bit color depth (MIR dying without any hint), that's why this message was added and MIR does not start at all. I think we can fix this crash pretty soon, if not I'll exchange the message to a simple warning, that allows you to run MIR with 16 bit color depth even if it might crash on many machines.
Sorry for the inconvenience caused, I hope we have everything up and running soon.
Florian
I did some more testing with color depths and the old MIR version - and the problem for all the crashes was the 16 bit color depth. With 32 bit color depth, MIR starts and runs fine, no problems.
And for some reason which I do not know (maybe some automatic Windows 7 update procedure in the background in the meantime), Waves plug-ins now show their GUI with 32 bit color depth also, which they never did before. So I will stay at 32 bit color depth now.
Thanks for your support.
