1. You can use the Event Input plugin to get more than 16 channels into one AU plugin.
2. The next release of VEPro (in a few days) contains a workaround for multiple midi ports for one AU plugin in Logic.
183,532 users have contributed to 42,306 threads and 255,097 posts.
In the past 24 hours, we have 6 new thread(s), 13 new post(s) and 51 new user(s).
1. Logic will compute any mixing derived from this instance on one core.
2. Processing of the instruments (and MIR) is multithreaded by VEPro itself.
3. Effect processing in Logic, which derives from a single channel (or its auxes), will occur on one core. It is a major downside of Logic, it's multithreading implementation is not the best.
4. The VEPro processing, including instruments and MIR, is likely to be the heaviest workload. Mixing after this, should be handled fine by a single core.
But. I'm not sure, I can undestand this well.
So if I will use Logic as MIDI sequencer only (no audio, no internal AU instruments, no internal FX), and send all MIDI data to the VEPro, Logic will compute just this. So it shouldn't be so many information, and it should be OK for 1 core. So Logic will display, it work just one core, right? But VEPro will compute all virtual instruments by multithreaded itslef, so the VEPro will use other cores. Although Logic will display it work just 1 core, the computer will use more (maybye all) cores, thanks to the VEPro, right?
So I don't have to be afraid, I'm using just one core, if I have 8 cores, and I don't have to be afraid, my CPU will be slow. Logic will compute just sending MIDI data to the VEPro plug-in.
I think, I have to download DEMO version of MIR Pro, and try it with Logic myself. :-)