Vienna Symphonic Library Forum
Forum Statistics

182,382 users have contributed to 42,223 threads and 254,774 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. VEP 7 Server - How to sync MIDI clock?
  • Dewdman42D
    Dewdman42D

    why doesn't it work in 7.0.889 AU3 for me then?
  • M
    M

    Definetly the AU3 doesnt sent the tempo correctly. I´ve tried with VEP in local and in a second W10 machine. It needs to be fixed urgently, please!

    VEP vers. 7.0.889

    PD: In the stand alone version, I can´t change the tempo in the W10 vers. The OSX vers works fine. I´ve reistalled the VEP but it doesnt solve it.

    Report sent to support.

    EDIT: VEP adjusts the tempo of the DAW correctly but does not send it to the instruments. It seems the tempo is fixed to 120bpm.
  • G
    G
    last edited
    last edited
    No synchronization with the host's tempo.
    Just bought VEPro 7 a couple of weeks ago. From day one, I've been facing two major problems:
    1. Erratic behavior of certain Kontakt instruments when inserted into VEP. Kontakt libraries such as Strummed Acoustic just crash when you try to send MIDI from the DAW. I couldn't find any references to tempo or sync in VEP Server settings, so at first I even assumed that this feature has never been implemented in VEP, and there was no mechanism that would convey the external DAW's tempo information to the plugins inside a VEP Server instance over the Ethernet. Then, I discovered this thread and found a tiny '120' in the lower right corner of VEP Server's window, but that doesn't help much since I cannot even modify it.
    2. When an LPX project is created from scratch, and two VEP AU3 instruments are inserted and set to Ports 1 & 2, the second one cannot connect to the same instance of VEP Server. The templates from VSL website work OK, but I don't need that many tracks at this point. Would be nice to be able to create my own template that doesn't take up so much real estate on the screen. Emailed support several times (last on 3/23), still waiting for a reply to my last two messages.
    Meanwhile, I've been putting together a template that utilizes MIDI instead of multi-timbral AU3 instruments. The main idea behind it is to avoid cluttering the sequencer workspace with aux channels, while still being able to adjust vol/pan independently on each track. One of the templates from https://www.vsl.info/en/manuals/vep7/multiple-midi-ports-in-logic?q=template served as the foundation/starting point.
    I rearranged MIDI channel assignments, so that every port corresponds to the appropriate MIDI channel (Sub 1 = MIDI Ch. 1, etc). They may have been criss-crossed for a reason, but I couldn't figure it out for the life of me. So I put them in the usual order, and everything seems to be working fine, at least for now. Please take a look, maybe you'll find it useful.
    Any ideas/updates will be greatly appreciated. Stay safe everybody, and keep music alive!
    Remote DAW: Logic Pro X & Cubase 10 on MacBook Pro (15-inch, Mid 2010), macOS HighSierra Version 10.13.6, Intel Core i5 2.53 GHz, 8 GB 1067 MHz DDR3
    VEPro Server 7.0.973 on iMac (27-inch, Late 2013), Windows 10 Home Version 1909 (Boot Camp), Intel Core i7 3.5 GHz, 32 GB 1600 MHz DDR3.

    (VEU0020ProU00202x8).logicx.zip-1696338329666-zrk09.zip
  • Dewdman42D
    Dewdman42D

    Midi clock sync doesn't work with the AU3 VePro plugin right now.  Use the AU2 plugin instead for that

    If you need clock sync between daw and your VePro instance, you can't use AU3 for now from LogicPro.

    for the cases where you don't need midi clock sync, you can use AU3 and I reccomend you check out the templates I made here:

    https://www.logicprohelp.com/forum/viewtopic.php?f=9&t=143416#p763950

    (read the whole thread to learn how to create your own templates with more or less tracks.  Two appraoches are explained on that thread, one using multi-instruments (up to 127 tracks per VePro Instance) and one using midi enviornment objects for up to 768 tracks per VePro instance....all using AU3...so it won't work with midi clock sync.