Problem signature:

  Problem Event Name: APPCRASH

  Application Name: Vienna MIR.exe

  Application Version: 1.0.0.1563

  Application Timestamp: 4aa043da

  Fault Module Name: ntdll.dll

  Fault Module Version: 6.0.6001.18000

  Fault Module Timestamp: 4791adec

  Exception Code: c00000fd

  Exception Offset: 0000000000047b9a

  OS Version: 6.0.6001.2.1.0.256.1

  Locale ID: 1031

  Additional Information 1: 46f9

  Additional Information 2: fa562687f56efb52c2ecdc0594571eaa

  Additional Information 3: 7b4c

  Additional Information 4: 30e2ee0f2efb3537dbbbfb3387f8191d

Read our privacy statement:

  http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409

hm are you still there ? 

i never was able to use mir, couse it allways crashes. is there any solution 

macpro 2.226 nehalem 16 vcores 12 gb ram .

i realy like to try this...

is there a way maybe to get week more to try it out ? couse today its the last day... maybe thats the problem

Did you say you're on a Mac Pro?  As far as i know MIR isnt available for Macs. Windows only. Even if you're running a windows system on a mac, i still dont think it's workable.

I could be wrong.. im a mac user, so dont have the chance to know the first thing about MIR, but just wanted to point that out.

-michael

yes i am running vista 64 on this macpro.

vsl ensemble 64 is running there too without much problems

yes i am running vista 64 on this macpro.

[/quote] 

This should be ok.

What buffer size did you select in the driver dialog of your audio interface? MIR supports only powers of two (28,256, 512...), any other buffer size should cause a warning (we had crashes with older versions there).

Do you see an ASIO driver for your mbox 2 in the audio settings dialog of Vienna Ensemble?

What happens exactly, when you start the engine - do you see a blue status bar at the bottom (indicating the progress of impulse response preprocessing) or does it crash right after you press the button?

Oh, and did you already try Asio4All?

This might help to figure out if there's just a problem with your rig kontrol or a general issue with MIR on your machine.

I hope we can figure out what's wrong here, Florian

i dont see the asio driver for my mbox 2 :/ 

can we talk german please ? :)

i see the blue status bar when i start the engine, but this just works if i have no instrument inserted...  when i load some instruments, then it will crash  when i start the engine.. or if i have the engine allready loaded and tryin to load some thing inside it will crash too... 

whats asio 4 all ? 

do you think it could be a rig controll problem ? 

can i get some more days on mir ? couse this is the last 30 minutes i can use it... :/ and it doesnt work. 

is there a telephone number where i can reach you ? 

i also tried every buffer size

question: if you don't see the ASIO drivers, how can you change buffer size then?

more questions: how do you feed MIDI, i.e. is there a sequencer installed on the machine?

if yes, please double check you don't have any MIDI or audio loops configured.

please make sure the mbox is NOT set as default audio device in windows (control panel, audio settings) - the mbox drivers are not multi-client, so any other application configured for the mbox will prevent MIR from accessing them.

driver & firmware version? vista SP1?

christian

i just can see the guitar rig kontrol in asio... and there i can change the buffer size inside MIR.

asio doesnt recognize the mbox2...  on this computer is no sequenzer installed. we use a motu micro lite midi interface @ this machine. on the sequenzer machine there is a logic 8 with a digi 003 wich sends the midi data to the motu midi interface.

the default audio device is the built in realtek from apple.

using windows vista 64 sp1 

driver and firmware from wich hardware ? 

well, from your posts above i've been reading your audio device (on the mac pro) is the mbox2 and google returns a lot of results with asio problems on vista, so i asked for firmware and driver version ....

guitar rig is a software, right? so which ASIO (from which sound device) do you see in rig kontrol?

christian

rig kontrol is an audio interface :)   mbox 2 is not pluged into the pc becouse asio did not recognize it. 

by the way i tried asio 4 all and used the realteak (built in sound card) its still the same problem.

i only see the rig kontrol device and asio4all in asio.

some posts ago someone told me i should try asio 4 all and tried it with it and the internal sound interface. 

but its the same result

ok.. i will reinstall vista 64 on the macpro... lets see what happens

i only see the rig kontrol device and asio4all in asio.

[/quote] 

And when you try to use asio4all MIR still crashes? Asio4all worked fine on several PCs for me...

Right now we try to allow MIR to load the mbox driver as well, I'll get back to you as soon as there's a new MIR build available.

I guess you already noticed, you got a new trial license for another 30 days.

Florian 

yes  i just noticed :) best support i ever had in my life !

ja the problem is still there when i use the asio4all and the internal sound card. 

ok, i installed vista 64, again... and it worked like a dream :)  

using asio4all and the internal realtek sound card, and midi over lan.  loaded 30 instruments and let them play unisono at 256 buffersize.

first time i can work without crashing vsl or sequenzer...

thank you so much for your help and your time spending. 

ok i understand :)

every other configuration, like with vienna ensemble even over lan does not work like expected... too many crashes... but i think its coused by the seqeuenzer... wich will disconnect after crash... and i need to reload everything ...  and this tooks time... :) 

ok, i installed vista 64, again... and it worked like a dream :)  

using asio4all and the internal realtek sound card, and midi over lan.  

[/quote] 

Hi Ralf, you're welcome!  : )

Just to be sure - does MIR run with your rig kontrol as well, or does it only work with asio4all?

I hope both drivers are fine now...

Cheers, Florian

i just bought the full version today :)

monday ill get back to the studio then i will tell you if it will run with the guitar rig audio interface