Hi Andi,
Thank you for looking into this issue. My guess is it's now fairly easy to track to the location where the memory exception occurs. Because the 4096 size is commonly the smallest buffer size offered by generic audio drivers, fixing it would give users a better experience and enhance the overall stability of the software.
By using the ASIO driver, I have found a acceptable work around. My configuration is running entirely on a slim 15" notebook computer so there is no option for me to put in an audio interface. My workflow does not required low latency as long as everything is synced up properly. The main concern is to keep a small memory footage and low CPU usage. In this case, a large buffer size is not a bad thing. My template has about 50 instruments with more to be added. It takes about 13.5GB and uses about 50% of the CPU which I find reasonable.
Despite the issue with MIRacle, I'm truly impressed with VE/MIR and VI. The integration is solid in working with Sibelius and also in hosting Kontak Player. I would like to congratulate the entire a team at VSL for their outstanding effort.