Vienna Symphonic Library Forum
Forum Statistics

190,082 users have contributed to 42,705 threads and 256,977 posts.

In the past 24 hours, we have 3 new thread(s), 44 new post(s) and 40 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. VEP Host Tempo Sync

  • VEP Host Tempo Sync

    Y
    Y

    So far I haven't been able to successfully get any tempo synced plugs to sync with my host (Logic Pro). Is it possible? I'd specifically like to get Kontakt and FXPansion Synth Squad (running in VEP32 on a slave machine) tempo synced with Logic. Can I do it with MIDI messages? Any plans to implement propper tempo sync support VSL? Isn't it a bit basic?

    Cheers,

    Will
  • K
    K

    There has been proper tempo syncing in VE Pro for quite some time, that is if you are using the VE Pro Server. Could you give some more information about your setup?
  • Y
    Y

    Hi Karel, thanks for jumping in on the thread so quickly!

    My setup is a pair of Mac Pros running OSX 10.6.4, Logic Pro 9.1.1 as the host, gigabit LAN, VEPro Server 32bit (v4.0.6150) on the slave.

    I should report that Spectrasonics Omnisphere is syncing up beautifully. Kontakt is also working great (apologies for reporting otherwise in my previous post, I ran into problems with Synth Squad and incorrectly assumed the behaviour would be the same with Kontakt).

    FXPansion Synth Squad (v1.0.3.11 [latest]) plugins (Amber, Cypher, Strobe, Fusor) loaded into the VEP slave are stuck at 120bpm.

    Thanks for your help.

    Cheers,

    Will
  • Y
    Y

    Of course, the same plugins/patches from Synth Squad sync up as expected if loaded directly into the Logic host project. I was just hoping to get the rather high CPU strain of some of these patches out of the master machine.
  • Y
    Y

    FXPansion BFD2 is also stuck at 120bpm. I'm wondering what type of tempo sync technology FXPansion are implementing that VSL are not..?
  • R
    R
    I can not sent midi clock from Cubase to VE Pro, because Cubase treats VEP's midi ports as VST instruments, not as midi ports. The only work around is to install third part midi, like MidiOverLan to send midi clock thru.
  • T
    T
    last edited
    last edited

    @Karel said:

    There has been proper tempo syncing in VE Pro for quite some time, that is if you are using the VE Pro Server. Could you give some more information about your setup?

     

    Karel - what's the situation with the standalone version?  If I send MIDi clock from the host via the local midi port, will VE Pro make sure all contained plugins sync to it?  I often have problems in my standalone instances of VE Pro and find that Kontakt does not sync to incoming clock.

    Thanks

    Jules
  • K
    K

    VE Pro standalone is not able to sync to MIDI clock yet. You should use the VE Pro Server instead, which provides sample accurate and jitter free time synchronization with the master host. I've further improved the time synchronization of AU's in VE Pro Server instances for the next update, which will also work around the sync issues with FXpansion AU's.
  • D
    D

    A problem I'm having (in OSX 10.6.6, Cubase 5.5.2, Kontakt 4.1), is that when I open an instance of Kontakt 4 inside VE Pro, all from Cubase by using a VST track preset, the Kontakt tempo is stuck at 120bpm until the tempo is adjusted again in Cubase, at which point it then syncs up.

    Perhaps the fault is with the Cubase vstpreset system though.  It seems like maybe when you load Kontakt-inside-VE Pro as a vstpreset it also defaults to the host tempo as it was when the vstpreset was first saved.

    So it confused me but while writing this I've figured out that I can work around it by either loading Kontakt manually into VE Pro, or by giving the Cubase tempo a nudge to wake Kontakt up and smell the tempo.

    :)