Dietz, those eq curves are very helpful thank you!  When I load Teldex, I see another character profile show up sometimes called MIRX Teldex.  Any clue about that one?

Ultimately I can always put my own eq in front of mirpro in order to eliminate a closely mic’d proximity warmth from a sound that is meant to be further back. I just wanted to have a clear idea what MIR Pro is doing to the dry signal based on distance. Looks like in a generic way the distance character profile would also provide a bit of a one size fits all low shelf to imply some distance that way. I will play with that.

By the way I wasn’t meaning to infer anything “bad” about calling the dry signal the "close mic". Just seeking absolute clarity about what is in that signal; and for the moment trying to be absolutely literal about what a close mic would have in the signal vs what MIR Pro potentially has in the dry signal.

So it’s a close mic signal after a mix engineer has potentially tweaked the sound in certain ways. Maybe a good way to think about it is: it’s a close mic after an engineer has panned it, eq’d it for character, adjusted the level and eq to mimic distance and air absorption (but not removing proximity effect unless distance character profile is used but still that is not variable based on icon position), and accounting for either the mic being attached to the players nose or being attached to the floor. That’s a mouthful though I get it.

Regarding proximity effect that may be baked into samples, that will always depend a lot on the samples being used. Many sample libraries have been close mic’d and are very present front and center. When they are lathered with reverb they will sound wrong. Our brain is hearing both proximity and reverb and it doesn’t compute. So that’s why there can often be a need to low shelf the low end in addition to hi end.  But it will always depend on the source samples being used, how they were produced to begin with...the mics, distances and processing on those source samples are all part of the close mic signal chain.

I don’t hear a lot of proximity warmth when I test out MIR Pro with various vsl instruments, which is probably a good thing most of the time. If vsl shelved out the proximity from the close mic samples to begin with then it’s a non issue when using them in MIR Pro unless you specifically wanted to hear the proximity. Other libraries, however might need more shelving and I am wondering about whether low shelf would need to be adjustable to account for the desired depth of the instrument, or distance from the main mic. Verta calls it z-plane.  It would have been cool if the icon on the soundstage effected this aspect of distance also in the dry signal. 

Perhaps if VSL had provided two parallel sets of IR's, one for the dry signal and one for the wet signal (rather then just removing the Dry from the IR's), then the IR's themselves I guess might have captured that.  But since dry has been removed from the wet IR's...then we have to mix certain assumptions about distance back in using conventional mixing techinques such as EQ.

@Another User said:

Perhaps if VSL had provided two parallel sets of IR's, one for the dry signal and one for the wet signal (rather then just removing the Dry from the IR's) [...]

Like pointed out before: This could be done in simple stereo convolution reverbs*), but not in case of MIR, where we mix and match more than 100 individual IRs for a single stereo source. Severe phasing issues and ugly colouring would be the result.

You know the proverb: "You can't have your cake and eat it." 😉

*) ... where it still sounds bad more often than not

I'm aware of Mirx Mode, but not the character profile by that name when I'm not even using Mirx Mode.  What is that doing?

I was not meaning to infer that we should bypass MirPro and do things the manual way, there is no point in purchasing MirPro if that is case obviously...Still trying to get confirmation that I understand what MirPro is doing to the dry signal?  It does sound like, however, I will probably want to think about using EQ and other plugins pre and post MIRPRo in order ot handle z-plane oriented spatiality which MIR Pro is currently NOT handling on the dry signal, mainly proximity effect.

My hypothetical point about parallel IR's, is not what you were understanding from my words I don't think, but we don't need to cover that I was just fantacizing out loud and it has distracted you from my core questions.  

@Another User said:

It does sound like, however, I will probably want to think about using EQ and other plugins pre and post MIRPRo in order ot handle z-plane oriented spatiality which MIR Pro is currently NOT handling on the dry signal, mainly proximity effect.

If it sounds right for you, then there's nothing wrong about that! 😊 I use track- and bus-based processing in MIR centered mixes as much as I do in "conventional" ones.

@Another User said:

Still trying to get confirmation that I understand what MirPro is doing to the dry signal? 

Let me try to summarize and if you can just confirm accuracy mainly regarding the dry signal...

