So we will loose you as potential customer, sorry to say so. :-/
The MIR.E(ngine) will rely on a completely proprietary format (allthough we will of course include the option to _import_ third party IRs). The reason for this is system-immanent: The MIR.E will have to "know" the input signals to work properly regarding directivity, while the IRs themselves will have a set of very demanding requirements to be fulfilled.
I don't want to spoil too much info about an unfinished product, but don't consider the MIR just another "reverb". Actually, it will be a complete mixing-frontend for our products. The integration will be _much_ closer than in an ordinary "sample library / reverb / mixer"-combination.
Thanks for your interest!
/Dietz - Vienna Symphonic Library
The MIR.E(ngine) will rely on a completely proprietary format (allthough we will of course include the option to _import_ third party IRs). The reason for this is system-immanent: The MIR.E will have to "know" the input signals to work properly regarding directivity, while the IRs themselves will have a set of very demanding requirements to be fulfilled.
I don't want to spoil too much info about an unfinished product, but don't consider the MIR just another "reverb". Actually, it will be a complete mixing-frontend for our products. The integration will be _much_ closer than in an ordinary "sample library / reverb / mixer"-combination.
Thanks for your interest!
/Dietz - Vienna Symphonic Library
/Dietz - Vienna Symphonic Library