MIR Crashing

[Jerry Gerber]

Dear musicians,

I downloaded the latest version of Mir Pro running under standalone VE Pro 6, latest version on a dedicated machine running VSL instruments.  Everything is installed correctly but I am getting crashes, it's happening, I think, only when I am adjusting the stereo width of an instrument's spatial characteristics, but I can do that many times before the crash occurs.  About every 10 minutes. 

Windows 7, sp 1, Intel i7, 24GB ram, 3 SSD drives.

I have a file with 48 tracks, Mir on every instrument in effects rack, stereo to stereo, inline. No MIR on busses.

I've got threads set at 6, but it crashes at both 6 and 2.  Audio Buffer 512, MIR latency 0. Also tried changing MIR latency to 1024, as manual suggests, no-go.

I've been running VE Pro 4 and now 6 and it never crashes until now as I demo MIR.

If anyone has a clue about how to stop this crashing, I am all ears and much appreciative that someone can instruct me.

Jerry

[Dietz]

Hi Jerry,

sorry to hear about your problems. I use a very similar system for all my MIR-related development work and can assure you that this behaviour is not the expected one. :-)

Please get in contact with support@vsl.co.at . VSL support staff will talk you through the trouble-shooting process. Please supply as many additional technical details as possible (audio system and drivers, posssibly interfering applications like virus scanners, firewalls etc. ...).

Kind regards,

[Jerry Gerber]

@Dietz said:

Hi Jerry,

sorry to hear about your problems. I use a very similar system for all my MIR-related development work and can assure you that this behaviour is not the expected one. 😊

Please get in contact with support@vsl.co.at . VSL support staff will talk you through the trouble-shooting process. Please supply as many additional technical details as possible (audio system and drivers, posssibly interfering applications like virus scanners, firewalls etc. ...).

Kind regards,

Hello Dietz,

I did contact support last night via email.  I've narrowed the problem down to the crashing only occuring when I move the instrument-reverb-width slider in MIR back and forth after having done so with several instruments.  I am not sure what my firewall settings should be, I am not running VE Pro 6 in network mode, I have it networked to my DAW via ethernet (MIDI over LAN).   I do have Microsoft security essentials (anti-virus) running but it's never caused a problem in 5 years before installing MIR.

My audio system is RME 9652, all audio is being sent via ADAT to my mixing board, latest RME driver, latest graphic driver also.   There are no other applications on this machine that I run other than VE Pro, VI Pro and, now, MIR.

Thanks!

Jerry

[Dietz]

Do you see a message that either VE Pro or MIR Pro have written a crash dump? This would be very helpful to get, too.

[Jerry Gerber]

@Dietz said:

Do you see a message that either VE Pro or MIR Pro have written a crash dump? This would be very helpful to get, too.

Yes, I checked Windows dump files and sent 2 .dmp files to VSL support.  I also checked the reliability history and the event viewer and found this:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Application Error" />
  <EventID Qualifiers="0">1000</EventID>
  <Level>2</Level>
  <Task>100</Task>
  <Keywords>0x80000000000000</Keywords>
  <TimeCreated SystemTime="2017-01-21T23:14:43.000000000Z" />
  <EventRecordID>70444</EventRecordID>
  <Channel>Application</Channel>
  <Computer>VSL</Computer>
  <Security />
  </System>
- <EventData>
  <Data>Vienna Ensemble Pro.exe</Data>
  <Data>6.0.0.15567</Data>
  <Data>58452ceb</Data>
  <Data>ntdll.dll</Data>
  <Data>6.1.7601.17725</Data>
  <Data>4ec4aa8e</Data>
  <Data>c0000005</Data>
  <Data>0000000000053560</Data>
  <Data>7d8</Data>
  <Data>01d2743945206cd7</Data>
  <Data>C:\Program Files\Vienna Ensemble Pro\Vienna Ensemble Pro.exe</Data>
  <Data>C:\Windows\SYSTEM32\ntdll.dll</Data>
  <Data>6399eca9-e02f-11e6-b6aa-485b39021c9b</Data>
  </EventData>
  </Event>

Finally, I don't know if this has anything to do with it, but when I replaced the 3 hard drives with SSD last month, I also turned off prefetch and superfetch in Windows as suggested by some as they are unnecessary with SSDs.  That probably doesn't' have anythign to do with it though...

Thanks,

Jerry

[Jerry Gerber]

Never mind, I figured out how to update the license...

[Dietz]

Hi Jerry,

I seem to remember that this thread was about (possibly) MIR-related crashes, originally. Does your latest message mean that this issue has been solved?

Kind regards,

[Jerry Gerber]

@Dietz said:

Hi Jerry,

I seem to remember that this thread was about (possibly) MIR-related crashes, originally. Does your latest message mean that this issue has been solved?

Kind regards,

No, the crashes are continuing.  What I resolved was how to extend the demo license, which I figured out.  What is still happening is that after 3 or 4 times of moving the instrument width slider in MIR, VE Pro crashes.  I've been troubleshooting most of the morning, have tried reinstalling MIR (havent' reinstalled the room pack yet) and experimenting with threads, but none of these efforts stopped the crash.  I've sent support several VSL dump files, so hopefully someone can identify the problem and the remedy.  I am awaiting a reply.

Thanks, Jerry

[Paul]

Hello Jerry, 

Quick update: Seems like our developers found the bug, it will be fixed in the next update. My colleague Marnix will send you a beta version to verify. 

Best, 
Paul

[Jerry Gerber]

@Paul said:

Hello Jerry, 

Quick update: Seems like our developers found the bug, it will be fixed in the next update. My colleague Marnix will send you a beta version to verify. 

Best, 
Paul

Wow, that was quick!  You guys are great.   Since I am new to MIR and it's been around for some time, I wonder why nobody else discovered it.

Might you know when I can expect the beta version?

Best,

Jerry

[marnix]

Hi Jerry,

I have just sent you a link to the latest VE Pro 6 beta version - please let us know wether this resolved the problem!

Best, Marnix