Vienna Symphonic Library Forum
Forum Statistics

194,080 users have contributed to 42,911 threads and 257,913 posts.

In the past 24 hours, we have 6 new thread(s), 21 new post(s) and 83 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. MIDI problèms VEP SLAVE

  • MIDI problèms VEP SLAVE

    E
    E

    Hello,

    I am coming to you to present a situation that I encounter very often, and I hope to find a solution among you.

     

    I use VEP 7, on two machines.

    My master computer is a Mac Pro 2013 (under Catalina), 64 GB of RAM, and my slave a Mac Book Pro Max (Monterey), also with 64 GB of Ram

    .

    Logic Pro (latest version) is installed on the Mac Pro

     

    The connection is fine between the two computers, and from Logic Pro, I can access both the VEP on the Mac Pro ( Local) and the VEP on the Mac Book Pro ( Network) normally.

     

    On the Mac Book Pro ( Network) I have Spitfire Audio BBC ORCHESTRA and various Vienna banks installed, all in one VEP instance.

     

    The problem is that when I play tracks in Logic Pro with sounds on the Mac Book Pro (network), there are MIDI artefacts. Notes cut out, expression controls ( 11) are not smooth, and it causes me to have volume jumps in the sound.

    I also have MIDI notes that get stuck (no note OFF), or random notes that get added (often in the high end with channel 1, piccolo flute...).

     

    I already checked my Logic template and my VEP, everything seems normal. I have already checked my Logic template and my VEPs, everything seems normal, especially since I only have these problems with the VEP on the network and not the one on the master computer.

     

    Have any of you already experimented?

    Does VEP work better with Cubase (admittedly in Logic it's not easy with the AU's 16 channel limit).

    Is the AU 3 stable? Do any of you use it?

     

    I thank you for all your comments which could help me to improve the situation because I am convinced of the power of VEP, but for the moment, I do not manage to take full advantage of it.
  • MackerM
    MackerM

    VEPro AU3 functionality is currently very badly broken in the new Logic Pro.

    I've sent VSL Support a report, along with a very simple and straightforward Logic+VEPro test setup that I've used to reveal the worst of the mayhem (e.g. now only half of the 48 AU3 ports work in each VEPro instance). VSL's response was that VEPro AU3 is still a Beta version.

    My 'solution':- I can dual-boot my iMac between Big Sur and High Sierra and now the only Logic version I use is Logic Pro X 10.4.8 in High Sierra; with this setup I have no problems at all configuring and using AU3 multiport communications with VEPro (v 7.0.1056).

    Although I don't use Cubase Pro 11 much, I haven't encountered any problems in its communications with VEPro.

    I've no idea what VSL and/or Apple are currently doing to address this catastrophic mess between VEPro AU3 and the latest Logic, but I suggest you provide a detailed fault report to VSL Support, in the hope that it may help with diagnosis, etc.
  • E
    E

    Hi,

    Thanks for your reply. 

    Thank you for your answer,

    I will do this and send a report to support.

    I feel like I'm in a bit of a bind. Logic is optimized for Mac (better resource management than Cubase), but AU3 systematically bugs and freezes the system.

    Even without using AU3, the stability with VEP is not exemplary, I often have disconnections, and either Logic or VEP quit unexpectedly.

    This situation is not easy when you are in a professional situation and you have to be able to rely on your system to have an efficient workflow.
  • MackerM
    MackerM

    Eric, I completely understand your need for a reliable professional rig, and can only sympathise with you and other professional users of Logic who really cannot be doing with (what seems to me to be) the somewhat cavalier approach by Apple in their development of Logic.

    I'm also badly affected by the current issues in Logic, because I have a large-scale and complex design in Logic's Environment that I intend to release as a not-for-profit innovation that will give composers access to true orchestral intonation as they play-in live and write - but now of course it's on hold because of these issues.

    I'm painfully aware that my current workaround of using an old Logic Pro X in an old macOS is far from ideal and probably completely out of the question for very many Logic users. Hence of course I'm not recommending it.

    But what can be done? In your position right now I'd be seriously considering an alternative DAW, so that you can meet your professional commitments with confidence and in a timely manner.

    I suppose that Apple - just like with the awful mess they first made of Logic in the major update to Logic Pro X - will probably pull the new Logic Pro into reasonably good shape eventually. But how long that might take is anyone's guess. I must wait, but you don't have to. I can only wish you the very best of luck.