Vienna Symphonic Library Forum
Forum Statistics

201,008 users have contributed to 43,225 threads and 259,177 posts.

In the past 24 hours, we have 8 new thread(s), 24 new post(s) and 82 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro (legacy)
  4. VEP5 standalone Midi Sync problems

  • VEP5 standalone Midi Sync problems

    M
    M

    Hi,

    I have two midi sync problems in VEP5 standalone.

    Master is Mac G5 Dual 2,7 PPC with Logic 7.23.

    Slave is Windows 7 64bit with VEP5.0.9753 standalone.

    Midi is transferred by hardware interfaces (unitor and RME multiface)
    This setup is working well.

    But when syncing the arpeggiator in Omnisphere a constant crackling is occuring. It is mainly present in the lower registers of the audio spectrum, like basses and similiar sounds.
    This seems to come from constant variations in speed in VEP5, the speed indicator in the lower right corner is flickering, showing very fast variations from e.g. 114.72 to 115.16 BPM,  when original tempo in logic is 115.
    That looks like VEP is not really locking to midisync (or too well?;-)
    The midi sync signal itself must be valid and usable, because this problem does NOT happen at all when using e.g. MiniHost instead of VEP.
    In this case there is no crackling at all.
    This problem does also NOT happen when using the server version of VEP5. In this case the speed indicator in the corner of VEP5 is not
    flickering like in the standalone version, but is showing constantly very stable 115 BPM.

    Second problem: when fresh loaded VEP5 shows a "sync" tempo of  6.76766 BPM, as long as the sequencer did not start. In this state you cannot chose a patch for the arpeggiator, because everything is so SLOOOOOWWWW ;-) Other hosts do choose a standard tempo of 120 bpm as long as there was no midi sync at the input, don't they?

    I did not check with another plugin than omnisphere, but since the problem shows up in the tempo indicator in VEP5, I do not think that with another plugin it would be different.
    Of course in the midi preferences of VEP I checked "Clock sync source" for the correct midi in port.

    What is going on here? Is there a bug in the midi sync department of VEP5?
    Or did I miss s.th.?

    (BTW I tried a different midi interface... same result.)

    The way it is I cannot use the standalone version of VEP5 when sync is needed.

    Matthias
  • M
    M

    Hi,

    any comment from VSL? Midisync in VEP5 standalone is not working correctly here as I described above.

    I can't use the program in standalone mode the way it is, when sync is needed....

    Matthias
  • K
    K

    Could you send a mail to  with your issue? I can help you better that way.
  • M
    M
    last edited
    last edited

    Hi Karel,

    @Karel said:

    Could you send a mail to  with your issue? I can help you better that way.

    yes of course. Thanks for your response!

    Regards

    Matthias
  • M
    M

    Hi,

    though 5 days after my email to vsl-support I did not yet receive any answer, I now sorted it out myself:

    Crackling was produced by time locked delays that were involved in the synth patches inside

    Omnisphere (or Sylenth) I used for testing. Those delays seem to be very sensible to tempo

    changes, even if the changes are very small.

    Once I turn off the delay, the crackling is gone.

    So VEP5 is not the culprit...

    BUT: I compared VEP5 with other hosts (Bidule, LiveProfessor, MiniHost) in regard to

    synchronization: the amount of crackling in the delays (given a little jitter in the clock

    signal) is totally different between the different hosts. VEP5 is worst (it seems to

    lock "too well")... the other ones more or less seem to avarage or smooth out the

    jitter, what to me seems to be more appropriate in a world, where probably the

    sync signal from hardware midi interfaces very rarely is free of jitter.

    Best

    Matthias