194,493 users have contributed to 42,922 threads and 257,973 posts.
In the past 24 hours, we have 2 new thread(s), 8 new post(s) and 78 new user(s).
hi all,
i am slowly getting my main VSL libraries lined up.
absolutely incredible.
i'm sure this question has come up many time, but i want to be sure...
MIR Pro can be used as a typical VST Plugin Insert on ANY audio/midi/instrument channel within a DAW like Studio One Pro, yes?
With VEP 5 i could do this as well?
thanks.
Yes, MIR Pro can be used on actually any kind of audio source.
Just be aware of the fact that in theses cases MIR "knows" considerably less about the incoming signal than it does in case of Vienna Instruments: Here, detailed "Instrument Profiles" allow for deep interaction between room and instrument. They supply:
... none of these aspects are available for other audio sources, of course, but MIR offers the so-called "General Purpose Profiles" to allow for their straigh-forward integration nonetheless. Those "plain" profiles are the ones you should choose for all signals which aren't derived from Vienna Instruments, otherwise the results will be unpredictable (even quite strange, under certain circumstances. 8-) ....)
HTH,
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%).
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..Clicking.. can be CPU and/or DAW.what are yours?
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,
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.
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,
