I find that a lot of Logic users do not use the MIDi filter to filter out unwanted cc events, like aftertouch. If you  go to Project Settings > MIDI > Input Filter you can do so. I believe that is perhaps why I do not have these issues with the Multiport layer.

You're welcome. Until DP8 with proper latency compensation for AU instruments is released it's now at least possible to get an accurate reading of the latency for manual compensation. Note that the actual latency is displayed there, not just a reflection of the latency buffers setting.

It's just a readout of the latency that is reported by the plugin to the host, which takes all latency inducing factors into account.

I was unable to get this version to work with PT 10.1.1. The moment a session with VEPro got recalled and VEPRO started loading its samples PT crashed. I tried it over and over again always the same. I reverted back to version 10068 and all is well again. Can anyone using the same configuration confirm this?

Cheers, Bob.

"OSX: Fixed Audio Input plug-in synchronization issues in Logic"

Is it possible that this bug caused EXS instruments sent to MIR to A: play (live from MIDI controller) when the transport in Logic is not running, and B: NOT allow live play (or recording) when Logic's transport IS running? That caused many difficult sessions of fruitless trouble-shooting. 

Do confirm if possible. 

Make sure you have properly setup I/O Utility plugins on both the Logic tracks with a Server Interface plugin and tracks with an Audio/Event Input plugin, or that sort of behavior may indeed occur.

Hi Karel,

You said also in a previous message if you use IAC you cannot bounce ofline and something about samples ( I have lost the email) can you explain a little bit more ?

You also said to use a VE server with multiple VE in Logic, I tought it was not possible with MIR PRO

Thanks in advance

Best

Cyril

P.S. We have seen various messages about VI 2.2, it looks FABULOUS, any idea when you will release it ?

IAC is an asynchronous protocol, while offline bouncing is synchronous by definition, so that will give unexpected results. Also due to the asynchronous nature of IAC the events do not arrive at the exact times they were delivered to Logic. When sending MIDI normally to the VE Pro Server, bouncing will be reliable and the events will be at the exact times they were delivered to Logic.

You can use as many VE Pro 5 (with MIR Pro) instances as you like. It's just somewhat less comfortable to work, not having all your MIR instrument icons on a single venue.

@Karel said:

Hi Karel

Thanks for your answer, I will try it next week when I return !

Is not that going to put much more stress to the computer ? say I have one VE for the string, one for the winds, one for the brass, one for the percussion and one for the rest (VSL kbd, EXS, K4, Omnisphere...)

There will be 5 x 8 audio channels (7.1) going back to Logic 

Is that going to solve the "one processor used" problem in Logic ?

Comming back to IAC with MIR :

It is not a big problem not being able to use offline bouncing, just takes a little bit more time

Why do you have to return the sound back to Logic ? why cant VE send directly the sound to the outs ?

Sorry but I do not understand why you have to return the sound back to Logic, when the sound is comming back from the venue it is THE END of the process !

Why not adding a bounce in the VE pro server !! that should not be a big job and will solve the problems with Logic and will put less stress on it as it will not have to deal with the 8 audio channels (in 7.1) comming back from VE

Thank again for the great thing VSL devellopers are doing, you are one of the rare company that solves the problems quickly and listen to his users

Best

Cyril

You did not answer about VI 2.2 ???? as I undertand it is going to bring a lot of fresh air to our configuration [H]

There will be a bit more stress with multiple instances, but if you don't use the Audio/Event Input plugins in Logic, it will indeed avoid the Live mode implications.

Note that the audio sent over network is compressed, meaning amongst other things that when there is no signal it will also not transfer data. So the number of channels with an actual signal is what really matters the most.

With the sound returning back to Logic, VE Pro basically operates as a regular plugin, keeping everything contained in a single project. Also outputting audio from the VE Pro Server is not technically viable because it is slaved to the clock of the master host.

I'm not actively involved in the development of VI 2, so I can't really comment on that unfortunately.

"Make sure you have properly setup I/O Utility plugins on both the Logic tracks with a Server Interface plugin and tracks with an Audio/Event Input plugin, or that sort of behavior may indeed occur."

You have my strongest assurance that I had the correct settings. I went through the "Select Output 1-2 in the bypassed I/O Plug-In" learning curve several weeks ago, and I tried every conceivable combination of settings before that (and aftwarwards, when the bug persisted). I'd still lose or gain playback indiscriminately. 

After I downloaded 5.0.10309 last night, the bug simply vanished, and that with the very same Logic file, without changing a single I/O or Audio Input setting. 

Thank You Thank You Thank You Thank You Thank You Thank You

You fixed the problem that has been nagging me. I don't know what item fixed it in the change log, but now all tempo Sync instruments work properly.

Some NI libraries like West Africa, would not play properly, now they do.

The Arps in FM8 now work, and all the tempo sync instruments now all seem to work .

Thank You

Glad to hear that it works well for you.