Vienna Symphonic Library Forum
Forum Statistics

180,822 users have contributed to 42,142 threads and 254,366 posts.

In the past 24 hours, we have 2 new thread(s), 4 new post(s) and 76 new user(s).

  • Obstacles with Current setup moving into Catalina

    Does anyone know, how I can solve this:

    My current set up.

    DP on one mac, generates all midi through MidiOverLan CP3.

    ProTools 11.3.2 on second mac running VePro 6 server AAX plugins.

    Audio feeds directly into ProTools. No network or ethernet transfers. All Internal on the Pro Tools mac.

    MIDI is triggered via external midi in VePro via external midi.

    Is there any way to split midi and audio for an instance of a VePro Plug in.

    MidiOverLan has been out of business, and the software is hanging on even in Catalina. I was able to get it work for a while, but then changed a the drive to a different mac, and then it stopped working. In 10.14.6 MidiOverLan still works.

    Current system, NO audio glitches.

    Currently I have something like 400 midi tracks in DP, 48 tracks of similtaneous record in ProTools while running 8 instances of VePro with about 36x16 patches, 30 instances of the Lexicon PCM. All with no issues.

    Trying to run everything through DP, using VePro in DP and feeding DP all audio and midi from VePro, chokes the system with a twelve core Mac Pro. Splitting between the two computers is more efficient IF I can get midi from the DP computer to the ProTools computer.

    And no, CopperLan, RPTMidi, and ipMidi do not work. They don't have enough midi ports (I currently use 41) and they are tapping off of Apple's midi system which is a high level driver and starts choking after about 8 ports. MidiOverLan uses a kext which made it work so well they came out with a 128 port version right before going out dropping development of it.

    Any thoughts appreciated.

    Thanks