Not right now, sorry to say so. Quite possible that we will see this in a future update, though.

 Many thanks for new update..Dietz would you mind to explain how can I use for example kontakt 3 with MIR 1.1? or how to import third part vsti in MIR ? Happy new year.

Shakuman.

That's easy:

• make sure your VSTi is compatible with a 64-bit OS
• tell MIR where to look for its DLL (in the preferences)
• create a new Icon, preferably with one of the General Purpose Instrument Profiles (otherwise you will get unpredictable results soundwise)
• select the VSTi from the Source-pulldown at the bottom of the Add Instrument dialogue window.

HTH,

Kambiz,

right now I have no simple solution for your needs. I know that informing MIR about the tempo of a master session will be helpful as soon as you want to work with loop- or pattern-based sources, and I have high hopes that we will see a possibilty for this in a later version.

Right now, the safest way to route audio back to a second computer is a digital audio connection, if you ask me. Nevertheless, we work on an integrated solution for MIR Pro.

Kind regards,

@Dietz said:

That's easy:

• make sure your VSTi is compatible with a 64-bit OS
• tell MIR where to look for its DLL (in the preferences)
• create a new Icon, preferably with one of the General Purpose Instrument Profiles (otherwise you will get unpredictable results soundwise)
• select the VSTi from the Source-pulldown at the bottom of the Add Instrument dialogue window.

HTH,

Dietz (or anyone who knows),

I just downloaded the update and installed it.  I am now trying to get it to host Pianoteq.  I do not see any places in the preferences of MIR to tell it where Pianoteq is located.  There is an advanced tab with a buffer multiplier setting, and a general tab for changing the output format folder and the location of the .vmi files.  Where exactly do you go to tell MIR where Pianoteq is located?

***EDIT - Never mind, I found that you actually set it up under audio settings, not preferences.  Then add the pianoteq.dll to the VST Plug-in section.  It's loaded now and I will report back if I have any more issues.

Thanks!

Maestro2be

Please be careful - the latest Beta-build of MIR (1680) is known to show several incompatibilities with projects of earlier builds. Don't use this build for any mission-critical work, use build 1670 instead.

Kind regards,

Thanks Dietz.  I am in fact using 1670.

Last night I only had 20-30 minutes to play around with it but using Pianoteq, it was working flawlessly.  CPU was at about 20-30% while blasting through as many notes as I could play.  The latency is killing me though.  I am going to try to to lower it for solo piano recordings.  If I can't get it where I need it, I will have to end up recording it locally on my macbookpro, and then once it's done send it to the MIR machine and finish the mixing on a stage of choice.  It adds additional steps but truthfully it's not that much of an inconvenience.  Because the latency will not matter for playback and fine tuning the reverb for final output.

My RME Hammerfall DSP Multiface 2 is set at 1024 at the moment.  That was because I was working on orchestral pieces.  I could probably drop that significantly while only working on a solo piano track recording.  Also, as far as latency goes I think I am also partially to blame for this due to the diasy chain hookup I have at the moment.

1.  Digital piano midi out is going to my M-audio Axiom midi in.

2.  The M-audio Axiom is connected to my Macbookpro/Logic 9 via USB.

3,  Then Logic sends the midi information out the M-audio Axiom via it's midi out, into the Hammerfall DSP Multiface on the MIR Machine.

4.  The MIR machine then has a setting of 1024 latency on the Hammerfall DSP Multiface.

5.  Fiber optic audio cable from the Multiface to the Lavry DAC.

The system is rock solid, never hiccups, never drops notes etc.  It works perfectly for all scenerios except for performing live piano parts.  So if you see an obvious massive improvement somewhere (that is ultra low cost) please let me know.  Otherwise I am going to try to lower the soundcard to 256 or 128 and see how it does during solo piano recordings.

Thanks,

Maestro2be

Thanks for the report!

There's not much we can do about the latency, which is the concession made to the fact that there are hundreds of convolutions going on in close-to-realtime. 256 samples is most likely the lowest meaningful value, and you have to be aware that this number is actually at least doubled by MIR's buffer multiplier.

Faster CPU's and busses will ease our pain in the near future, though. ;-)