I've been very happy with MIR Pro on other audio sources. It takes some fiddling (like most things) but the results are excellent.

**Leigh

The MIR plugin works great. But I have some issues with the VEP 6 Audio Input Plugin -> VEP MIR.
Latency compensation does not work and I get a lot of clicking (it's even worse with the mixdown).

Tried all different variations of buffer-sizes and settings. Nothing helped.
For now I am using VEP MIR with VSL Instruments and MIR Pro Plugin with recorded audio.
Works fine and to get Dry/Wet seperatly I have a second plugin in the Fx-send bus (+ setting Dry-Wet ratio in MIR to 0% and 100%).

@bbelius said:

The MIR plugin works great. But I have some issues with the VEP 6 Audio Input Plugin -> VEP MIR.Latency compensation does not work and I get a lot of clicking (it's even worse with the mixdown). Tried all different variations of buffer-sizes and settings. Nothing helped..

Have you tried to switch off "ASIO Guard" in Cubase's Preferences? 

I run into the same problem at low latencies and/or as soon as I use more than four or five instances.

"Audio Input" into VE Pro has always been some kind of experimental feature. Most DAWs are not ready to send audio to an external application from anything else than their actual outputs; abusing a plug-in like VE Pro's "Audio Input" for this task comes for a price ... please keep in mind that VE Pro has been primarily invented to act as a MIDI host that reacts to incoming MIDI data, not audio.

Kind regards,

My ASIO latancy is set to 2048 (the highest value my interface can handle). I used 4-5 instances of the plugin.

Maybe if we could return the the processed audio-signal from VE back to the plugins output, it would solve this issue?

No, this would actually make the issue worse. If this would have been easier, VSL's software engineers would have opted for this straight-forward situation from the very beginning ...

PS: This is the reason why the - actually stripped-down - plug-in version of MIR Pro has been invented at all. In this case, the hosting DAW is still processing the audio like with any other plug-in; it's "just" the GUI that runs in an independent process. No CPU-timing-critical stuff to compute here.

Ah! Ok, this explains a lot. Thank you for these information.

Dietz, one more question about MIR: does MIR add propagation delay (de: Laufzeitverzögerung) to the instruments / sound?
If yes, is there a switch to turn it on/off?

Good question! :-)

Back then, we were very proud to offer perfect alignment between Main Mic and the direct signal from virtual spot mic (i.e. MIR's "dry" signal component). As a matter of fact, we carefully cut any remnant of the recorded direct signal from all IRs and replace it in real-time with the readily positioned dry signal, to avoid any hint of phasing and/or timing issues. So there's nothing you could compensate. :-)

That said, I know very well that sometimes the delay between spot mic and main mic adds to the sense of perceived depth and enveloping. You can achieve this (in VE Pro only!) by splitting the wet from the dry MIR signal and adding some milliseconds of delay to the former.

HTH,

Yet another PS:

You might have seen the "Delay" parameter in MIR Pro's Output Format editor (which controls the Ambisonic decoder and contains the output matrix). Here you can add delay to individual virtual microphone capsules, but of course this will affect _all_ decoded signals then, so that's not what you were asking for.

... the main idea of this feature was to fine-tune the delay of microphones routed to surround channels.

Kind regards,

Sounds interesting. I will experiment with some added delay.

Big thank you, Dietz!

You're welcome! :-)

@Dietz said:

• Typical playing techniques and ways of sound production

Yes, but only in form of a weighted average, not dynamically.

Crazy, thanks :)