[SOLVED] MIR reverb kicking in late on audio mixdown in Cubase

[DeepakAnanth]

Hi Everyone,

 

This is my first post on the VSL forums - it's really a great and active community and Dietz and Paul are very helpful in general! So looking forward to hearing back and hopefully resolving my issue. 😇

On to the issue I'm facing. Prior to that, let me explain the use case (my set-up is below my signature):

1. Running a simple set of MIDI tracks in Cubase 8.5 Pro that are patched to VE Pro where I've uploaded VI Pro channels for string section and brass section (essentially 9 tracks in all - 5 for strings and 4 for brass).

2. The tracks all have a MIR Pro instance with a venue (in my case Gateshead The Sage Hall One) set up inline.

3. While playing the arrangement back in Cubase, everything works just fine - the sections sound nice and lush like they're supposed to.

The issue: When I run an audio mixdown inside Cubase, the tracks are completely dry for the first few seconds, and then the MIR reverb kicks in.

Request anyone's inputs on how I can resolve this or if I'm missing some basic setting? Thanks in advance!

 

Regards,

Deepak

 VE Pro 5, MIR Pro and a bunch of VSL instruments

Cubase 8.5 Pro

OS X 10.10.5 - Yosemite

Custom Build (64GB RAM, 6-core @3.3GHz)

[Dietz]

Welcome Deepak,

thanks for the friendly words - highly appreciated! :-)

Sorry to hear that you're facing issues. Just to make sure that I understand your setup correctly:

1. You're using VE Pro in server mode with the "built-in" MIR Pro version (which means: the "red" plug-in, not the gey-ish VST/AU-version)?

2. When you write "audio mixdown" you mean an off-line file export, or an actual re-recording to another track within Cubase? If the former is true - do you export in real-time or really "off-line" (which means "faster than real-time" in most cases)?

In addition, please tell us the latency and buffer settings of all involved components (ASIO system, VE Pro buffers, MIR Pro's additional latency settings).

... I hope that we will be able to solve the issue swiftly.

Kind regards,

[DeepakAnanth]

Hi Dietz,

 

As usual, so quick to respond!! Reassures one in investing in VSL products! :-) Let me try and answer your questions to the best of my ability. :-)

 

1. Yes, I am using 2 VE Pro instances, both in Server Mode. I have 2 instances set up at this point. One with strings and the other with brass. The MIR Pro instance is hosted within VE Pro, not Cubase, so I guess the answer your question is yes, it's the built-in version. To clarify further, I'm not using MIR Pro as an insert FX or FX track in Cubase anywhere - it's all within VE Pro.

2. Cubase's Audio Mixdown is an offline (faster than realtime) function that allows you to export one or more tracks (or the output from any of your busses) to a file on disk. I've tried exporting to both MP3 and WAV, but am seeing the issue on both types of tracks, so it's doesn't seem to be an issue with my mixdown settings. Note that I don't have this issue when I use some other reverb plug-in inside Cubase.

ASIO System - (using my Steinberg UR22)

• Input Latency: 9.771 ms
• Output Latency: 10.500 ms
• ASIO-Guard Latency: 96.000 ms
• HW Sample Rate: 48kHz
• Buffer Size: 384 Samples.

VE Pro - Latency: 256

 

Let me know if you need any other information?

 

Regards,

Deepak

VE Pro 5, MIR Pro and a bunch of VSL instruments

Cubase 8.5 Pro

OS X 10.10.5 - Yosemite

Custom Build (64GB RAM, 6-core @3.3GHz)

[Dietz]

Does it help when you switch off ASIO Guard?

[DeepakAnanth]

Oh, I didn't realize that ASIO Guard could have been causing the issue! Thanks, Dietz! It's all working fine now.

 

Out of curiosity though, why would ASIO Guard cause this to happen?

 

Regards,

Deepak

VE Pro 5, MIR Pro and a bunch of VSL instruments

Cubase 8.5 Pro

OS X 10.10.5 - Yosemite

Custom Build (64GB RAM, 6-core @3.3GHz)

[Dietz]

ASIO Guard is "secretly" raising the latency for all channels that are not in input monitoring mode (... at least this is how I understand it). This outsmarts VE Pro, in a way. - Given the fact that you have set it to 96.000 samples while you're running the audio system at 48 kHz, I assume that it took exactly 2 seconds for MIR Pro to kick in. :-)

AFAIK, Cubase's Preferences allow for creating exception rules for certain plug-ins (VE Pro, in that case), so you don't have to switch it off in general.

Kind regards,

[DeepakAnanth]

Yes, exactly 2 seconds for MIR Pro to kick in. I should have figured that earlier! Doh! 😳

 

And thanks for reminding me that I could have turned off ASIO Guard at a per plug-in level! Had completely forgotten about that! This issue is now resolved! 😎

 

Thanks, Dietz! You rock! :-)

[Dietz]

You're welcome!