Oh, and I forgot to ask: What are the latency settings you're using for your audio hardware and for MIR Pro (... it's in the Preferences)?

Hi Dupuy,

for testing purposes, please try the following steps:

- Set the latency of your audio system, to 512 or 1024 samples.

- Set the sampling frequency to 44.1 kHz.

- Create a new Reaper project.

- Create a single audio track and connect it withe the master output.

- Instantiate MIR Pro as insert effect.

- Open MIR Pro's Preferences, set its latency to 1024 samples (... while you're at it, you might also activate "Dynamic Processing", but that's only relevant for bigger projects, not for our testing scenario). Close the Pref's window.

- Add something like a test-tone generator plug-in before MIR Pro. Pink Noise is a good testing source, but any continuous signal will do.

- Now, while the signal is processed by MIR Pro, move the Icon on the Venue's stage and try to provoke the error you were describing.

... if everything's fine up to now, add more instances and see what happens. Assuming that you're working in Stereo on a recent machine you should be able to have 150 or more instances playing easily.

A final thought: You didn't tell us about your graphics card yet. A problem in this context could explain the issues when changing MIR's GUI items.

Thank you.. I am ready to do these tests but something is not very fair for me... For about 10 years, all my projects are in 48 kHz... Is it very important to switch to 44,1 ?

48 kHz is fine, of course. I just wanted to make sure that we can rule out issues that might related to higher sampling rates (which I haven't tested with Reaper yet).

I set the parameters as you mentionned... But I have a problem to do the test.

I describe it :

- I create only one track in Reaper

- I insert the wave generator form "waves" (Emo generator) which provides sinus, white or pink noise

- I insert one instance of Mir pro 24 in the track

- I start the generator ... That's ok of course but...

- at each time i put my mouse on the GUI of Mir to move or modify the  source parameters,  the generator stops... It restarts when i click on the Reaper GUI... I have not this problem with others plug-ins (for example, with Vienna suite, that I own too) . With all others I may modify parameters on the plug-in GUI without any consequences on the Reaper's workflow..

Graphic card : NVDIA Geforce GTX 1050 Ti

I can't say anything about the graphics card as I'm no hardware guru. :-) Just make sure that it's drivers are up-to-date; maybe Google knows something about its Ins and Outs.

If you were in Cubase or Nuendo I would also ask if you have activated the host's Preference for releasing the ASIO-driver once the application is in the background. Is there anything like that in Reaper?

I've also heard from people who were throttling their system by using certain graphics routines on the CPU rather than the graphics card, but again: I'm no hardware guru.

... other than that I can just repeat that I'm able to use MIR Pro in Reaper without any problems here. :-/

You are not a guru but you are not very far  to become it ! I put your recommandations on Reaper settings and it works fine now ! I hope there is definitve ... I thank you very much !  I'll come back if another trouble decides to bother me !

So it was indeed the Preference for releasing the drivers in the background? Yay! :-)

Enjoy MIR Pro now. 

Best,