MIRx bug in VI Pro 5?!

[chrishawk]

Hi, MIRx seems to have dropped out on some of my instruments, although there is nothing to indicate why. I have 2x VEP instances running (Live9->VEP server->VEP), one for Strings and one for Brass. With MIRx activated, both instances and everything is synchronized, no problems. However, in my current project, some instruments (notably solo for VI, VA, VC in Strings VEP, and all Brass instruments in Brass VEP) do not get any reverb whatsoever. Everything has been fine, but suddenly these have now dropped out in the current project. Everything I can see in VI Pro indicates things are fine. MIRx activated along with Venue, Profile, Nat Volume, Pre-Eq, Synch, and Dry/Wet. If I change the dry/wet, nothing happens with the reverb. If I change the venue (which then synchronizes with all other VEP and VI instances), the reverb is still zero. If I change to Algo, then I get reverb. If I change back to MIRx, it disappears. I also tried Channel 15 (reverb on/off) without any effect. I duplicated the involuntarily dry Trumpet section, to see if a new instance would be wet, but it was not. I saved the matrix, then imported it into a new VI Pro instance. Reverb worked. Then I saved the patch, imported it into a new VI Pro instance, reverb worked not. So there is probably something in the patch that is fundamentally anti-MIRx :) Any ideas how to fix this? Is there a hidden setting somewhere that I'm missing? I've been through all the settings I can find, but I still have no clue what it is in the preset that disables the MIRx reverb. Knowing how thing go, this will probably happen again sooner or later. And I'm not too keen on setting up 10+ new instruments when the reverb starts failing. Interestingly, this probably happened all at once yesterday. One moment things were working, the next MIRx for 10+ instruments in two separate VEP channels got disabled. Regards, Chris

[Paul]

Hi Chris, 

Thanks for the report. I have contacted you via mail, and hopefully with a solution [:)]

Best, 

Paul

[chrishawk]

Thanks Paul! Will try it out, but possibly not now since I got it working, and I'm too paranoid to change anything ;) Here is what I found: During the replacing of the various instruments, one of them actually would not get MIRx reverb whatever I did. However, by chance the MIRx-specific delay compensation got changed, and suddenly things started working. Since I'm working in a near-zero delay environment, I suspected this might be the issue and it probably was. I will have to revert back to manuals or self-testing later on to see what the MIRx delay compensation actually does, but I suspect VI PRO disables MIRx reverb when system resources get low. Correct? Regards, CH

[Paul]

Hi Chris,

From the MIRx manual:

• Default MIRx Latency: 512 Samples
• As a rule of thumb: More latency means less CPU load.
• But there are two numbers to be taken into account here, namely the host buffer size (as reported by your audio system drivers) and the MIRx latency setting. The latter should either be 0 (which is usually ideal) or a number greater the host buffer size.
• MIRx latency below or equal to the host buffer size will yield sub-par results.

The question is: What are you latency settings in your soundcard, in the VE PRO Server Interface (I assume "0") and in MIRx.

Latency always only affects real-time playing.

Best,

Paul

[chrishawk]

True, and the answer is that my latency is usually 64-128 in the host, and 0 for VEP/MIRx. What I failed to see is that it seems VI PRO disables MIRx reverb when latency is too low. If that is the case (and I'm not sure it is) a warning would be nice :)

[Paul]

Hi chrishawk, 

I couldn´t reproduce muted MIRx with 0 latency on my systems, but we´ll look into it. If you want, you can send me a small exemplary Live Project with steps on how to reproduce and your settings and specs => . 

Best,

Paul