1. The original dry signal that came into MIR is never passed through in any fashion.  MIR blocks it and replaces it with the "MIR-positioned dry" signal.
2. The wet signal has had the direct instrument sound to the main mics specfically cut out.  But otherwise it has all reflections happening in the room, early and late..as encoded in the IR's, but with the direct sound from the instruments missing.
3. MIRPro modifies the incoming signal, which is assumed to be a center panned signal; and effects the signal to provide spatial information, the result is the MIR-positioned dry signal
4. The wet/dry slider can be used to adjust the balance between the MIR-positioned dry signal and the wet signal, described above.
5. The MIR-positioned dry signal has been time aligned with the wet signal to avoid any phasing problems that are typical in real world recording situations.
6. The dry signal is regarded like a close spot mike, but after a mixing engineer has applied a few more typical adjustments to that close mic dry signal, resulting in a stereo MIR-positioned dry signal.  The following options are available for the dry signal:
7. The directivity filter option will determine whether the direction of the player icon will have any bearing on the dry sound.  If checked, then it will be considered like the mic is planted to the floor, and directivity profile will be used to effect various aspects of the sound such as level, EQ, etc..based on directivity profile.  If unchecked, then the direction the player is facing has no bearing on the dry sound, only to the wet sound.
8. Distance depedent scaling, if checked, will take into consideration the distance from the player to the main mic and adjust the LEVEL accordingly in the dry signal.
9. Air Absorption, if checked, will roll off HF from the dry signal, based on distance from the player to the main mic.
10. Proximity effect is not adjusted automatically by icon placement on the stage, however there is a character profile called "Distance" that can be used to specifically remove proximity warmth in order to place an instrument futher towards the back of the stage, somewhat generically, in terms of proximity warmth. 
11. LR pan of the instrument is determined by the icon location on the stage relative to the main mic.  The dry (and wet) output of MIRPro will be stereo, panned signal
12. The width of the instrument or ensemble will also be determined from the icon and will effect the dry signal in the stereo panned output in some way.
13. Instrument and character profiles provide a few typical default EQ curves (and 2100 other settings), in order to get a slightly different engineered sound out of the instrument.  The ones built for MIRx mode are of interest because they have been crafted to make VSL instruments sound great in specific VSL rooms.  These will effect both the dry and wet signals.

If that is all correct as stated, then that about covers it I think.  My overall impression is that the wet signal will generally just take care of itself, it has all the widths, sizes, distances, panning, directivity, reflections and everything else that actually happened in the room...all present in the IR's...  so the wet signal will have all that, but will sound kind of wet because the direct sound to the main mic from all the instruments has been cut out.  You can play around with different mic arrays to hear more or less of the later reflections or to change the stereo width of the wet sound.  Or adjust the dry/wet slider or reverberation time to taste.

Then we mix the above mentioned MIR-positioned dry signal in with the wet using the wet/dry slider...which has had some of the spatial information engineered back into it, such as panning and directivity, but might not be a complete picture of the actual distance to the main mic in terms of proximity EQ.  We lost that when we removed the direct signal from the main mic.  Its ok, it just means a pre or post EQ may be useful to dial that in exactly if the character profiles aren't enough of a fix.

Sorry for the slightly delayed reply, Dewdman. I'm in the midst of a quite demanding recording session ATM, which leaves little spare time for forum discussions. 

@Another User said:

If that is all correct as stated, then that about covers it I think. [...]

*two thumbs up* 😊

This whole thread was incredibly useful!  Thank you Dietz and Dewdman.

Wonderful educational Dietz!

Thank you and Dewdman for elaborating on this topic. I'm happy to get that I was (almost) understanding it correctly, but a lot more confirmation and clear-up was made.

From the first day, I loved MIR, but from the very first day I was wondering that the manual is too little and concise: a great start, but not a deep dive (e.g. how to manage different mics?, how to use the virtual mics creation editor?, how to treat external signals (e.g. other plug-ins or real audio)? etc. etc.)

Maybe I will write my "questions list" as well :) (don't worry, sooner or later, but more later than soner so you have time to recover Dietz :)

Writing a manual is always a "fight" between technical completeness and ease of comprehensibleness. Legacy Vienna MIR (MIR Pro predecessor) lent itself to the first approach, and consequently there were complaints about the complexity and technicality of the manual. I tried to stick to the second approach when compiling the manual for MIR Pro, separating parts of the engineering background to addenum texts - which of course means to omit some of the more technical aspects. 

... it's hard to do suit everybody ...

Hi Dietz,

thank you for your answers, really interesting. I have bookmarked this thread for future reference. Here is just too much useful information, to let it get lost in the mass.

Maybe you can add an additional optional chapter in teh manual for the technical stuff?
(Or even better: Please make a blog/yt-channel filled with your wisdom ; )

Big thanks and all Best, Ben

@Another User said:

... it's hard to do suit everybody ...



As usual. 😊