Vienna Symphonic Library Forum
Forum Statistics

195,311 users have contributed to 42,976 threads and 258,204 posts.

In the past 24 hours, we have 1 new thread(s), 10 new post(s) and 66 new user(s).

  • MIR Pro – more than 16 positions in AU plug-in (Logic, Digital Performer)

    last edited
    last edited
    Hello, I didn't buy the MIR Pro yet, but I would like to. But I'm not sure, how to load more than 16 instruments with different positions, from the VE Pro 5 as Audio Unit plug-in (from Logic or Digital Performer). I read this thread about more than 16 channels in the AU plug-ins. I solved this problem the same way – use more VE Pro instances. But I'm not sure, how will this work with the MIR Pro? How can I send MIDI data to all 32 or 50 channels of Herb's Teldex Presets from AU host, please? Thanks, Martin

  • 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.


  • Great! Will the 2nd option work with Login only? Or will this work with any AU hosts (for example Digital Performer too), please?

  • Only Logic, since it uses the Logic environment.


  • I see. I will wait, thanks! Martin

  • One more question about this: How it will work with CPU cores? One Channel strip is computed on separately core in the Logic. So if I will úsek only one VE5 instance, Logic will compute all instruments on one core only? If I will use outputs from MIR and VE back to Logic, and make effect processors in the Logic, than the Logic will compute these effects on different cores. But whole VE (and all instruments) will compute on one core only, right? Or do you have some solution fór this? Is it possible to use more CPU cores this way? Thanks a lot! I'm very hungry to MIR - more and more. :-)

  • 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.


  • Thank you very much!

    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. :-)


  • You are right. It just works, and it's quite intuitive.
    Great work, thanks!
    Martin

  • Hello Martin,
    Can you indicate little bit, how it will work? I have very big problems with synchronization, if I'm using 32 MIDI channels, VEPro Event Input and I/O plug-in. It just doesn't work in sync, now.
    And can you tell the release date, please?
    Best, Martin

  • Thi is it! Thanks!
    Martin